2019-05-19 13:07:45 +01:00
# SPDX-License-Identifier: GPL-2.0-only
2005-04-16 15:20:36 -07:00
if ARCH_IXP4XX
menu "Intel IXP4xx Implementation Options"
comment "IXP4xx Platforms"
2019-01-27 14:08:36 +01:00
config MACH_IXP4XX_OF
bool
prompt "Devce Tree IXP4xx boards"
default y
select ARM_APPENDED_DTB # Old Redboot bootloaders deployed
select I2C
select I2C_IOP3XX
select PCI
select TIMER_OF
select USE_OF
help
Say 'Y' here to support Device Tree-based IXP4xx platforms.
2005-11-10 14:05:04 +00:00
config MACH_NSLU2
bool
2006-03-08 23:45:12 +00:00
prompt "Linksys NSLU2"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2005-11-10 14:05:04 +00:00
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
2006-12-16 23:04:05 +01:00
config MACH_AVILA
2005-04-16 15:20:36 -07:00
bool "Avila"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2005-04-16 15:20:36 -07:00
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>.
2006-12-16 23:04:05 +01:00
config MACH_LOFT
bool "Loft"
depends on MACH_AVILA
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).
2005-04-16 15:20:36 -07:00
config ARCH_ADI_COYOTE
bool "Coyote"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2005-04-16 15:20:36 -07:00
help
Say 'Y' here if you want your kernel to support the ADI
Engineering Coyote Gateway Reference Platform. For more
information on this platform, see <file:Documentation/arm/IXP4xx>.
2007-06-02 15:44:08 +01:00
config MACH_GATEWAY7001
bool "Gateway 7001"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2007-06-02 15:44:08 +01:00
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
2007-06-02 15:47:51 +01:00
config MACH_WG302V2
bool "Netgear WG302 v2 / WAG302 v2"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2007-06-02 15:47:51 +01:00
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
2005-04-16 15:20:36 -07:00
config ARCH_IXDP425
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 MACH_IXDPG425
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 MACH_IXDP465
bool "IXDP465"
help
Say 'Y' here if you want your kernel to support Intel's
IXDP465 Development Platform (Also known as BMP).
2005-04-16 15:23:56 -07:00
For more information on this platform, see <file:Documentation/arm/IXP4xx>.
2005-04-16 15:20:36 -07:00
2009-05-23 23:58:30 +02:00
config MACH_GORAMO_MLR
bool "GORAMO Multi Link Router"
help
Say 'Y' here if you want your kernel to support GORAMO
MultiLink router.
2007-04-06 15:00:31 +01:00
config MACH_KIXRP435
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>.
2005-04-16 15:20:36 -07:00
#
# 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 ARCH_IXCDP1100
bool
depends on ARCH_IXDP425
default y
config ARCH_PRPMC1100
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>.
2006-01-04 17:17:11 +00:00
config MACH_NAS100D
bool
prompt "NAS100D"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2006-01-04 17:17:11 +00:00
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
2007-04-28 08:31:40 +01:00
config MACH_DSMG600
bool
prompt "D-Link DSM-G600 RevA"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2007-04-28 08:31:40 +01:00
help
Say 'Y' here if you want your kernel to support D-Link's
DSM-G600 RevA device. For more information on this platform,
see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
2005-04-16 15:20:36 -07:00
config ARCH_IXDP4XX
bool
2007-04-06 15:00:31 +01:00
depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
2005-04-16 15:20:36 -07:00
default y
2008-04-01 10:53:23 +01:00
config MACH_FSG
bool
prompt "Freecom FSG-3"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2008-04-01 10:53:23 +01:00
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
2010-04-10 21:32:38 +01:00
config MACH_ARCOM_VULCAN
bool
prompt "Arcom/Eurotech Vulcan"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2010-04-10 21:32:38 +01:00
help
Say 'Y' here if you want your kernel to support Arcom's
Vulcan board.
2005-04-16 15:20:36 -07:00
#
# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
#
config CPU_IXP46X
bool
depends on MACH_IXDP465
default y
2007-04-06 15:00:31 +01:00
config CPU_IXP43X
bool
depends on MACH_KIXRP435
default y
2005-04-16 15:20:36 -07:00
config MACH_GTWX5715
bool "Gemtek WX5715 (Linksys WRV54G)"
depends on ARCH_IXP4XX
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2005-04-16 15:20:36 -07:00
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 ARM/Xscale JTAG interface on J2
2011-09-28 15:16:41 +02:00
config MACH_DEVIXP
bool "Omicron DEVIXP"
help
Say 'Y' here if you want your kernel to support the DEVIXP
board from OMICRON electronics GmbH.
config MACH_MICCPT
bool "Omicron MICCPT"
2018-11-15 20:05:32 +01:00
select FORCE_PCI
2011-09-28 15:16:41 +02:00
help
Say 'Y' here if you want your kernel to support the MICCPT
board from OMICRON electronics GmbH.
config MACH_MIC256
bool "Omicron MIC256"
help
Say 'Y' here if you want your kernel to support the MIC256
board from OMICRON electronics GmbH.
2005-04-16 15:20:36 -07:00
comment "IXP4xx Options"
config IXP4XX_INDIRECT_PCI
bool "Use indirect PCI memory access"
2006-04-30 15:34:29 +01:00
depends on PCI
2005-04-16 15:20:36 -07:00
help
IXP4xx provides two methods of accessing PCI memory space:
2009-11-15 18:02:10 +01:00
1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
2005-04-16 15:20:36 -07:00
To access PCI 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
2009-11-15 18:02:10 +01:00
limits the system to just 64MB of PCI memory. This can be
2006-11-30 05:22:59 +01:00
problematic if using video cards and other memory-heavy devices.
2009-11-15 18:02:10 +01:00
2) If > 64MB of memory space is required, the IXP4xx can be
configured to use indirect registers to access the whole PCI
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 PCI access requires three local register accesses
plus a spinlock, but in some cases the performance hit is
acceptable. In addition, you cannot mmap() PCI devices in this
case due to the indirect nature of the PCI window.
2005-04-16 15:20:36 -07:00
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.
endmenu
endif