mach/io.h cleanup and removal question
andrew at lunn.ch
Fri Jun 8 10:35:48 EDT 2012
> > Probably shrinking ORION5X_PCIE_IO_SIZE to 64K, unless we really have a
> > requirement to support a larger IO space.
> Agreed. The next step is moving all i/o space to a fixed virtual address
> and for this we want to make i/o windows 64K.
O.K. I will submit a patch for this, so Orion5x at least boots. Maybe
PCI will not work, but booting is a step forward.
> However, I think you may also have a problem with
> ORION5X_PCIE_IO_BUS_BASE and the resource start. The i/o resource start
> should really be 0 and then the __io() macro should add the virtual i/o
> base address. However, Russell has mentioned previously that some chips
> may not work correctly with i/o space at 0 (PCI bus addresses, not host).
> Do you have cards with i/o that you can test or know what devices are
> used with this platform?
Humm, not sure. I have a Marvell Orion5x NAS reference design. It has
a Mini-PCI slot on the bottom. So if i can find a card, i can test. I
know i have some WiFi cards in my junk box, but i've no idea if these
More information about the linux-arm-kernel