From: Meelis Roos <mroos@linux.ee>
To: linuxppc-dev@ozlabs.net
Subject: How to port PReP to arch/powerpc?
Date: Wed, 22 Aug 2007 14:50:07 +0300 (EEST) [thread overview]
Message-ID: <Pine.SOC.4.64.0708221444510.5639@math.ut.ee> (raw)
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.
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.
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2007-08-22 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 11:50 Meelis Roos [this message]
2007-08-22 12:29 ` How to port PReP to arch/powerpc? 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
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=Pine.SOC.4.64.0708221444510.5639@math.ut.ee \
--to=mroos@linux.ee \
--cc=linuxppc-dev@ozlabs.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).