On Thu, 25 Jan 2007, Jeff Garzik wrote:
>
> On sparc64, for example, after I pointed this out to DaveM, he was able to
> implement the new iomap interface without the 'if (pio-mem-area)' branch
> present on x86.
However, in all honesty, we have triggered bugs in that area too, simply
because some driver code "knew" that PIO addresses could fit in 16 bits,
and used u16 or "unsigned short" to remember the PIO address. Both ARM and
Sparc was bitten by this, although usually the issue is trivial to fix
once found.
Also, many ISA-only drivers actually have hardcoded PIO numbers (eg
"0x1f0").
But yes, I would generally suggest that architectures where the PIO range
is really just another magic MMIO range (which is most of the non-x86
world, as you point out) might as well at least aim for doing the
remapping early (ie with "pci_resource_start()")
Making that easy was one of my goals for the "new" IO accessor functions,
in fact.
Not that many people actually use them.
So *if* you use the new "iomap" interfaces, and the new "pci_iomap()"
things, that should actually not just allow drivers (like the ATA layer)
to share much more code between the PIO and MMIO cases, but it hopefully
actually makes it easier for strange architectures to do it all.
So traditionally, we've had PIO be "limited integer addresses, and some
drivers know magic numbers", but hopefully new drivers could at least try
to use some of the infrastructure where we try to help people not have to
deal with it so much as a special case any more.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
