From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] gtk UI doesn't correctly byte swap 32-bit framebuffer on qemu-system-ppc little-endian host
Date: Tue, 04 Jun 2013 09:52:40 +0100 [thread overview]
Message-ID: <51ADAAD8.1070304@ilande.co.uk> (raw)
In-Reply-To: <51AD9C35.4060001@redhat.com>
On 04/06/13 08:50, Gerd Hoffmann wrote:
> On 06/04/13 01:19, Anthony Liguori wrote:
>> Mark Cave-Ayland<mark.cave-ayland@ilande.co.uk> writes:
>>
>>> Hi all,
>>>
>>> I've just been testing some more OpenBIOS images with the new gtk UI and
>>> found that if you specify a 32-bit depth framebuffer on qemu-system-ppc
>>> running on a little-endian host then the RGB -> BGR byteswap doesn't
>>> take place.
>>>
>>> Good:
>>> ./qemu-system-ppc -g 1024x768x32 -vnc :1
>>> ./qemu-system-ppc -g 1024x768x32 -sdl
>>>
>>> Bad:
>>> ./qemu-system-ppc -g 1024x768x32
>>
>> cairo has a pretty limited number of modes that it supports.
>>
>> I guess we could use pixman to do the conversion. Gerd, is that the
>> right approach?
>
> Hmm, looks like we can't pass pixman format values to cairo, even though
> cairo uses pixman under the hood. So, yes, we must convert and using
> pixman is the easiest way to get the job done.
>
>> Is there a way I can force the display API to do the
>> conversion for me?
>
> No, but asking pixman to do it is easy, see attached patch.
Hi Gerd,
A quick test of the patch shows that it solves the problem here - thanks
a lot!
ATB,
Mark.
prev parent reply other threads:[~2013-06-04 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 22:35 [Qemu-devel] gtk UI doesn't correctly byte swap 32-bit framebuffer on qemu-system-ppc little-endian host Mark Cave-Ayland
2013-06-03 23:19 ` Anthony Liguori
2013-06-04 7:50 ` Gerd Hoffmann
2013-06-04 8:52 ` Mark Cave-Ayland [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=51ADAAD8.1070304@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.