linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@ozlabs.org, Rob Landley <rob@landley.net>
Subject: Re: Porting "prep" from ppc to powerpc.
Date: Mon, 28 May 2007 19:22:00 +1000	[thread overview]
Message-ID: <1180344121.19517.70.camel@localhost.localdomain> (raw)
In-Reply-To: <20070528084652.GA7686@iram.es>

On Mon, 2007-05-28 at 10:46 +0200, Gabriel Paubert wrote:
> On Mon, May 28, 2007 at 06:23:34PM +1000, Benjamin Herrenschmidt wrote:
> > On Mon, 2007-05-28 at 09:55 +0200, Gabriel Paubert wrote:
> > > I was thinking of writing a bootwrapper that would
> > > convert residual data to flat device tree. There
> > > is a lot of valuable information in the residual data,
> > > like the interrupt routing (which is correct if you 
> > > can read the spec, which is not what the code in
> > > arch/ppc did). 
> > 
> > We were wondering the other day how reliable the residual data are...
> > 
> 
> On the boards I use, they are very good. And there is some information
> (memory size, tb and cpu freq, etc...) that I'd rather take from the 
> residual data than trying to guess.
> 
> > David Gibson's been toying with that too already, you should sync with
> > him. 
> 
> I've not yet started to write anything (finishing a hardware project).

Ok, well, anyway, that's good to know that they are good.

Ben.

  reply	other threads:[~2007-05-28  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  2:38 Porting "prep" from ppc to powerpc Rob Landley
2007-05-27 23:20 ` David Gibson
2007-05-29 21:16   ` Rob Landley
2007-05-28  7:55 ` Gabriel Paubert
2007-05-28  8:23   ` Benjamin Herrenschmidt
2007-05-28  8:46     ` Gabriel Paubert
2007-05-28  9:22       ` Benjamin Herrenschmidt [this message]
2007-05-29 21:02   ` Rob Landley
2007-05-30 11:19     ` 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=1180344121.19517.70.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paubert@iram.es \
    --cc=rob@landley.net \
    /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).