From: Ben Collins <bcollins@debian.org>
To: Nico Schottelius <nico-mutt@schottelius.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: transmeta cpu code question
Date: Wed, 19 Nov 2003 21:53:15 -0500 [thread overview]
Message-ID: <20031120025315.GR11983@phunnypharm.org> (raw)
In-Reply-To: <20031120020218.GJ3748@schottelius.org>
On Thu, Nov 20, 2003 at 03:02:18AM +0100, Nico Schottelius wrote:
> Hello!
>
> What does this do:
>
> printk(KERN_INFO "CPU: Processor revision %u.%u.%u.%u,
> %u MHz\n",
> (cpu_rev >> 24) & 0xff,
> (cpu_rev >> 16) & 0xff,
> (cpu_rev >> 8) & 0xff,
> cpu_rev & 0xff,
> cpu_freq);
>
> (from arch/i386/kernel/cpu/transmeta.c)
>
> Does not & 0xff make no sense? 0 & 1 makes 0, 1 & 1 makes 1,
> no changes.
>
> And I don't understand why we do this for 8bit and shifting the
> cpu_rev...
You are a bit confused. The cpu_rev is a 4 byte value, each byte is a
decimal of the revision.
And (0 & 1) makes 1, not 0. That's an AND, not an OR.
Think about it this way. If cpu_rev == 0x01040801, then this would
produce:
(0x01040801 >> 24 & 0xff) -> (0x01 & 0xff) -> 0x01
(0x01040801 >> 16 & 0xff) -> (0x0104 & 0xff) -> 0x04
(0x01040801 >> 8 & 0xff) -> (0x010408 & 0xff) -> 0x08
(0x01040801 & 0xff) -> 0x01
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2003-11-20 2:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 2:02 transmeta cpu code question Nico Schottelius
2003-11-20 2:10 ` Ben Hoskings
2003-11-20 8:38 ` Nico Schottelius
2003-11-20 17:33 ` H. Peter Anvin
2003-11-20 23:25 ` Jamie Lokier
2003-11-21 8:34 ` John Bradford
2003-11-21 8:48 ` Jamie Lokier
2003-11-24 6:54 ` H. Peter Anvin
2003-11-24 13:19 ` Jamie Lokier
2003-11-20 2:53 ` Ben Collins [this message]
2003-11-20 3:06 ` Kevin P. Fleming
2003-11-20 13:25 ` Ben Collins
2003-11-20 3:18 ` Ben Hoskings
2003-11-20 6:57 ` Eric Sandall
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=20031120025315.GR11983@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-mutt@schottelius.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.