qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: Subject: Re: [Qemu-devel] VGA BIOS source code
Date: Tue, 1 Jun 2004 12:44:18 +0100	[thread overview]
Message-ID: <20040601124418.E25801@edinburgh.cisco.com> (raw)
In-Reply-To: <40BC18B6.9040300@fabianowski.de>; from bartosz@fabianowski.de on Tue, Jun 01, 2004 at 07:48:38AM +0200

On Tue, Jun 01, 2004 at 07:48:38AM +0200, Bartosz Fabianowski wrote:
> That seems like a good idea. Though if you are pretending to be some 
> particular chip set, you should be prepared to emulate the most weird 
> register settings that drivers could set for that chip set. So if the 
> goal is to reach close to 100% compatibility, I fear a substantial 
> subset of the entire spec for the chosen subset will have to be implemented.

and that's the reason to try and pick a simple chip...  The good thing about
the Cirrus chips,  is that (ignoring the Laguna family - '62/'64/'65) the
TrueColour ('2x) and Alpine ('3x/'4x/'80) are all basically variations on
a theme.

So one should be able to take the work provided for the non PCI version
(a '2x or '30 I guess),  and update it to be a simple PCI version.  Then
(if desired) one could morph it into later chips (video windows etc).

>From a quick glance at the datasheets and tech refs,  it looks as if
the '34 or '36 is the one to target - being early PCI supporting versions
and supporting 4M of video memory (i.e. 1024x768 @ 24 bit).  They do contain
a BitBLT,  but it's a relatively simple 2 operand (16 operations) version,
and may actually be the same op's as supported by X/Windows - need to check.

I'm not sure,  but I guess the '36 is the one to target,  as removing the
ISA and VL-bus of the '34 may make things simpler.  But the '36 BitBLT is
slightly more capable (more support at 24/32 bpp,  and seems to hang off
a FIFO).  But it may be that the '34 canonly to 1024x768 @ 16bpp.

Mind the other complexity (some may think it an advantage) is that the '36
has byte swapping PCI windows (think PPC support).

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

Well the VMware 'chip' interface is documented,  you could implement it,
however I doubt they'd be happy for you to use their drivers.

DF

  parent reply	other threads:[~2004-06-01 11:44 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
2004-06-01 11:44       ` Derek Fawcus [this message]
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=20040601124418.E25801@edinburgh.cisco.com \
    --to=dfawcus@cisco.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).