qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] update bochs vbe interface
Date: Thu, 25 Mar 2010 09:22:14 +0100	[thread overview]
Message-ID: <4BAB1D36.6030608@redhat.com> (raw)
In-Reply-To: <m3eij9s6b1.fsf@trasno.mitica>

On 03/24/10 23:28, Juan Quintela wrote:
> Humm, I think it means.  Can you migrate from a "new" vga to an old one,
> and maintain it working?

Depends on the vgabios version.

vgabios 0.6c will not support vesa gfx modes on older qemu, no matter 
whenever you started fresh or migrated to it.

> -    s->vbe_regs[VBE_DISPI_INDEX_ID] = VBE_DISPI_ID0;
> +    s->vbe_regs[VBE_DISPI_INDEX_ID] = VBE_DISPI_ID5;
> +    s->vbe_regs[VBE_DISPI_INDEX_VIDEO_MEMORY_64K] = s->vram_size / (64 * 1024);

> After migration, vbe_regs[VBE_DISPI_INDEX_ID] would have the value
> VBE_DISPI_ID5, but vbe_regs[VBE_DISPI_INDEX_VIDEO_MEMORY_64K] will have
> any random value, no?

vgabios uses both once at init time.  resetting vga will reset the vbe 
regs too.  So when migrating from new to old qemu:  Before reset vgabios 
will have the video memory size saved somewhere.  After reset ID will 
reset to ID0, and in case you are running vgabios 0.6c vesa gfx modes 
will stop working.

cheers,
   Gerd

  reply	other threads:[~2010-03-25  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 14:14 [Qemu-devel] [PATCH] update bochs vbe interface Gerd Hoffmann
2010-03-24 17:04 ` [Qemu-devel] " Juan Quintela
2010-03-24 19:44   ` Gerd Hoffmann
2010-03-24 22:28     ` Juan Quintela
2010-03-25  8:22       ` Gerd Hoffmann [this message]
2010-03-25  8:44         ` Juan Quintela
2010-03-25  9:10           ` Gerd Hoffmann
2010-03-25 12:14             ` Juan Quintela
2010-03-25 15:51               ` Gerd Hoffmann

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=4BAB1D36.6030608@redhat.com \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).