qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Mark" <markk@clara.co.uk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Cirrus issues
Date: Mon, 1 Jul 2013 16:16:41 +0100	[thread overview]
Message-ID: <a520e848d6932fd2957a0d9b35f7840c.squirrel@ssl-webmail-vh.clara.net> (raw)

Hi,

The developer of WinUAE has been adding support for Cirrus-based graphics
cards to the program, based on the Qemu Cirrus emulation. Apparently he
has discovered some bugs, which I thought I'd post about here in case
someone who knows about that code wants to take a look.

[begin quote]

Graphics glitches are actually caused by bug in cirrus logic blitter
emulation, it has incorrect "blit is outside of vram" tests, it assumes
all blits are normal copy blits, for example it can incorrectly reject
color expansion blits (used by RectFill).

Because I am too lazy to create logins to qemu bugtracker or mailing list,
at least not yet, here are bugs I have found:

cirrus_vga.c: BLTUNSAFE() macro is broken. (Graphics glitches are gone if
I uncomment them all, of course it can introduce crashes if there are
actual invalid blits..)

cirrus_vga.c: cirrus_do_copy() "extra x, y", s->cirrus_blt_srcpitch or
s->cirrus_blt_dstpitch can be zeros: division by zero.

CIRRUS_BLT_STATUS bit was missing. PicassoII driver polls this to check if
blit has finished.

And one thing that may not be a bug:

vga.c: vga_draw_graphic() seems to assume shift_control =
(s->gr[VGA_GFX_MODE] >> 5) & 3; must be >=2 (bit 6 of Mode Register is
"256 color mode") or it uses standard VGA graphics mode, even if cirrus
extended registers are used to enabled extended (SVGA) modes. My
workaround was to set bit 6 when any extended mode is enabled.

[end quote]

Original forum posting URL: http://eab.abime.net/896935-post30.html

Regards,
-- Mark

                 reply	other threads:[~2013-07-01 15:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a520e848d6932fd2957a0d9b35f7840c.squirrel@ssl-webmail-vh.clara.net \
    --to=markk@clara.co.uk \
    --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).