From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>, Milton Miller <miltonm@bga.com>
Subject: Re: [Qemu-devel] I got a kernel booted under qemu-system-ppc !
Date: Sun, 21 Oct 2007 04:55:50 -0500 [thread overview]
Message-ID: <200710210455.51059.rob@landley.net> (raw)
In-Reply-To: <1192870252.16781.22.camel@rapid>
On Saturday 20 October 2007 3:50:52 am J. Mayer wrote:
> Sleep mode is currently implemented only for a few CPUs. I should add
> all the currently emulated cores. For this, I would have to emulate the
> HID registers, in most case, which is still not done.
Getting it to exit in response to a shut down attempt would be really nice
too. (It may already do so, but I have no idea how to trigger it and neither
did Milton last I checked.)
> And you can get the list of all CPUs emulated by Qemu with the '-cpu ?'
> switch.
I did that, but it -cpu ? gives output like:
PowerPC 7448 PVR 80040201
PowerPC 7448v1.0 PVR 80040100
PowerPC 7448v1.1 PVR 80040101
PowerPC 7448v2.0 PVR 80040200
PowerPC 7448v2.1 PVR 80040201
I prefer the result of "-M ?" which makes it slightly clearer which field you
need to feed qemu as an argument. (For the record, -cpu seems to want filed
$2 of the -cpu ? output.) Also, that doesn't tell me what the differences
between any of them are.
From earlier research, I know that if you configure a toolchain for "7xx" all
major PowerPC variants except two will run that, it's more or less "-mcpu
386" of the powerpc world.
The two that won't run it (Motorola's 8xx and IBM's 4xx) are both embedded
subsets of powerpc that have had instructions removed, and thus need their
own toolchains. (Of course those two removed DIFFERENT instructions,
sigh...)
My random and confused notes about various hardware platforms are
at "http://landley.net/ols/ols2007/platforms.txt", which has a largeish
section on ppc that probably makes sense to nobody but me. :)
I don't actually have any _background_ in embedded hardware. Busybox, uClibc,
and qemu all dragged me into it, and I've been trying to pick things up as I
go along...
Rob
P.S. I removed you from the CC: list because your ISP is still bouncing my
emails as spam, and I don't know if the list sends you a copy if you're cc'd.
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-10-21 9:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 0:12 [Qemu-devel] I got a kernel booted under qemu-system-ppc ! Rob Landley
2007-10-18 23:46 ` J. Mayer
2007-10-19 17:57 ` Milton Miller
2007-10-23 9:17 ` J. Mayer
2007-10-19 6:00 ` [Qemu-devel] " Milton Miller
2007-10-19 15:03 ` [Qemu-devel] " Aurelien Jarno
2007-10-19 15:19 ` Aurelien Jarno
2007-10-19 17:39 ` Jocelyn Mayer
2007-10-19 18:10 ` Milton Miller
2007-10-19 19:39 ` Aurelien Jarno
2007-10-19 20:33 ` Aurelien Jarno
2007-10-20 6:08 ` Rob Landley
2007-10-20 8:50 ` J. Mayer
2007-10-21 9:55 ` Rob Landley [this message]
2007-10-21 10:24 ` J. Mayer
2007-10-21 12:28 ` J. Mayer
2007-10-21 22:37 ` Rob Landley
2007-10-20 14:23 ` Aurelien Jarno
2007-10-20 14:49 ` Aurelien Jarno
2007-10-20 21:49 ` Aurelien Jarno
2007-10-21 9:01 ` J. Mayer
2007-10-20 7:52 ` Rob Landley
2007-10-20 9:03 ` J. Mayer
2007-10-20 9:42 ` 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=200710210455.51059.rob@landley.net \
--to=rob@landley.net \
--cc=aurelien@aurel32.net \
--cc=miltonm@bga.com \
--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).