All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: linuxppc-dev@ozlabs.org
Subject: Building ppc/powerpc kernel to run under QEMU.
Date: Wed, 9 May 2007 22:03:25 -0400	[thread overview]
Message-ID: <200705092203.26042.rob@landley.net> (raw)

I've been puttering around with my Firmware Linux project trying to add
powerpc as a supported platform.  I can build kernels that qemu can boot (such
as a "prep" kernel) using ARCH=ppc, but that one doesn't support make
headers_install.

Using ARCH=powerpc makes headers_install work, but there's no kernel .config 
I've been able to come up with that generates a kernel I can boot under qemu.

I could add a special case to my build script, but so far I've got it building 
eight targets (x86, x86-64, mips, mipsel, armv4l, armv5l, and sparc) with the 
same ARCH= for headers_install and the actual kernel compile.  It seems there 
_should_ be a way to do this for as prominent an architecture as PowerPC.

I was told this was the right place to ask: what's the status of the 
ppc->powerpc migration, and is there any known way to get ARCH=powerpc to 
build a kernel qemu can boot?

Rob

             reply	other threads:[~2007-05-10  3:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  2:03 Rob Landley [this message]
2007-05-10 17:28 ` Building ppc/powerpc kernel to run under QEMU Linas Vepstas
2007-05-10 22:07   ` Matt Sealey
2007-05-11  1:46     ` David Gibson
2007-05-12  3:30       ` Rob Landley
2007-05-12  1:46     ` Rob Landley
2007-05-12  3:00       ` Doug Maxey
2007-05-12  4:05         ` Rob Landley
2007-05-12  1:14   ` Rob Landley
2007-05-14 19:09     ` Hollis Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2007-05-09 22:39 Rob Landley
2007-05-09 23:38 ` Stephen Rothwell

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=200705092203.26042.rob@landley.net \
    --to=rob@landley.net \
    --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 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.