From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] (Before) RFC for new features
Date: Fri, 09 Jul 2004 18:32:33 +0100 [thread overview]
Message-ID: <1089394353.59382.203.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40F00D38.8050605@witch.dyndns.org>
On Sat, 2004-07-10 at 16:37, Hetz Ben Hamo wrote:
> Natalia Portillo wrote:
> > * 1 Chipset (Intel Natoma)
> >
> > We should have more?
> > If anyone can put more, great!
>
> How many chipset do you know that support Intel's Pentium Pro? Another
> chipset might require MMX/SSE support, not mentioning the BIOS support
> which is needed...
I don't think that the chipset particularly cares what extended
instructions the CPU can execute... However, BIOS support we are
definitely lacking. IIRC, the BIOS we are using doesn't do any PCI setup
- so we rely on some code in pc.c and pci.c to make the chipset look
configured and to set up the BARs.
--
Antony T Curtis <antony.t.curtis@ntlworld.com>
next prev parent reply other threads:[~2004-07-09 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 1:59 [Qemu-devel] (Before) RFC for new features Natalia Portillo
2004-07-10 15:37 ` Hetz Ben Hamo
2004-07-09 17:23 ` Natalia Portillo
2004-07-09 17:32 ` Antony T Curtis [this message]
2004-07-09 17:57 ` Natalia Portillo
2004-07-09 20:42 ` Jim C. Brown
2004-07-10 2:41 ` 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-10 20:53 ` [Qemu-devel] (Before) " Hetz Ben Hamo
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 18:14 [Qemu-devel] " Fabrice Bellard
2004-07-09 21:51 ` [Qemu-devel] (Before) " Hetz Ben Hamo
2004-07-09 9:50 ` Johannes Schindelin
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=1089394353.59382.203.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.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).