All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: Rob Landley <rob@landley.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Porting "prep" from ppc to powerpc.
Date: Mon, 28 May 2007 09:55:07 +0200	[thread overview]
Message-ID: <20070528075507.GA6633@iram.es> (raw)
In-Reply-To: <200705252238.39819.rob@landley.net>

On Fri, May 25, 2007 at 10:38:39PM -0400, Rob Landley wrote:
> Is anyone already doing this?  

I'm interested but I don't have the time right now.

> I asked around here a few weeks ago and got the 
> advice:
> 
> > In theory.. copy the files from ppc/platforms/prep.* to
> > powerpc/platforms/prep/ 
> > and make some Kconfigs and see what breaks :)
> 
> Unfortunately, there isn't a ppc/platforms/prep.  Under arch/ppc there's:
> 
> ./boot/simple/misc-prep.c
> ./boot/simple/prepmap.c
> ./boot/utils/mkprep.c
> ./configs/prep_defconfig
> ./platforms/prep_pci.c
> ./platforms/prep_setup.c
> ./syslib/prep_nvram.c
> 
> And I'm not sure which are relevant.  Any hints?

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).


	Gabriel

  parent reply	other threads:[~2007-05-28  7:55 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 [this message]
2007-05-28  8:23   ` Benjamin Herrenschmidt
2007-05-28  8:46     ` Gabriel Paubert
2007-05-28  9:22       ` Benjamin Herrenschmidt
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=20070528075507.GA6633@iram.es \
    --to=paubert@iram.es \
    --cc=linuxppc-dev@ozlabs.org \
    --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 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.