From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] Looking for an SH4 QEMU-ready kernel (for TCG conversion)
Date: Sun, 31 Aug 2008 12:41:45 -0600 (MDT) [thread overview]
Message-ID: <20080831.124145.-345494437.imp@bsdimp.com> (raw)
In-Reply-To: <20080831183615.GA11830@hall.aurel32.net>
In message: <20080831183615.GA11830@hall.aurel32.net>
Aurelien Jarno <aurelien@aurel32.net> writes:
: On Sun, Aug 31, 2008 at 06:36:36PM +0200, Andreas Färber wrote:
: >
: > Am 30.08.2008 um 00:29 schrieb Aurelien Jarno:
: >
: > >On Fri, Aug 29, 2008 at 11:12:13PM +0200, Andreas Färber wrote:
: > >>Hi,
: > >>
: > >>Am 28.08.2008 um 23:17 schrieb Aurelien Jarno:
: > >>
: > >>>By the way, patches
: > >>>for the PPC and Alpha target are also welcome.
: > >>
: > >>I'd be interested in helping with ppc but I have a problem testing
: > >>such
: > >>changes: ppc-softmmu does not boot anything, ppc-linux-user does
: > >>not seem
: > >
: > >ppc-softmmu is able to boot prep kernels (-M prep), but
: > >unfortunately the
: > >support for this platform has been removed from upstream along with
: > >the
: > >ppc/ arch (since 2.6.26).
: >
: > According to Wikipedia, Debian and NetBSD still maintain PReP support.
: > http://en.wikipedia.org/wiki/PowerPC_Reference_Platform
:
: This is now mostly wrong, PReP support in Debian has been removed from
: unstable just after the release of Etch. Debian Lenny won't support it.
:
: > What's missing in QEMU's default g3bw machine that only PReP is known
: > to work? I've tested booting into Debian 4.0 r4a netinst CD (2.6.18?)
: > on a real PowerMac G3 blue&white and it works.
:
: A decent BIOS.
:
: > Does removal of "the ppc/ arch" in 2.6.26 above imply that recent
: > Linux kernels will only work on ppc64 and power?
: >
:
: The ppc/ arch is a new way of supporting both PowerPC and PowerPC64
: machines. The CPU support is the same, but it only supports machines
: that have been ported to this new arch. Theoretically it is possible
: to add PReP support to the ppc/ arch, but nobody cares anymore about
: PReP.
s=ppc/=powerpc/=g
arch/powerpc is the new way. arch/ppc is the old. Nobody bothered to
port things forward.
warner
next prev parent reply other threads:[~2008-08-31 18:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 21:17 [Qemu-devel] Looking for an SH4 QEMU-ready kernel (for TCG conversion) Aurelien Jarno
2008-08-28 23:08 ` Miklos Vajna
2008-08-29 10:07 ` Aurelien Jarno
2008-08-29 12:23 ` Shin-ichiro KAWASAKI
2008-08-29 13:33 ` Aurelien Jarno
2008-08-29 21:12 ` Andreas Färber
2008-08-29 21:53 ` Paul Brook
2008-08-30 10:23 ` [Qemu-devel] Looking for an SH4 QEMU-ready kernel Jernej Simončič
2008-08-30 13:08 ` Paul Brook
2008-08-29 22:12 ` [Qemu-devel] Looking for an SH4 QEMU-ready kernel (for TCG conversion) Miklos Vajna
2008-08-31 13:54 ` Andreas Färber
2008-08-29 22:29 ` Aurelien Jarno
2008-08-31 16:36 ` Andreas Färber
2008-08-31 18:36 ` Aurelien Jarno
2008-08-31 18:41 ` M. Warner Losh [this message]
2008-08-31 18:54 ` Blue Swirl
2008-08-31 18:59 ` Aurelien Jarno
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=20080831.124145.-345494437.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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).