qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] (Before) RFC for new features
Date: Fri, 9 Jul 2004 16:42:43 -0400	[thread overview]
Message-ID: <20040709204243.GA16636@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <E1Bizej-0008JG-Jd@lists.gnu.org>

On Fri, Jul 09, 2004 at 06:57:21PM +0100, Natalia Portillo wrote:
> 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. 
> 

A modular BIOS designed for qemu is ok (e.g. VGABios vs Bochs BIOS vs
some other hand-written BIOS) but supporting a commercial BIOS written
for actual hardware is another matter. This is very difficult as such a BIOS
will expect different hardware in different places. Not to mention adding support
for different types of motherboards/ROM chips. Its easier to just fix the
current qemu BIOS.

P.S.

Someone is working on that iirc.... posted to the list a while back. They
loaded qemu directly from a bootloader (so there was no host OS, only a guest
OS) and did some hacking so qemu could access the host BIOS directly. So it
is possible, just very hard.

> > 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>

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2004-07-09 20:45 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
2004-07-09 20:42       ` Jim C. Brown [this message]
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=20040709204243.GA16636@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --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).