From: Rob Landley <rob@landley.net>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Porting "prep" from ppc to powerpc.
Date: Tue, 29 May 2007 17:02:54 -0400 [thread overview]
Message-ID: <200705291702.55060.rob@landley.net> (raw)
In-Reply-To: <20070528075507.GA6633@iram.es>
On Monday 28 May 2007 3:55 am, Gabriel Paubert wrote:
> 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'm interested but don't have the expertise.
I don't have prep documentation, I'm not familiar with the internals of the
powerpc architecture (beyond the endianness/word size/alignment checklist for
porting userspace programs from arch to arch), I know just enough about Open
Firmware to really dislike it, and I don't actually have prep hardware. I do
have qemu, but it doesn't actually work even with the old ARCH=ppc prep
kernels. It segfaults trying to decompress them.
I was hoping to use a prep kernel to debug qemu, but my build system (which
already builds several other architecutres from the same script) can't do
ARCH=ppc because that doesn't understand "make headers_install", so I have to
build them by hand supplying different architectures at different steps of
the process. Which puts it waaaaay down on my todo list.
Fixing the Linux build system to actually work for prep would be nice, but it
sounds like teaching ARCH=ppc to do "make headers install" would be a couple
orders of magnitude easier...
Rob
next prev parent reply other threads:[~2007-05-29 21:03 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
2007-05-29 21:02 ` Rob Landley [this message]
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=200705291702.55060.rob@landley.net \
--to=rob@landley.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paubert@iram.es \
/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).