Re: ioremap definition in generic io.h

[Arnd Bergmann]

On Wednesday 29 September 2010, Jonas Bonn wrote:
> On another note, looking at the definitions of ioread32/iowrite32, they
> imply a little-endian bus.  Some architectures (e.g. Microblaze) define
> these to use host-native byte ordering instead.  Is there a correct
> way these functions should be defined?

ioread32/iowrite32 are accessor functions for PCI byte order which is
little endian. If microblaze does this differently, that is a microblaze
bug. Any code that needs big-endian I/O should use ioread32be/iowrite32be.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/