if [31mCONFIG_ARCH_IXP4XX[0m
menu "Intel IXP4xx Implementation Options"
comment "IXP4xx Platforms"
config [31mCONFIG_MACH_NSLU2[0m
bool
prompt "Linksys NSLU2"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support Linksys's
NSLU2 NAS device. For more information on this platform,
see http://www.nslu2-linux.org
config [31mCONFIG_MACH_AVILA[0m
bool "Avila"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support the Gateworks
Avila Network Platform. For more information on this platform,
see <file:Documentation/arm/IXP4xx>.
config [31mCONFIG_MACH_LOFT[0m
bool "Loft"
depends on [31mCONFIG_MACH_AVILA[0m
help
Say 'Y' here if you want your kernel to support the Giant
Shoulder Inc Loft board (a minor variation on the standard
Gateworks Avila Network Platform).
config [31mCONFIG_ARCH_ADI_COYOTE[0m
bool "Coyote"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support the [31mCONFIG_ADI[0m
Engineering Coyote Gateway Reference Platform. For more
information on this platform, see <file:Documentation/arm/IXP4xx>.
config [31mCONFIG_MACH_GATEWAY7001[0m
bool "Gateway 7001"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support Gateway's
7001 Access Point. For more information on this platform,
see http://openwrt.org
config [31mCONFIG_MACH_WG302V2[0m
bool "Netgear WG302 v2 / WAG302 v2"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support Netgear's
WG302 v2 or WAG302 v2 Access Points. For more information
on this platform, see http://openwrt.org
config [31mCONFIG_ARCH_IXDP425[0m
bool "IXDP425"
help
Say 'Y' here if you want your kernel to support Intel's
IXDP425 Development Platform (Also known as Richfield).
For more information on this platform, see <file:Documentation/arm/IXP4xx>.
config [31mCONFIG_MACH_IXDPG425[0m
bool "IXDPG425"
help
Say 'Y' here if you want your kernel to support Intel's
IXDPG425 Development Platform (Also known as Montajade).
For more information on this platform, see <file:Documentation/arm/IXP4xx>.
config [31mCONFIG_MACH_IXDP465[0m
bool "IXDP465"
help
Say 'Y' here if you want your kernel to support Intel's
IXDP465 Development Platform (Also known as BMP).
For more information on this platform, see <file:Documentation/arm/IXP4xx>.
config [31mCONFIG_MACH_GORAMO_MLR[0m
bool "GORAMO Multi Link Router"
help
Say 'Y' here if you want your kernel to support GORAMO
MultiLink router.
config [31mCONFIG_MACH_KIXRP435[0m
bool "KIXRP435"
help
Say 'Y' here if you want your kernel to support Intel's
KIXRP435 Reference Platform.
For more information on this platform, see <file:Documentation/arm/IXP4xx>.
#
# IXCDP1100 is the exact same HW as IXDP425, but with a different machine
# number from the bootloader due to marketing monkeys, so we just enable it
# by default if IXDP425 is enabled.
#
config [31mCONFIG_ARCH_IXCDP1100[0m
bool
depends on [31mCONFIG_ARCH_IXDP425[0m
default y
config [31mCONFIG_ARCH_PRPMC1100[0m
bool "PrPMC1100"
help
Say 'Y' here if you want your kernel to support the Motorola
PrPCM1100 Processor Mezanine Module. For more information on
this platform, see <file:Documentation/arm/IXP4xx>.
config [31mCONFIG_MACH_NAS100D[0m
bool
prompt "NAS100D"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support Iomega's
NAS 100d device. For more information on this platform,
see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
config [31mCONFIG_MACH_DSMG600[0m
bool
prompt "D-Link DSM-G600 RevA"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support [31mCONFIG_D[0m-Link's
DSM-G600 RevA device. For more information on this platform,
see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
config [31mCONFIG_ARCH_IXDP4XX[0m
bool
depends on [31mCONFIG_ARCH_IXDP425[0m || [31mCONFIG_MACH_IXDP465[0m || [31mCONFIG_MACH_KIXRP435[0m
default y
config [31mCONFIG_MACH_FSG[0m
bool
prompt "Freecom FSG-3"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support Freecom's
FSG-3 device. For more information on this platform,
see http://www.nslu2-linux.org/wiki/FSG3/HomePage
config [31mCONFIG_MACH_ARCOM_VULCAN[0m
bool
prompt "Arcom/Eurotech Vulcan"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support Arcom's
Vulcan board.
#
# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
#
config [31mCONFIG_CPU_IXP46X[0m
bool
depends on [31mCONFIG_MACH_IXDP465[0m
default y
config [31mCONFIG_CPU_IXP43X[0m
bool
depends on [31mCONFIG_MACH_KIXRP435[0m
default y
config [31mCONFIG_MACH_GTWX5715[0m
bool "Gemtek WX5715 (Linksys WRV54G)"
depends on [31mCONFIG_ARCH_IXP4XX[0m
select [31mCONFIG_PCI[0m
help
This board is currently inside the Linksys WRV54G Gateways.
IXP425 - 266mhz
32mb SDRAM
8mb Flash
miniPCI slot 0 does not have a card connector soldered to the board
miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
npe0 is connected to a Kendin KS8995M Switch (4 ports)
npe1 is the "wan" port
"Console" UART is available on J11 as console
"High Speed" UART is n/c (as far as I can tell)
20 Pin [31mCONFIG_ARM[0m/Xscale JTAG interface on J2
config [31mCONFIG_MACH_DEVIXP[0m
bool "Omicron DEVIXP"
help
Say 'Y' here if you want your kernel to support the DEVIXP
board from OMICRON electronics GmbH.
config [31mCONFIG_MACH_MICCPT[0m
bool "Omicron MICCPT"
select [31mCONFIG_PCI[0m
help
Say 'Y' here if you want your kernel to support the MICCPT
board from OMICRON electronics GmbH.
config [31mCONFIG_MACH_MIC256[0m
bool "Omicron MIC256"
help
Say 'Y' here if you want your kernel to support the MIC256
board from OMICRON electronics GmbH.
comment "IXP4xx Options"
config [31mCONFIG_IXP4XX_INDIRECT_PCI[0m
bool "Use indirect PCI memory access"
depends on [31mCONFIG_PCI[0m
help
IXP4xx provides two methods of accessing [31mCONFIG_PCI[0m memory space:
1) [31mCONFIG_A[0m direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
To access [31mCONFIG_PCI[0m via this space, we simply ioremap() the BAR
into the kernel and we can use the standard read[bwl]/write[bwl]
macros. This is the preferred method due to speed but it
limits the system to just 64MB of [31mCONFIG_PCI[0m memory. This can be
problematic if using video cards and other memory-heavy devices.
2) If > 64MB of memory space is required, the IXP4xx can be
configured to use indirect registers to access the whole [31mCONFIG_PCI[0m
memory space. This currently allows for up to 1 GB (0x10000000
to 0x4FFFFFFF) of memory on the bus. The disadvantage of this
is that every [31mCONFIG_PCI[0m access requires three local register accesses
plus a spinlock, but in some cases the performance hit is
acceptable. In addition, you cannot mmap() [31mCONFIG_PCI[0m devices in this
case due to the indirect nature of the [31mCONFIG_PCI[0m window.
By default, the direct method is used. Choose this option if you
need to use the indirect method instead. If you don't know
what you need, leave this option unselected.
config [31mCONFIG_IXP4XX_QMGR[0m
tristate "IXP4xx Queue Manager support"
help
This driver supports IXP4xx built-in hardware queue manager
and is automatically selected by Ethernet and HSS drivers.
config [31mCONFIG_IXP4XX_NPE[0m
tristate "IXP4xx Network Processor Engine support"
select [31mCONFIG_FW_LOADER[0m
help
This driver supports IXP4xx built-in network coprocessors
and is automatically selected by Ethernet and HSS drivers.
endmenu
endif