From: "J. Mayer" <l_indien@magic.fr>
To: Thiemo Seufer <ths@networkno.de>
Cc: oliver <oliver@linux-kernel.at>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu alpha?
Date: Sun, 21 Oct 2007 11:00:02 +0200 [thread overview]
Message-ID: <1192957202.16781.42.camel@rapid> (raw)
In-Reply-To: <20071020124945.GF4544@networkno.de>
On Sat, 2007-10-20 at 13:49 +0100, Thiemo Seufer wrote:
> 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
> > - 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.
> > But the first step about the Alpha target would be to properly debug the
> > linux-user-mode emulation, that would validate the core CPU INSNS
> > emulation part.
> > I guess my Alpha CPU and ABI knowledge is too restricted to find the
> > problem of most program crashing for now. It seems to me that the Unique
> > register is not initialized properly, but this is just a guess and I
> > have no idea of what's going wrong with this register and what should be
> > its value.
>
> Could you record the limitations you know about in a STATUS file and
> commit that to the target-alpha directory?
You're right. I will commit a status file today.
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-21 9:02 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 [this message]
2007-10-20 13:39 ` Daniel Jacobowitz
2007-10-21 10:43 ` Rob Landley
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=1192957202.16781.42.camel@rapid \
--to=l_indien@magic.fr \
--cc=oliver@linux-kernel.at \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).