cirrus: Move the Cirrus network driver
Move the Cirrus Ethernet driver into drivers/net/ethernet/cirrus/ and make the necessary Kconfig and Makefile changes CC: Hartley Sweeten <hsweeten@visionengravers.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
This commit is contained in:
Родитель
8c7de408fd
Коммит
57d0b7a0d7
|
@ -1768,7 +1768,7 @@ CIRRUS LOGIC EP93XX ETHERNET DRIVER
|
||||||
M: Hartley Sweeten <hsweeten@visionengravers.com>
|
M: Hartley Sweeten <hsweeten@visionengravers.com>
|
||||||
L: netdev@vger.kernel.org
|
L: netdev@vger.kernel.org
|
||||||
S: Maintained
|
S: Maintained
|
||||||
F: drivers/net/arm/ep93xx_eth.c
|
F: drivers/net/ethernet/cirrus/ep93xx_eth.c
|
||||||
|
|
||||||
CIRRUS LOGIC EP93XX OHCI USB HOST DRIVER
|
CIRRUS LOGIC EP93XX OHCI USB HOST DRIVER
|
||||||
M: Lennert Buytenhek <kernel@wantstofly.org>
|
M: Lennert Buytenhek <kernel@wantstofly.org>
|
||||||
|
|
|
@ -11,14 +11,6 @@ config ARM_AT91_ETHER
|
||||||
If you wish to compile a kernel for the AT91RM9200 and enable
|
If you wish to compile a kernel for the AT91RM9200 and enable
|
||||||
ethernet support, then you should always answer Y to this.
|
ethernet support, then you should always answer Y to this.
|
||||||
|
|
||||||
config EP93XX_ETH
|
|
||||||
tristate "EP93xx Ethernet support"
|
|
||||||
depends on ARM && ARCH_EP93XX
|
|
||||||
select MII
|
|
||||||
help
|
|
||||||
This is a driver for the ethernet hardware included in EP93xx CPUs.
|
|
||||||
Say Y if you are building a kernel for EP93xx based devices.
|
|
||||||
|
|
||||||
config W90P910_ETH
|
config W90P910_ETH
|
||||||
tristate "Nuvoton w90p910 Ethernet support"
|
tristate "Nuvoton w90p910 Ethernet support"
|
||||||
depends on ARM && ARCH_W90X900
|
depends on ARM && ARCH_W90X900
|
||||||
|
|
|
@ -4,5 +4,4 @@
|
||||||
#
|
#
|
||||||
|
|
||||||
obj-$(CONFIG_ARM_AT91_ETHER) += at91_ether.o
|
obj-$(CONFIG_ARM_AT91_ETHER) += at91_ether.o
|
||||||
obj-$(CONFIG_EP93XX_ETH) += ep93xx_eth.o
|
|
||||||
obj-$(CONFIG_W90P910_ETH) += w90p910_ether.o
|
obj-$(CONFIG_W90P910_ETH) += w90p910_ether.o
|
||||||
|
|
|
@ -18,6 +18,7 @@ source "drivers/net/ethernet/atheros/Kconfig"
|
||||||
source "drivers/net/ethernet/broadcom/Kconfig"
|
source "drivers/net/ethernet/broadcom/Kconfig"
|
||||||
source "drivers/net/ethernet/brocade/Kconfig"
|
source "drivers/net/ethernet/brocade/Kconfig"
|
||||||
source "drivers/net/ethernet/chelsio/Kconfig"
|
source "drivers/net/ethernet/chelsio/Kconfig"
|
||||||
|
source "drivers/net/ethernet/cirrus/Kconfig"
|
||||||
source "drivers/net/ethernet/cisco/Kconfig"
|
source "drivers/net/ethernet/cisco/Kconfig"
|
||||||
source "drivers/net/ethernet/dec/Kconfig"
|
source "drivers/net/ethernet/dec/Kconfig"
|
||||||
source "drivers/net/ethernet/dlink/Kconfig"
|
source "drivers/net/ethernet/dlink/Kconfig"
|
||||||
|
|
|
@ -10,6 +10,7 @@ obj-$(CONFIG_NET_VENDOR_ATHEROS) += atheros/
|
||||||
obj-$(CONFIG_NET_VENDOR_BROADCOM) += broadcom/
|
obj-$(CONFIG_NET_VENDOR_BROADCOM) += broadcom/
|
||||||
obj-$(CONFIG_NET_VENDOR_BROCADE) += brocade/
|
obj-$(CONFIG_NET_VENDOR_BROCADE) += brocade/
|
||||||
obj-$(CONFIG_NET_VENDOR_CHELSIO) += chelsio/
|
obj-$(CONFIG_NET_VENDOR_CHELSIO) += chelsio/
|
||||||
|
obj-$(CONFIG_NET_VENDOR_CIRRUS) += cirrus/
|
||||||
obj-$(CONFIG_NET_VENDOR_CISCO) += cisco/
|
obj-$(CONFIG_NET_VENDOR_CISCO) += cisco/
|
||||||
obj-$(CONFIG_NET_VENDOR_DEC) += dec/
|
obj-$(CONFIG_NET_VENDOR_DEC) += dec/
|
||||||
obj-$(CONFIG_NET_VENDOR_DLINK) += dlink/
|
obj-$(CONFIG_NET_VENDOR_DLINK) += dlink/
|
||||||
|
|
|
@ -0,0 +1,28 @@
|
||||||
|
#
|
||||||
|
# Cirrus network device configuration
|
||||||
|
#
|
||||||
|
|
||||||
|
config NET_VENDOR_CIRRUS
|
||||||
|
bool "Cirrus devices"
|
||||||
|
depends on ARM && ARCH_EP93XX
|
||||||
|
---help---
|
||||||
|
If you have a network (Ethernet) card belonging to this class, say Y
|
||||||
|
and read the Ethernet-HOWTO, available from
|
||||||
|
<http://www.tldp.org/docs.html#howto>.
|
||||||
|
|
||||||
|
Note that the answer to this question doesn't directly affect the
|
||||||
|
kernel: saying N will just cause the configurator to skip all
|
||||||
|
the questions about Cirrus cards. If you say Y, you will be asked
|
||||||
|
for your specific card in the following questions.
|
||||||
|
|
||||||
|
if NET_VENDOR_CIRRUS
|
||||||
|
|
||||||
|
config EP93XX_ETH
|
||||||
|
tristate "EP93xx Ethernet support"
|
||||||
|
depends on ARM && ARCH_EP93XX
|
||||||
|
select MII
|
||||||
|
help
|
||||||
|
This is a driver for the ethernet hardware included in EP93xx CPUs.
|
||||||
|
Say Y if you are building a kernel for EP93xx based devices.
|
||||||
|
|
||||||
|
endif # NET_VENDOR_CIRRUS
|
|
@ -0,0 +1,5 @@
|
||||||
|
#
|
||||||
|
# Makefile for the Cirrus network device drivers.
|
||||||
|
#
|
||||||
|
|
||||||
|
obj-$(CONFIG_EP93XX_ETH) += ep93xx_eth.o
|
Загрузка…
Ссылка в новой задаче