qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: andrzej zaborowski <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] VMware SVGA uses incorrect depth
Date: Fri, 27 Feb 2009 21:21:10 +0100	[thread overview]
Message-ID: <fb249edb0902271221rbafe5cahe3ec7a318271b18b@mail.gmail.com> (raw)
In-Reply-To: <49A842CD.1000306@us.ibm.com>

2009/2/27 Anthony Liguori <aliguori@us.ibm.com>:
> Brian Kress wrote:
>>
>> The VMware SVGA adapter is set to a 24 bit depth, where as the display
>> surfaces
>> (and just about everything else) are using a 32 bit depth.  So when you
>> use "-vga vmware"
>> in either the sdl or vnc displays, you get some very odd video that has
>> the wrong colors, is
>> repeated and is only over 3/4 of the screen.  Fix seems to be to change it
>> to 32 bit.  With
>> this patch I can use VMware video in both sdl and vnc and have it display
>> correctly.
>>
>>
>> Signed-off-by: Brian Kress <kressb@moose.net>
>>
>> Index: hw/vmware_vga.c
>> ===================================================================
>> --- hw/vmware_vga.c     (revision 6626)
>> +++ hw/vmware_vga.c     (working copy)
>> @@ -914,7 +914,7 @@
>>     s->width = -1;
>>     s->height = -1;
>>     s->svgaid = SVGA_ID;
>> -    s->depth = 24;
>> +    s->depth = 32;
>>     s->bypp = (s->depth + 7) >> 3;
>>
>
> I think having:
>
> s->depth = 24;
> s->bypp = 4;

I don't think hardcoding any depth is correct (not counting the
obvious performance disadvantage).  The s->depth value is what is
returned by the SVGA_REG_HOST_BITS_PER_PIXEL register, so it should be
the host's color depth if possible (may be impossible for VNC, but
easy with SDL), iirc this broke only recently.

Cheers

  reply	other threads:[~2009-02-27 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 21:27 [Qemu-devel] [PATCH] VMware SVGA uses incorrect depth Brian Kress
2009-02-19 21:55 ` [Qemu-devel] " Consul
2009-02-27 19:45 ` [Qemu-devel] " Anthony Liguori
2009-02-27 20:21   ` andrzej zaborowski [this message]
2009-03-02 11:36     ` Stefano Stabellini

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=fb249edb0902271221rbafe5cahe3ec7a318271b18b@mail.gmail.com \
    --to=balrogg@gmail.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).