qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Mastracci <matt@aclaro.com>
To: fabrice@bellard.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Fix for bochs vbe issues
Date: Wed, 28 Apr 2004 20:32:34 -0600	[thread overview]
Message-ID: <1083205954.17126.1229.camel@matt> (raw)
In-Reply-To: <1083205072.17126.1214.camel@matt>

And right after I sent this message, I discovered why the shutdown
screen is corrupted:

The VBE_DISPI_ENABLED flag wasn't getting cleared internally when VBE
was disabled by the driver, causing some issues in other parts of the
code that check it:

            } else {
                /* XXX: the bios should do that */
                s->bank_offset = -0xa0000;
+               s->vbe_regs[s->vbe_index] = val;
            }

The above makes the shutdown screen appear as expected.

Matt.

On Wed, 2004-04-28 at 20:17, Matthew Mastracci wrote:
> Looks good.  The shutdown screen is still corrupted in Windows, but
> that's not a huge issue.  I think that it's expecting to be back in
> latched mode, but isn't setting it itself.  
> 
> One last thing to add - we need to ensure that the chain-4 mask is set
> when we start up VBE mode.  This will ensure that all of the planes are
> written (inserted right after your chain-4 mode change):
> 
> sr[2] |= 0x0f;
-- 
Matthew Mastracci <matt@aclaro.com>

  reply	other threads:[~2004-04-29  2:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 21:34 [Qemu-devel] Fix for bochs vbe issues Matthew Mastracci
2004-04-28 22:42 ` Fabrice Bellard
2004-04-29  2:17   ` Matthew Mastracci
2004-04-29  2:32     ` Matthew Mastracci [this message]
2004-04-29 16:03   ` Michael L Torrie
2004-04-29 19:51     ` [Qemu-devel] " Matthew Mastracci
2004-04-29 20:12       ` Lionel Ulmer
2004-04-29 20:24         ` Matthew Mastracci
2004-04-29 20:36         ` Jean-Michel POURE

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=1083205954.17126.1229.camel@matt \
    --to=matt@aclaro.com \
    --cc=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).