Lines Matching +full:pci +full:- +full:to +full:- +full:cpu
6 -------------------------------------------------------------------------
12 in industrial control and other areas due to low cost and power
17 integration such as an on-chip I2C controller.
19 For more information on the various versions of the CPU, see:
23 Intel also made the IXCP1100 CPU for sometime which is an IXP4xx
30 - Dual serial ports
31 - PCI interface
32 - Flash access (MTD/JFFS)
33 - I2C through GPIO on IXP42x
34 - GPIO for input/output/interrupts
35 See arch/arm/mach-ixp4xx/include/mach/platform.h for access functions.
36 - Timers (watchdog, OS)
41 - USB device interface
42 - Network interfaces (HSS, Utopia, NPEs, etc)
43 - Network offload functionality
45 If you need to use any of the above, you need to download Intel's
50 DO NOT POST QUESTIONS TO THE LINUX MAILING LISTS REGARDING THE PROPRIETARY
56 - http://sourceforge.net/projects/ixp4xx-osdg/
59 - http://gatewaymaker.sourceforge.net/
62 - http://ixp425.sourceforge.net/
67 3a. Limited inbound PCI window
69 The IXP4xx family allows for up to 256MB of memory but the PCI interface
70 can only expose 64MB of that memory to the PCI bus. This means that if
71 you are running with > 64MB, all PCI buffers outside of the accessible
74 3b. Limited outbound PCI window
76 IXP4xx provides two methods of accessing PCI memory space:
78 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
79 To access PCI via this space, we simply ioremap() the BAR
81 macros. This is the preferred method due to speed but it
82 limits the system to just 64MB of PCI memory. This can be
83 problematic if using video cards and other memory-heavy devices.
86 configured to use indirect registers to access PCI This allows
87 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
88 The disadvantage of this is that every PCI access requires
91 mmap() PCI devices in this case due to the indirect nature
92 of the PCI window.
95 you need more PCI memory, enable the IXP4XX_INDIRECT_PCI config option.
99 Currently the code only handles level-sensitive GPIO interrupts
107 small residential/office gateways. One NPE is connected to a 10/100
108 interface, one to 4-port 10/100 switch, and the third to and ADSL
109 interface. In addition, it also supports to POTs interfaces connected
111 the platform has two mini-PCI slots used for 802.11[bga] cards.
117 The Avila platform is basically and IXDP425 with the 4 PCI slots
118 replaced with mini-PCI slots and a CF IDE interface hanging off
125 also known as the Richfield board. It contains 4 PCI slots, 16MB
137 added. One issue with this board is that the mini-PCI slots only
138 have the 3.3v line connected, so you can't use a PCI to mini-PCI
139 adapter with an E100 card. So to NFS root you need to use either
141 a pivot_root to NFS.
146 The PrPMC1100 is based on the IXCP1100 and is meant to plug into
147 and IXP2400/2800 system to act as the system controller. It simply
148 contains a CPU and 16MB of flash on the board and needs to be
149 plugged into a carrier board to function. Currently Linux only
154 - Add support for Coyote IDE
155 - Add support for edge-based GPIO interrupts
156 - Add support for CF IDE on expansion bus
164 - Lennerty Buytenhek
165 - Lutz Jaenicke
166 - Justin Mayfield
167 - Robert E. Ranslam
169 [I know I've forgotten others, please email me to be added]
171 -------------------------------------------------------------------------