From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: "Kyle McMartin" <kyle@mcmartin.ca>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: ioread32 endianess.
Date: Tue, 27 Feb 2007 15:31:20 +0300 [thread overview]
Message-ID: <f19298770702270431i198e032fhe025e221a625140f@mail.gmail.com> (raw)
In-Reply-To: <20070226160450.GB3787@athena.road.mcmartin.ca>
On 2/26/07, Kyle McMartin <kyle@mcmartin.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
>
next prev parent reply other threads:[~2007-02-27 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 15:36 ioread32 endianess Alexey Zaytsev
2007-02-26 16:04 ` Kyle McMartin
2007-02-27 12:31 ` Alexey Zaytsev [this message]
2007-02-27 13:20 ` Kyle McMartin
2007-02-27 13:55 ` Kyle McMartin
2007-02-27 14:27 ` Haavard Skinnemoen
2007-02-27 14:36 ` Alexey Zaytsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f19298770702270431i198e032fhe025e221a625140f@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox