linux-kernel - Re: ioremap definition in generic io.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201009301345.16817.arnd@arndb.de>
Date:	Thu, 30 Sep 2010 13:45:16 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jonas Bonn <jonas@...thpole.se>
Cc:	Jiri Slaby <jirislaby@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: ioremap definition in generic io.h

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/