From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, jakub@jermar.eu
Subject: Re: [Qemu-devel] status of sparc64 port
Date: Wed, 16 May 2007 21:15:58 +0300 [thread overview]
Message-ID: <f43fc5580705161115m6ca02d21y743bab28c481fe3a@mail.gmail.com> (raw)
In-Reply-To: <464B3B8E.80503@jermar.eu>
> can someone summarize the status of the sparc64 port for me?
> I'd be especially interested in having an opensource simulator of some
> UltraSPARC II/UltraSPARC IIi based machines (like Ultra 5 or Ultra 60,
> even Sun Blades with UltraSPARC IIe and IIi).
>
> What is the biggest showstopper for including full sparc64 support in
> qemu releases?
>
> Thanks for your answer and please respond directly to me as I don't read
> qemu-devel.
This is almost a FAQ. Please see
http://article.gmane.org/gmane.comp.bios.openbios/554
prev parent reply other threads:[~2007-05-16 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 17:12 [Qemu-devel] status of sparc64 port Jakub Jermar
2007-05-16 18:15 ` Blue Swirl [this message]
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=f43fc5580705161115m6ca02d21y743bab28c481fe3a@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=jakub@jermar.eu \
--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).