From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 13/16] ps3: get firmware version
Date: Mon, 29 Jan 2007 11:13:46 -0800 [thread overview]
Message-ID: <45BE476A.3010407@am.sony.com> (raw)
In-Reply-To: <200701271230.06534.arnd@arndb.de>
Arnd Bergmann wrote:
>> Changed from a struct to a union and got rid of the output to /proc/cpuinfo.
>> I'll look into arranging something in /proc/device-tree that userspace utils
>> can query.
>
> What's the current plan for the creating the device tree anyway? I think
> this should be part of the boot wrapper for the kernel in the ps3 flash,
> which can write the version into the flattened device tree. The second
> kernel then gets a copy of that through kboot.
Yes, that's hopefully ppossible, start with the static tree from ps3.dts then
add some properties in the first stage (romboot) wrapper entry. kboot then
passes that to the second stage wrapper entry, which passes it to the
second stage kernel. I suppose the second stage wrapper could do some
processing on it if needed. Backward compatibility with the 2.6.16 bootloader
will probably need that.
To make it work, I need to arrange to do 64 bit HV calls from the 32 bit
wrapper. I'm not yet entirely sure how to set that up. Any suggestions
would be welcome.
-Geoff
next prev parent reply other threads:[~2007-01-29 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 3:08 [PATCH 13/16] ps3: get firmware version Geoff Levand
2007-01-27 11:30 ` Arnd Bergmann
2007-01-29 19:13 ` Geoff Levand [this message]
2007-01-29 21:22 ` 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=45BE476A.3010407@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=arnd@arndb.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.