From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: Segher Boessenkool <segher@koffie.nl>
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
"Halfmann, Klaus" <Klaus.Halfmann@bauer-partner.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Unexpected sleep on old iBook
Date: Thu, 21 Nov 2002 23:47:34 -0500 [thread overview]
Message-ID: <20021122044733.GA22490@paco.resnet.purdue.edu> (raw)
In-Reply-To: <3DDC7AFC.6A8B4A0C@koffie.nl>
Segher Boessenkool spake unto us the following wisdom:
> Ethan Blanton wrote:
> > (Does it irritate anyone else that there seems to be no *good* way to
> > differentiate iBook versions? I'm sure there's some motherboard
> > resource version that's unambiguous, but come on...)
>
> Just read the device tree:
>
> /proc/device-tree/model gives you the model name.
> /proc/device-tree/scb# gives you the revision number.
I actually meant for the layman ... I realize that I can look up
system resources (in this case OF values) that will tell me, but hand
me an iBook and ask me what rev it is ... no clue.
Ethan
--
And if I claim to be a wise man / it surely means that I don't know.
-- Kansas, "Carry on Wayward Son"
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-22 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 8:15 Unexpected sleep on old iBook Halfmann, Klaus
2002-11-19 16:48 ` Michael Schmitz
2002-11-19 20:33 ` Ethan Blanton
2002-11-21 6:19 ` Segher Boessenkool
2002-11-22 4:47 ` Ethan Blanton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-20 11:11 Halfmann, Klaus
2002-11-19 7:43 Halfmann, Klaus
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=20021122044733.GA22490@paco.resnet.purdue.edu \
--to=eblanton@cs.ohiou.edu \
--cc=Klaus.Halfmann@bauer-partner.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=segher@koffie.nl \
/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).