From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: paul@codesourcery.com
Subject: [Qemu-devel] [PATCH] Initialize the VMware VGA console after vga_init
Date: Tue, 08 Jul 2008 16:15:47 +0200 [thread overview]
Message-ID: <48737693.5030300@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Hi,
while trying the -vmwarevga switch I stumbled across this nifty problem:
vga_common_init calls vga_reset, which memsets the whole VGAState to 0.
Unfortunately the console initialization code is before that, so it gets
overwritten by 0 which breaks later on.
To circumvent this I reordered the console initialization to after the
vga_init. I am not 100% sure if that's correct, but it works so far.
Please double-check if this is the right approach.
Alex
Signed-off-by: Alexander Graf <agraf@suse.de>
[-- Attachment #2: qemu-vmwarevga.patch --]
[-- Type: text/x-patch, Size: 952 bytes --]
Index: hw/vmware_vga.c
===================================================================
--- hw/vmware_vga.c (revision 4852)
+++ hw/vmware_vga.c (working copy)
@@ -1123,16 +1123,16 @@
vmsvga_reset(s);
- s->console = graphic_console_init(ds, vmsvga_update_display,
- vmsvga_invalidate_display,
- vmsvga_screen_dump,
- vmsvga_text_update, s);
-
#ifdef EMBED_STDVGA
vga_common_init((VGAState *) s, ds,
vga_ram_base, vga_ram_offset, vga_ram_size);
vga_init((VGAState *) s);
#endif
+
+ s->console = graphic_console_init(ds, vmsvga_update_display,
+ vmsvga_invalidate_display,
+ vmsvga_screen_dump,
+ vmsvga_text_update, s);
}
static void pci_vmsvga_save(QEMUFile *f, void *opaque)
next reply other threads:[~2008-07-08 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 14:15 Alexander Graf [this message]
2008-07-08 16:44 ` [Qemu-devel] [PATCH] Initialize the VMware VGA console after vga_init Rick Vernam
2008-07-11 14:25 ` Filip Navara
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=48737693.5030300@suse.de \
--to=agraf@suse.de \
--cc=paul@codesourcery.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).