From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Carl Love <cel@us.ibm.com>
Subject: Re: Help with an MMIO register read function
Date: Sat, 11 Nov 2006 00:10:28 +0100 [thread overview]
Message-ID: <200611110010.28788.arnd@arndb.de> (raw)
In-Reply-To: <1163199434.30540.13.camel@dyn9047021226.beaverton.ibm.com>
On Friday 10 November 2006 23:57, Carl Love wrote:
> I expect the SBI values to be 0x2000000 =A0not 0x200000000. =A0The L2 deb=
ug
> value should be 0x6 not 0x600000000000000. =A0It seems like the bits are
> there but shifted from where I would expect them to be. =A0Anyone have any
> thoughts as to what is wrong?
Hmm, maybe you confused the bit order in the specification? IBM
counts the MSB as bit 0, while everyone else counts the LSB as
bit 0.
Arnd <><
next prev parent reply other threads:[~2006-11-10 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 22:57 Help with an MMIO register read function Carl Love
2006-11-10 23:10 ` Arnd Bergmann [this message]
2006-11-11 1:46 ` Benjamin Herrenschmidt
2006-11-13 17:06 ` Carl Love
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=200611110010.28788.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cel@us.ibm.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).