Messages in this thread | | | Date | Sat, 2 Apr 2005 18:38:05 -0800 | From | "David S. Miller" <> | Subject | Re: iomapping a big endian area |
| |
On Sun, 3 Apr 2005 02:37:57 +0100 Matthew Wilcox <matthew@wil.cx> wrote:
> My thought on this is that we should encode the endianness of the > registers in the ioremap cookie. Some architectures (sparc, I think?) can > do this in their PTEs. The rest of us can do it in our ioread/writeN > methods. I've planned for this in the parisc iomap implementation but > not actually implemented it.
SPARC64 can do it in the PTEs, but we just use raw physical addresses in our I/O accessors, and in those load/store instructions we can specify the endianness.
Be careful though. Endianness can be dealt with on a hardware level. Consider a byte access to a 32-bit word sized config space datum, the PCI controller on a big-endian system will likely byte-twist the data lanes in order for this to work properly.
It's a subtle issue, and it's explained pretty well in some of the UltraSPARC PCI controller docs at:
http://www.sun.com/processors/documentation.html
In particular, "U2P UPA to PCI User's Manual", chapter 10 "Little-Endian Support", has some informative diagrams.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |