From: Michael Ellerman <michael@ellerman.id.au>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 14/16] powerpc: add ps3 platform OS params support
Date: Mon, 13 Nov 2006 15:02:16 +1100 [thread overview]
Message-ID: <1163390536.7410.61.camel@localhost.localdomain> (raw)
In-Reply-To: <4557E45C.10703@am.sony.com>
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
On Sun, 2006-11-12 at 19:19 -0800, Geoff Levand wrote:
> > Is it an offset (from something) or a segment number?
> >
> >> + * @ldr_format: ldr_format flag.
> >> + * @ldr_size: Size of bootloader image in bytes.
> >
> > If these three all describe the same thing, the bootloader, it'd be good
> > if the names were similar, eg: bootloader_offset, bootloader_format,
> > bootloader_size.
>
>
> These names came from the docs. I think it would be best to keep them the
> same to avoid confusion.
I'm not sure I like that argument, if we followed it throughout the
kernel we'd have one unholy mess, but I'm not that fussed.
>
> It is not so convenient to view, but the other os area is documented in the
> iso image CELL-Linux-CL_20061110-ADDON.iso at
> http://ftp.uk.linux.org/pub/linux/Sony-PS3/.
Any chance we can get that in some sort of non-insane format? Like a
PDF? :)
> >> +static int __init verify_header(const struct header *header)
> >> +{
> >> + if (memcmp(header->magic_num, "cell_ext_os_area", 16)) {
> >> + pr_debug("%s:%d magic_num failed\n", __func__, __LINE__);
> >> + return -1;
> >> + }
> >> +
> >> + if (header->hdr_version != 1) {
> >> + pr_debug("%s:%d hdr_version failed\n", __func__, __LINE__);
> >> + return -1;
> >> + }
> >
> > Is version 2 not going to be backward compatible? Could it be >= 1 ?
>
>
> I have absolutely no clue what the next version number will be, nor the
> compatibility, etc. I'll set this when the version changes.
Except you'll have trouble changing it on the installed base of millions
of PS3s running Linux :) - At the moment if firmware bump the version on
you, you've got an unbootable system until the user does a kernel
upgrade. But it's your baby.
>
>
> >> + dump_header(header);
> >> + dump_params(params);
> >> +
> >> + os_params.rtc_diff = params->rtc_diff;
> >> + os_params.av_multi_out = params->av_multi_out;
> >> + if (0) { /* currently not used */
> >
> > Why not?
>
>
> The drivers aren't ported yet. I suppose I could take this out though.
Not fussed, but if you leave it in, expand the comment so no one else
needs to ask :)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-13 4:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 20:03 [PATCH 14/16] powerpc: add ps3 platform OS params support Geoff Levand
2006-11-13 1:29 ` Michael Ellerman
2006-11-13 3:19 ` Geoff Levand
2006-11-13 4:02 ` Michael Ellerman [this message]
2006-11-13 4:45 ` Geoff Levand
2006-11-14 1:54 ` Michael Ellerman
2006-11-14 2:05 ` Geoff Levand
2006-11-14 2:24 ` Michael Ellerman
2006-11-15 18:09 ` Christoph Hellwig
2006-11-16 8:10 ` Geoff Levand
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=1163390536.7410.61.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=geoffrey.levand@am.sony.com \
--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).