From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: oliver <oliver@linux-kernel.at>
Subject: Re: [Qemu-devel] qemu alpha?
Date: Sun, 21 Oct 2007 05:43:14 -0500 [thread overview]
Message-ID: <200710210543.14960.rob@landley.net> (raw)
In-Reply-To: <1192870572.16781.29.camel@rapid>
On Saturday 20 October 2007 3:56:12 am J. Mayer wrote:
> On Fri, 2007-10-19 at 19:49 -0500, Rob Landley wrote:
> > On Sunday 14 October 2007 5:14:27 am J. Mayer wrote:
> > > On Sun, 2007-10-14 at 11:19 +0200, Oliver Falk wrote:
> > > > Hi list!
> > >
> > > Hi you !
> > >
> > > > Just wanted to know how far the progress on alpha target is? I would
> > > > be happy if I have some 'virtual alpha' to test new isos.
> > > >
> > > > If I can help some way (I have a few alphas around). Let me know.
> > >
> > > I'm happy to see someone interresting in improving Alpha support, which
> > > is .... very alpha for now !
> >
> > I'm interested in testing Alpha too, but I haven't seem a
> > qemu-system-alpha show up yet. Alas, I have no hardware or specific
> > expertise in this platform, I'm just trying to build and boot Linux
> > kernels (and corresponding root filesystems) on as many emulated target
> > platforms as I can.
>
> There are a lot of things missing for qemu-system-alpha to be available:
> - the PALCode emulation is far from being complete or even usable
I have no idea what that is.
> - there is no hardware machine emulation for Alpha in Qemu.
> As I have no Alpha platform, I don't know much about the hardware to be
> emulated.
I do know that the ev6 bus is the same as the Athlon used.
When Compaq bought the corpse of DEC back in the mid-90's, they weren't
interested in their chip designers, so AMD scooped up most of the Alpha
design team. AMD then asked them "ok, if you guys were going to design an
x86 compatible processor, what would it look like?" The result was the
Athlon back around 1997. You could actually stick one in an Alpha
motherboard, and the only reason it wouldn't boot is the bios was alpha
machine language instead of x86 code. Everything else was the same, because
it's what the designers were familiar with.
So if you slap an Alpha in a virtual x86-64 PC motherboard, you're not too far
off.
Here's one spec:
http://web.archive.org/web/19990913123756/http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-10-21 10:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 9:19 [Qemu-devel] qemu alpha? Oliver Falk
2007-10-14 10:14 ` J. Mayer
2007-10-20 0:49 ` Rob Landley
2007-10-20 8:56 ` J. Mayer
2007-10-20 12:49 ` Thiemo Seufer
2007-10-21 9:00 ` J. Mayer
2007-10-20 13:39 ` Daniel Jacobowitz
2007-10-21 10:43 ` Rob Landley [this message]
2007-10-21 10:55 ` Paul Brook
2007-10-22 7:39 ` Oliver Falk
2007-10-21 11:06 ` J. Mayer
2007-10-22 7:43 ` Oliver Falk
2007-10-22 22:38 ` J. Mayer
2007-10-23 13:01 ` Brian Wheeler
2007-10-22 7:38 ` Oliver Falk
2007-10-20 8:59 ` Sunil Amitkumar Janki
2007-10-25 23:21 ` Rob Landley
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=200710210543.14960.rob@landley.net \
--to=rob@landley.net \
--cc=oliver@linux-kernel.at \
--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).