qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 16/18] console: stop using DisplayState in gfx hardware emulation
Date: Mon, 25 Mar 2013 10:55:54 +0100	[thread overview]
Message-ID: <51501F2A.9000802@web.de> (raw)
In-Reply-To: <51501D75.2090902@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]

On 2013-03-25 10:48, Gerd Hoffmann wrote:
> On 03/25/13 10:32, Jan Kiszka wrote:
>> On 2013-03-25 10:10, Gerd Hoffmann wrote:
>>> On 03/25/13 09:40, Jan Kiszka wrote:
>>>> On 2013-03-25 09:39, Gerd Hoffmann wrote:
>>>>> Hi,
>>>>>
>>>>>>> Any hints in the X server log?
>>>>>>
>>>>>> "vmwlegacy(0): Weight given (565) is inconsistent with the
>>>>>> depth (24)"
>>>>>
>>>>> Weight hints depth 16 indeed.  What depth used the server to
>>>>> run at? 16 or 24?
>>>>
>>>> 24
>>>
>>> As expected.  Puzzling where the 565 weight comes from ...
>>>
>>> Can you apply the attached patch, enable vmware_* +
>>> displaysurface_* tracepoints + send a log?
>>
>> [shrinking CC list at this chance]
> 
> Hmm, no displaysurface_* tracepoints?

Setting up a full trace was a bit too unhandy (it still lacks some
ad-hoc configuration). If you need it, I'll redo.

> 
>> read: index 1, value 0x0 read: index 2, value 0x320 read: index 3,
>> value 0x258
> 
> 800x600
> 
>> read: index 7, value 0x20
> 
> 4 bytes per pixel
> 
>> read: index 9, value 0xf800 read: index 10, value 0x7e0 read: index
>> 11, value 0x1f
> 
> 16bpp r/g/b masks.  Hmm.
> 
> No attempt to initialize the display (set res etc).  Maybe because the
> x11 server driver errors out early.
> 
> The 800x600 video mode was probably set from vgabios.  That doesn't
> explain the inconsistency though.
> 
> Do you boot with vesafb enabled?  Which video mode?  Probably 800x600?
>  What depth?

I'm booting with vga=0x314.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-03-25  9:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 10:32 [Qemu-devel] [PATCH 00/18] console: data structures overhaul Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 01/18] console: fix displaychangelisteners interface Gerd Hoffmann
2013-03-18 17:49   ` Niel van der Westhuizen
2013-03-18 18:00   ` Peter Maydell
2013-03-12 10:32 ` [Qemu-devel] [PATCH 02/18] console: kill DisplayState->opaque Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 03/18] spice: zap sdpy global Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 04/18] qxl: zap qxl0 global Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 05/18] qxl: better vga init in enter_vga_mode Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 06/18] sdl: drop dead code Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 07/18] console: rework DisplaySurface handling [vga emu side] Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 08/18] console: rework DisplaySurface handling [dcl/ui side] Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 09/18] console: add surface_*() getters Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 10/18] gtk: stop using DisplayState Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 11/18] vnc: " Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 12/18] sdl: " Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 13/18] spice: " Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 14/18] cocoa: " Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 15/18] console: zap displaystate from dcl callbacks Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 16/18] console: stop using DisplayState in gfx hardware emulation Gerd Hoffmann
2013-03-25  7:50   ` Jan Kiszka
2013-03-25  7:55     ` Gerd Hoffmann
2013-03-25  7:59       ` Jan Kiszka
2013-03-25  8:21         ` Gerd Hoffmann
2013-03-25  8:28           ` Jan Kiszka
2013-03-25  8:39             ` Gerd Hoffmann
2013-03-25  8:40               ` Jan Kiszka
2013-03-25  9:10                 ` Gerd Hoffmann
2013-03-25  9:32                   ` Jan Kiszka
2013-03-25  9:48                     ` Gerd Hoffmann
2013-03-25  9:55                       ` Jan Kiszka [this message]
2013-03-25 10:00                         ` Jan Kiszka
2013-03-25 10:37                           ` Gerd Hoffmann
     [not found]                             ` <5150572D.6090201@gmail.com>
2013-03-25 13:56                               ` Igor Mitsyanko
2013-03-25 20:30                                 ` Gerd Hoffmann
2013-03-26  0:02                                   ` BALATON Zoltan
2013-03-26  8:26                                   ` Jan Kiszka
2013-04-03 11:50                                     ` Gerd Hoffmann
2013-04-10  8:31                                       ` Jan Kiszka
2013-04-16  7:42                                         ` Gerd Hoffmann
2013-04-20 14:04                                           ` Jan Kiszka
2013-03-12 10:32 ` [Qemu-devel] [PATCH 17/18] console: zap color_table Gerd Hoffmann
2013-03-12 10:32 ` [Qemu-devel] [PATCH 18/18] console: remove ds_get_* helper functions 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=51501F2A.9000802@web.de \
    --to=jan.kiszka@web.de \
    --cc=kraxel@redhat.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).