linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis <hollis-lists@austin.rr.com>
To: "Timothy A. Seufert" <tas@mindspring.com>,
	linuxppc-dev@lists.linuxppc.org
Cc: "Guillaume Laurès" <guillaume.laures@noos.fr>,
	"Leonard N. Zubkoff" <lnz@dandelion.com>
Subject: Re: another endianness issue...
Date: Sat, 23 Jun 2001 13:33:27 -0500	[thread overview]
Message-ID: <01062313332701.00569@silence.internal> (raw)
In-Reply-To: <v04220800b75a8da0ed9d@[10.0.0.42]>


On Saturday 23 June 2001 01:19, Timothy A. Seufert wrote:
>
> Bitfields are not a good way to describe hardware registers.

Why is that? Are there generally bitfield problems other than this one?

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-06-23 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B2E747A.6090607@noos.fr>
     [not found] ` <01061823464800.00690@reality.internal>
     [not found]   ` <3B2F0871.2070304@noos.fr>
     [not found]     ` <0106192003070C.00609@reality.internal>
2001-06-22 17:12       ` getting the 8600 to boot 2.4.5 Guillaume Laurès
2001-06-24  9:54         ` Michel Lanners
2001-06-24 11:39           ` Takashi Oe
2001-06-23  9:29       ` another endianness issue Guillaume Laurès
2001-06-23 18:19         ` Timothy A. Seufert
2001-06-23 18:33           ` Hollis [this message]
2001-06-23 23:22             ` Benjamin Herrenschmidt
2001-06-24 13:59           ` Guillaume Laurès
2001-06-24 14:50             ` Benjamin Herrenschmidt
2001-06-24 14:52             ` Geert Uytterhoeven
2001-06-24 22:49             ` Dan Malek

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=01062313332701.00569@silence.internal \
    --to=hollis-lists@austin.rr.com \
    --cc=guillaume.laures@noos.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=lnz@dandelion.com \
    --cc=tas@mindspring.com \
    /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;
as well as URLs for NNTP newsgroup(s).