linux-kernel - RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090417170707.B6C95C4004F@mail150-wa4.bigfish.com>
Date:	Fri, 17 Apr 2009 10:06:05 -0700
From:	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>
To:	<microblaze-uclinux@...e.uq.edu.au>, <linux-kernel@...r.kernel.org>
CC:	"John Linn" <john.linn@...inx.com>
Subject: RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze


Can we have XILINX_DRIVERS, please?  That way this can also be enabled
on any architecture that has FPGA peripherals.

Steve

> -----Original Message-----
> From: owner-microblaze-uclinux@...e.uq.edu.au
[mailto:owner-microblaze-uclinux@...e.uq.edu.au] On
> Behalf Of monstr@...str.eu
> Sent: Thursday, April 16, 2009 2:57 AM
> To: linux-kernel@...r.kernel.org
> Cc: microblaze-uclinux@...e.uq.edu.au; Michal Simek
> Subject: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig:
Enable drivers for Microblaze
> 
> From: Michal Simek <monstr@...str.eu>
> 
> Signed-off-by: Michal Simek <monstr@...str.eu>
> ---
>  drivers/block/Kconfig |    2 +-
>  drivers/char/Kconfig  |    2 +-
>  drivers/gpio/Kconfig  |    2 +-
>  drivers/usb/Kconfig   |    1 +
>  4 files changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index ddea8e4..9f1665f 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -438,7 +438,7 @@ source "drivers/s390/block/Kconfig"
> 
>  config XILINX_SYSACE
>  	tristate "Xilinx SystemACE support"
> -	depends on 4xx
> +	depends on 4xx || MICROBLAZE
>  	help
>  	  Include support for the Xilinx SystemACE CompactFlash
interface
> 
> diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> index 735bbe2..bb1a071 100644
> --- a/drivers/char/Kconfig
> +++ b/drivers/char/Kconfig
> @@ -893,7 +893,7 @@ config DTLK
> 
>  config XILINX_HWICAP
>  	tristate "Xilinx HWICAP Support"
> -	depends on XILINX_VIRTEX
> +	depends on XILINX_VIRTEX || MICROBLAZE
>  	help
>  	  This option enables support for Xilinx Internal Configuration
>  	  Access Port (ICAP) driver.  The ICAP is used on Xilinx Virtex
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index edb0253..11f3739 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -69,7 +69,7 @@ comment "Memory mapped GPIO expanders:"
> 
>  config GPIO_XILINX
>  	bool "Xilinx GPIO support"
> -	depends on PPC_OF
> +	depends on PPC_OF || MICROBLAZE
>  	help
>  	  Say yes here to support the Xilinx FPGA GPIO device
> 
> diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
> index c6c816b..5eee3f8 100644
> --- a/drivers/usb/Kconfig
> +++ b/drivers/usb/Kconfig
> @@ -22,6 +22,7 @@ config USB_ARCH_HAS_HCD
>  	default y if PCMCIA && !M32R			# sl811_cs
>  	default y if ARM				# SL-811
>  	default y if SUPERH				# r8a66597-hcd
> +	default y if MICROBLAZE
>  	default PCI
> 
>  # many non-PCI SOC chips embed OHCI
> --
> 1.5.5.1
> 
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@...e.uq.edu.au
> Project Home Page :
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> 


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/