linux-kernel - Re: ioread32 endianess.

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: <f19298770702270431i198e032fhe025e221a625140f@mail.gmail.com>
Date:	Tue, 27 Feb 2007 15:31:20 +0300
From:	"Alexey Zaytsev" <alexey.zaytsev@...il.com>
To:	"Kyle McMartin" <kyle@...artin.ca>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: ioread32 endianess.

On 2/26/07, Kyle McMartin <kyle@...artin.ca> wrote:
> On Mon, Feb 26, 2007 at 06:36:05PM +0300, Alexey Zaytsev wrote:
> > Hello.
> >
> > May I ask you, guys, if ioread32 and his friends should treat the data
> > as host-endian or bus-endian? E.g, should the data read from PCI on a
> > big-endian host be byte swapped or not?
> >
>
> It should be in bus-endian. This is why ioreadXbe() exist.

Than how should one write a portable endian-independent driver? Should
I wrap ioread32 with an le32_to_cpu?

>
> Cheers,
>         Kyle
>
-
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/