From: Manfred Spraul <manfred@colorfullife.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David S. Miller" <davem@redhat.com>,
alan@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.40-ac1
Date: Thu, 03 Oct 2002 17:53:51 +0200 [thread overview]
Message-ID: <3D9C680F.5080705@colorfullife.com> (raw)
In-Reply-To: 1033660105.28814.11.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
> On Thu, 2002-10-03 at 16:18, Manfred Spraul wrote:
>
>>There should bit nonatomic bit ops for every byte width.
>>
>>http://marc.theaimsgroup.com/?l=linux-kernel&m=99167415926343&w=2
>>
>>I even sent you the patch proposal, but never got a reply.
>>
>>Patch again attached, but untested.
>
>
> What about reverse endianness ?
AFAIK, writeX macros should swap as needed, i.e.
writel(0x100,ioaddr);
should arrive as bit 8 set on the hardware. [please correct me if I'm
wrong] Thus the input into write{b,w,l} should be in host byte order.
u{8,16,32} array[];
__set_bit_{8,16,32}(,array);
write{b,w,l}(array[],ioaddr);
would achieve that.
next prev parent reply other threads:[~2002-10-03 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 14:45 Linux 2.5.40-ac1 Manfred Spraul
2002-10-03 14:50 ` David S. Miller
2002-10-03 15:18 ` Manfred Spraul
2002-10-03 15:15 ` David S. Miller
2002-10-03 15:48 ` Alan Cox
2002-10-03 15:53 ` Manfred Spraul [this message]
2002-10-03 15:17 ` Alan Cox
2002-10-03 15:34 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 23:38 Greg Ungerer
2002-10-03 14:17 ` Christoph Hellwig
2002-10-03 14:20 ` Alan Cox
2002-10-03 14:51 ` Christoph Hellwig
2002-10-03 15:25 ` Alan Cox
2002-10-03 15:28 ` Christoph Hellwig
2002-10-03 15:31 ` Greg Ungerer
2002-10-03 19:16 ` Rik van Riel
2002-10-03 23:44 ` Greg Ungerer
2002-10-04 0:32 ` Rik van Riel
2002-10-02 22:18 Alan Cox
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=3D9C680F.5080705@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=davem@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.