From: "Natalia Portillo" <claunia@claunia.com>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] RFC for new features
Date: Fri, 9 Jul 2004 20:28:47 +0100 [thread overview]
Message-ID: <E1Bj1Cb-00049t-SR@lists.gnu.org> (raw)
In-Reply-To: <1089399858.29409.119.camel@jma1.dev.netgem.com>
Hi
> > Select what CPU we want to emulate.
> > For example under the x86 emulation, what if I want to run a system
> > that does not work with the current emulated CPU (Pentium Pro) but
> > does with an older one (for example a 486DX4).
> > Also in PowerPC emulation, it should be interesting as the 601 has
> > opcodes that no other 6xx/7xx PowerPC have (that are from POWER).
>
> I agree with this.
>
> I wonder if the best is to choose the CPU (ie 601/603/604/G3/G4 for
> PPC...) or to choose a coherent hw entity (PowerMac G3, ...).
> I think the first approach is good for ones who want to
> emulate exotic hardware configurations but the second is more
> usable for end-users.
What about both?
> The good approach may be to be able to select all motherboard
> components but have some predefined templates that describes
> well known motherboards.
Yeah.
And think that in PowerMacintosh emulation, there can be almost identically
motherboards, but are a different computer (check Gestalt value, and OF one,
both says the computer model).
next prev parent reply other threads:[~2004-07-09 19:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 20:50 [Qemu-devel] RFC for new features Natalia Portillo
2004-07-08 22:48 ` Natalia Portillo
2004-07-09 19:04 ` Jocelyn Mayer
2004-07-09 19:28 ` Natalia Portillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 2:41 [Qemu-devel] (Before) " Natalia Portillo
2004-07-10 13:10 ` Fabrice Bellard
2004-07-10 14:03 ` [Qemu-devel] " Fabrice Bellard
2004-07-10 14:47 ` Antony T Curtis
2004-07-10 14:57 ` Fabrice Bellard
2004-07-08 19:19 Thomas Munn
2004-07-09 10:02 ` Johannes Schindelin
2004-07-09 10:34 ` Julian Seward
2004-07-08 18:14 Fabrice Bellard
2004-07-08 18:54 ` Antony T Curtis
2004-07-08 19:36 ` Jim C. Brown
2004-07-08 20:31 ` Jernej Simončič
2004-07-08 21:04 ` Jim C. Brown
2004-07-08 22:37 ` Jernej Simončič
2004-07-08 22:57 ` Jim C. Brown
2004-07-08 19:45 ` Jocelyn Mayer
2004-07-08 19:00 ` Karel Gardas
2004-07-08 21:44 ` vaise
2004-07-08 19:30 ` Jean-Michel POURE
2004-07-08 19:48 ` Brad Watson
2004-07-08 21:37 ` Jan Dittmer
2004-07-08 22:24 ` malc
2004-07-08 19:35 ` Jim C. Brown
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=E1Bj1Cb-00049t-SR@lists.gnu.org \
--to=claunia@claunia.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).