From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Purpose of Cirrus VGA BIOS
Date: Tue, 08 Jun 2004 04:14:59 +0100 [thread overview]
Message-ID: <1086664499.13855.353.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40C4F3ED.7050205@fabianowski.de>
On Tue, 2004-06-08 at 00:02, Bartosz Fabianowski wrote:
> Hi all
>
> I am trying to figure out how the new Cirrus emulation works. One thing
> I am still not sure about is the purpose of the Cirrus BIOS. The
> emulation coded inside QEMU seems to be trapping the graphics card
> interrupt as well as port and memory accesses. It also performs lots of
> operations and reacts to registers being changed or the interrupt being
> invoked. So, what exactly is the purpose of the graphics card BIOS in
> this scenario? What purpose does it serve? Obviously, a real Cirrus BIOS
> contains lots of code that would control a real Cirrus graphics card and
> that is totally unnecessary in QEMU. What other stuff does it contain
> that can't be done in native C code?
For starters, the real Cirrus BIOS would initialize the reserved
scratchpad registers (they do have specific uses even if it is not fully
documented).
As an aside, looking at the ROP codes, I have worked out the
relationship of what the bits mean...
ROP[0] for bit 0
ROP[1] for bit 1
etc
DST = ((ROP[0] & SRC) | ROP[1]) & ((ROP[2] & DST) | (ROP[3] & ~DST))
& ((ROP[4] & ~SRC) | ROP[5]) & ~((ROP[6] & ~DST) | (ROP[7] & DST));
--
Antony T Curtis <antony.t.curtis@ntlworld.com>
prev parent reply other threads:[~2004-06-08 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 23:02 [Qemu-devel] Purpose of Cirrus VGA BIOS Bartosz Fabianowski
2004-06-08 3:14 ` Antony T Curtis [this message]
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=1086664499.13855.353.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.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).