From: "Natalia Portillo" <claunia@claunia.com>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] (Before) RFC for new features
Date: Sat, 10 Jul 2004 03:41:07 +0100 [thread overview]
Message-ID: <E1Bj7pt-0003pA-BV@lists.gnu.org> (raw)
In-Reply-To: <20040709204243.GA16636@jbrown.mylinuxbox.org>
Well I didn't say about using a real commercial modular BIOS, but making the
QEMU BIOS modular as the commercial ones are.
Making the first, will be a HARD task, and, Award/AMI/Phoenix/MrBIOS won't
let us to do that.
Both VMWare and VirtualPC pays for using a commercial BIOS in their
products.
> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org]
> En nombre de Jim C. Brown
> Enviado el: viernes, 09 de julio de 2004 21:43
> Para: qemu-devel@nongnu.org
> Asunto: Re: [Qemu-devel] (Before) RFC for new features
>
> 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.
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-07-10 2:43 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
2004-07-10 2:41 ` Natalia Portillo [this message]
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=E1Bj7pt-0003pA-BV@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).