From: Dan Malek <dan@netx4.com>
To: jlquinn@us.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Help with cross-endian bitfields?
Date: Fri, 05 May 2000 16:05:52 -0400 [thread overview]
Message-ID: <391329A0.763DED8@embeddededge.com> (raw)
In-Reply-To: 852568D6.006ADE94.00@D51MTA03.pok.ibm.com
jlquinn@us.ibm.com wrote:
> Hi, all. I'm working on getting the Advansys driver working and what
> appears to be the final stumbling block is a difference in the layout of
> bitfields between little-endian and big-endian systems.
IMHO, bit fields are not normally a good thing to be using if this is
describing a real device register. The compiler is able to read/write
in ways that may not be proper for hardware access. For device registers
and when this is a data structure in memory, the cross-platform method
of using macros for reading writing 16- and 32-bit values and then 'C'
operators for testing/setting bits has worked pretty well in the past.....
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-05 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 19:27 Help with cross-endian bitfields? jlquinn
2000-05-05 20:05 ` Dan Malek [this message]
2000-05-05 20:45 ` Josh Huber
2000-05-05 20:49 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2000-05-05 20:47 jlquinn
[not found] <200005060514.AAA05188@lists.linuxppc.org>
2000-05-08 7:03 ` james woodyatt
2000-05-08 9:50 ` Geert Uytterhoeven
2000-05-08 10:13 D.J. Barrow
2000-05-08 14:19 ` Geert Uytterhoeven
2000-05-08 14:38 jlquinn
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=391329A0.763DED8@embeddededge.com \
--to=dan@netx4.com \
--cc=jlquinn@us.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.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.