From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: yhalperi@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFCv2] vga: VBE: report maximum VGA_MEM_SIZE memory
Date: Thu, 26 May 2011 09:46:23 +0200 [thread overview]
Message-ID: <4DDE054F.7060804@redhat.com> (raw)
In-Reply-To: <1306338965-6119-1-git-send-email-alevy@redhat.com>
On 05/25/11 17:56, Alon Levy wrote:
> When using -vga qxl the amount reported is minimally 32 MiB, making windows
> guests come up in a 16 color mode. With this change they work correctly, coming
> up with the full range of VBE supported modes.
>
> This patch changes just the reported memory size by VBE
> (VBE_DISPI_INDEX_VIDEO_MEMORY_64K) and not the actual vram_size like my
> previous try.
Patch looks fine, nevertheless I'd like to root-cause this first, even
if this is only for a better changelog entry.
cheers,
Gerd
prev parent reply other threads:[~2011-05-26 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 15:56 [Qemu-devel] [RFCv2] vga: VBE: report maximum VGA_MEM_SIZE memory Alon Levy
2011-05-26 7:46 ` Gerd Hoffmann [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=4DDE054F.7060804@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@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).