From: Nathan Lynch <ntl@pobox.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 10/14] ps3: get firmware version
Date: Fri, 26 Jan 2007 14:37:58 -0600 [thread overview]
Message-ID: <20070126203758.GC17317@localdomain> (raw)
In-Reply-To: <1169843138.24996.114.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> > Anyway, that is the need, the question is where to make it
> > available. I thought /proc/cpuinfo already has the platform type
> > (coming from the generic powerpc code), so it would be convenient
> > for utilities to have the firmware version there too. I don't
> > think parsing the dmsg is an option for minimal configs like
> > bootloaders and distro installers, as they may not keep the boot
> > messages around, and in general doesn't seem a reliable way. If
> > you can make a suggestion, I'd like to hear it.
>
> Yeah, /proc/cpuinfo is actually a fairly convenient place for that...
Other firmwares provide a property in the device tree with version
information, for example on Power5:
$ lsprop /proc/device-tree/openprom/ibm,fw-vernum_encoded
/proc/device-tree/openprom/ibm,fw-vernum_encoded "SF225_096"
next prev parent reply other threads:[~2007-01-26 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 2:40 [PATCH 10/14] ps3: get firmware version Geoff Levand
2007-01-25 3:56 ` Benjamin Herrenschmidt
2007-01-25 6:23 ` Arnd Bergmann
2007-01-26 2:59 ` Christoph Hellwig
2007-01-26 18:52 ` Geoff Levand
2007-01-26 20:25 ` Benjamin Herrenschmidt
2007-01-26 20:37 ` Nathan Lynch [this message]
2007-01-26 23:12 ` Geoff Levand
2007-01-26 23:27 ` Geoff Levand
2007-01-27 4:34 ` Benjamin Herrenschmidt
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=20070126203758.GC17317@localdomain \
--to=ntl@pobox.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).