All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 10/14] ps3: get firmware version
Date: Fri, 26 Jan 2007 10:52:05 -0800	[thread overview]
Message-ID: <45BA4DD5.2030106@am.sony.com> (raw)
In-Reply-To: <20070126025955.GE18537@lst.de>

Christoph Hellwig wrote:
> On Wed, Jan 24, 2007 at 06:40:17PM -0800, Geoff Levand wrote:
>> Output the PS3 firmware version to dmesg and /proc/cpuinfo.
> 
> Do we really need to bloat /proc/cpuinfo with more information that's
> totally platform-specific?  The file is enough of a mess already..

I wanted to make the firmware version available to user space utilities, so
for example, I plan to make a utility to write the kernel to flash.  If the
utility can query the firmware version, it can prompt the user that a firmware
update would allow the kernel to take advantage of some new or updated feature.
Without this, the only way to notify the user is with a message to the system
log when the new kernel is running.

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.

-Geoff

  reply	other threads:[~2007-01-26 18:56 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 [this message]
2007-01-26 20:25     ` Benjamin Herrenschmidt
2007-01-26 20:37       ` Nathan Lynch
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=45BA4DD5.2030106@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=hch@lst.de \
    --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 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.