qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: Subject: Re: [Qemu-devel] VGA BIOS source code
Date: Tue, 01 Jun 2004 12:30:16 +0200	[thread overview]
Message-ID: <40BC5AB8.3060304@bellard.org> (raw)
In-Reply-To: <40BC18B6.9040300@fabianowski.de>

Bartosz Fabianowski wrote:
>> Is there a reasons for the a c b ordering?
> 
> 
> No ;)
> 
>> I think you are probably a little harsh on this code.  It may be 
>> far from perfect, but it does (mostly) work.
> 
> 
> Yes, it does work. Maybe I was a bit harsh in my wording after 
> wasting a day on it, sorry.

Yes, and if you think about it longer, you will see the benefit of the
Bochs VESA VBE layer. It is one of the simplest implementation
you can think of.

The VMware driver idea is just an extension of it to add some
acceleration primitives, and of course it is much more complicated.
Adding real hardware support (such as a Cirrus Logic VGA card) will also
be more complicated than the Bochs VESA VBE layer.

> Since my main interest is in running Windows inside QEMU, I could 
> also envision adding another driver later, similar to what is done in
> VMWare. It would be a windows driver that acts as a dumb stub and 
> forwards every request to the dumb side. Since it would be designed 
> from the ground up only for QEMU, it could be limited in its
> functionality to really only being a frame buffer and nothing else.
> This would probably accelerate the emulation quite a bit.

It is already done for NT (read the faq), at least for a linear frame 
buffer.

Fabrice.

  reply	other threads:[~2004-06-01 10:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 20:00 Subject: Re: [Qemu-devel] VGA BIOS source code Bob Barry
2004-05-31 20:17 ` Bartosz Fabianowski
2004-06-01  4:14   ` Kyle Hayes
2004-06-01  5:48     ` Bartosz Fabianowski
2004-06-01 10:30       ` Fabrice Bellard [this message]
2004-06-01 11:44       ` Derek Fawcus
2004-06-01 18:05         ` Bartosz Fabianowski
2004-06-01 19:09           ` John R. Hogerhuis
2004-06-01 20:53             ` Derek Fawcus
2004-06-01 21:51           ` Hetz Ben Hamo
2004-06-01 22:23             ` Jan Fabianowski
2004-06-02  8:28               ` Johannes Schindelin
2004-06-02  9:19                 ` Bartosz Fabianowski
2004-06-01 18:42         ` Daniel Serpell
2004-06-01 20:46           ` Derek Fawcus
2004-06-01 20:59             ` Daniel Serpell
  -- strict thread matches above, loose matches on Subject: below --
2004-06-02 11:41 Vladimir N. Oleynik

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=40BC5AB8.3060304@bellard.org \
    --to=fabrice@bellard.org \
    --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).