From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound7-blu-R.bigfish.com (outbound-blu.frontbridge.com [65.55.251.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id C078BDE3B5 for ; Sat, 27 Jan 2007 10:12:33 +1100 (EST) Message-ID: <45BA8ADA.8000108@am.sony.com> Date: Fri, 26 Jan 2007 15:12:26 -0800 From: Geoff Levand MIME-Version: 1.0 To: Nathan Lynch Subject: Re: [PATCH 10/14] ps3: get firmware version References: <45B81891.1010309@am.sony.com> <20070126025955.GE18537@lst.de> <45BA4DD5.2030106@am.sony.com> <1169843138.24996.114.camel@localhost.localdomain> <20070126203758.GC17317@localdomain> In-Reply-To: <20070126203758.GC17317@localdomain> Content-Type: text/plain; charset=UTF-8 Cc: paulus@samba.org, linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Nathan Lynch wrote: > 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: But this firmware does not. The kernel must do it sometime after startup. I don't see any reason why the kernel should try to emulate the behavior of firmware on some other platform. -Geoff