From: David Gibson <david@gibson.dropbear.id.au>
To: Josh Boyer <jwboyer@jdub.homelinux.org>
Cc: Meelis Roos <mroos@linux.ee>, linuxppc-dev@ozlabs.net
Subject: Re: How to port PReP to arch/powerpc?
Date: Thu, 23 Aug 2007 13:37:03 +1000 [thread overview]
Message-ID: <20070823033703.GK7042@localhost.localdomain> (raw)
In-Reply-To: <20070822072956.56b7df46@vader.jdub.homelinux.org>
On Wed, Aug 22, 2007 at 07:29:56AM -0500, Josh Boyer wrote:
> On Wed, 22 Aug 2007 14:50:07 +0300 (EEST)
> Meelis Roos <mroos@linux.ee> wrote:
>
> > It seems no one cares for arch/ppc any more but the move to powerpc was
> > not finished completely (PReP subarch was not migrated but sees users, I
> > do not know about the user base of the other subarches). So I have been
> > thinking about migrating PReP support to arch/powerpc myself since I use
> > it.
>
> The merge is still on-going. So it's not "finished" at all.
>
> > Any general guidelines or specific hints about that? I have looked
> > around in the code and some pieces are clearly PReP specific (setup,
> > pci, boot) but others seem wuite a bit mixed up with other subarches.
>
> David Gibson and Rob Landley had a quite interesting discussion about
> PReP last night on IRC. You might want to contact them and see if they
> came to any conclusions.
Yes, my draft PReP support patch, tweaked this morning to build again
(changes roughly identical to Rob Landley's patch, I believe) is at:
http://ozlabs.org/~dgibson/home/tmp/prep-support
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-08-23 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 11:50 How to port PReP to arch/powerpc? Meelis Roos
2007-08-22 12:29 ` Josh Boyer
2007-08-22 16:19 ` Linas Vepstas
2007-08-22 15:27 ` Olof Johansson
2007-08-22 16:26 ` Josh Boyer
2007-08-23 3:37 ` David Gibson [this message]
2007-08-22 13:04 ` Sven Luther
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=20070823033703.GK7042@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=jwboyer@jdub.homelinux.org \
--cc=linuxppc-dev@ozlabs.net \
--cc=mroos@linux.ee \
/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).