From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Hollis Blanchard <hollisb@us.ibm.com>
Subject: [Qemu-devel] 440 emulation?
Date: Mon, 16 Mar 2009 14:05:36 -0500 [thread overview]
Message-ID: <200903161405.37420.rob@landley.net> (raw)
I'm trying to come up with a working 440 toolchain and root filesystem, and I
think I've built one (--with-cpu=440 for the binutils and gcc config seems to
be the magic), but my attempt to test it under qemu with -M bamboo led to an
"Unable to initialize CPU" message, because apparently the 440 isn't actually
supported.
I tried feeding in "-cpu 405" in hopes of getting something to at least launch
(that's what the source code does when it's using kvm, anyway), but it still
said it couldn't initialize the cpu.
Presumably this works for somebody, but I dunno how to get it to do anything
interesting. What is the status of the bamboo board?
Rob
next reply other threads:[~2009-03-16 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 19:05 Rob Landley [this message]
2009-03-16 19:15 ` [Qemu-devel] Re: 440 emulation? Hollis Blanchard
2009-03-16 19:41 ` Rob Landley
2009-03-16 20:00 ` Hollis Blanchard
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=200903161405.37420.rob@landley.net \
--to=rob@landley.net \
--cc=hollisb@us.ibm.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).