[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMO-S2i8Z7q2NQN4WDwvwjrNAoe2uFKhFcfpLb4gRHoZtiynzQ@mail.gmail.com>
Date: Thu, 9 Feb 2012 01:14:39 +0900
From: Hitoshi Mitake <h.mitake@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Roland Dreier <roland@...estorage.com>,
Matthew Garrett <mjg@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
James Bottomley <James.Bottomley@...allels.com>,
Ravi Anand <ravi.anand@...gic.com>,
James Bottomley <jbottomley@...allels.com>,
Len Brown <lenb@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Uhlenkott <juhlenko@...mai.com>,
Kashyap Desai <Kashyap.Desai@....com>,
linux-kernel@...r.kernel.org,
Vikas Chaudhary <vikas.chaudhary@...gic.com>,
Matthew Wilcox <matthew.r.wilcox@...el.com>, mingo@...e.hu
Subject: Re: [PATCH] asm-generic: architecture independent readq/writeq for
32bit environment
On Tue, Feb 7, 2012 at 12:56, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Feb 6, 2012 6:47 PM, "Hitoshi Mitake" <h.mitake@...il.com> wrote:
>>
>> All of them are endian aware
>
> I think that part is wrong.
>
> Pci is little-endian, so readl and writel are always already little-endian.
> Trying to make readq be endian-aware is wrong.
Is every memory area which can be read/written by read[wl]/write[wl]
always little-endian?
If so, of course I have to eliminate the big-endian version.
But I'm not sure about this point because the new readq/writeq is
in asm-generic which is used by every archs, so I'd like to ask you about it.
>
> Linus
>
> On Feb 6, 2012 6:47 PM, "Hitoshi Mitake" <h.mitake@...il.com> wrote:
--
Hitoshi Mitake
h.mitake@...il.com
--
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/
Powered by blists - more mailing lists