I wasn't necessarily thinking of doing it myself! :-) Mainly because
it's a *huge* job, because of all the old drivers which need to be
changed with any new scheme even to keep working on their original
platforms. Or lots of compatibility macros need writing.
Can you tell me what you mean by "virtual busaddr" to "physical
busaddr"? If it is a translation of addresses from the CPU subsystem to
those on the ISA/PCI bus, it's not a problem because it can be
encapsulated in ioremap().
If it's a way to access 64-bit PCI space from a 32-bit micro, everything
gets dubious because you sometimes want to pass the bus address around,
which needs the full 64 bits. To make matters worse, in this case some
devices won't be able to write to the memory of others because you can't
program them with 64-bit target addresses.
If it's a translation between different devices on the ISA/PCI bus
that's a much bigger problem because a few things do device-to-device
DMA, and they would have to know about this one way or another.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/