All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Natalia Portillo" <claunia@claunia.com>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] (Before) RFC for new features
Date: Fri, 9 Jul 2004 18:57:21 +0100	[thread overview]
Message-ID: <E1Bizej-0008JG-Jd@lists.gnu.org> (raw)
In-Reply-To: <1089394353.59382.203.camel@pcgem.rdg.cyberkinetica.com>

About the BIOS question we should have a modular BIOS.

Like AWARD, AMI, Phoenix, etc, BIOS, that have support for a great variety
of chipsets and CPUs, and are compiled with required modules for each
motherboard. 

> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org 
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org] 
> En nombre de Antony T Curtis
> Enviado el: viernes, 09 de julio de 2004 18:33
> Para: qemu-devel@nongnu.org
> Asunto: Re: [Qemu-devel] (Before) RFC for new features
> 
> 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>
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2004-07-09 17:59 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
2004-07-09 17:57     ` Natalia Portillo [this message]
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=E1Bizej-0008JG-Jd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.