linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Porting "prep" from ppc to powerpc.
Date: Tue, 29 May 2007 17:16:52 -0400	[thread overview]
Message-ID: <200705291716.53090.rob@landley.net> (raw)
In-Reply-To: <20070527232055.GA23768@localhost.localdomain>

On Sunday 27 May 2007 7:20 pm, David Gibson wrote:
> On Fri, May 25, 2007 at 10:38:39PM -0400, Rob Landley wrote:
> > Is anyone already doing this?  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 :)
> 
> Actually, I don't really recommend that method in any case.
> 
> Instead I suggest making a Kconfig under arch/powerpc, then adding
> things until it builds, then adding things until it boots.  When you
> need to know what has to be done at a particular point, consult
> arch/ppc.

So study the old code until I figure out what should be in the Kconfig, 
what "things" to add for it to build, and what "things" to add until it 
boots.  And the hint as to where to start is...  study the old code.

Right.  Copying the old implementation to the new directory and debugging it 
sounded like something I might be able to do.  Starting from scratch?  Not so 
much.

Rob

  reply	other threads:[~2007-05-29 21:16 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 [this message]
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
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=200705291716.53090.rob@landley.net \
    --to=rob@landley.net \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.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).