From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Updated BGR vs. RGB vga patch...
Date: Mon, 10 Apr 2006 14:24:30 -0400 [thread overview]
Message-ID: <443AA2DE.3060908@win4lin.com> (raw)
In-Reply-To: <200604101759.34399.paul@codesourcery.com>
Here's a better patch... I can't seem to validate BGR X servers in 15 or
16-bit mode. This may not make sense (or be prevalent) on little-endian
machines anyway (I'm using VNC server on a little endian box to test
against.) In any case, 24 and 32-bit works like a charm. I use the
same basic logic as the original patch, so it's possible it was always
broken for 16-bit... especially given that most Sun X servers run in
24-bit, which is what the originators intended the patch for.
Anyway, I didn't spend time figuring out how to query SDL for the
ordering. You still have to manually pass in -bgr. The good news is
that all the computation is now done at compile-time, with only very few
tests done at run-time. I agree with your assessment of compile-time
versus run-time options... I was merely suggesting a compromise to fend
off the minor performance hit of using the old patch. But the method
you suggested is much better and that's how it's implemented now.
Thanks,
Leo Reiter
Paul Brook wrote:
> Ok. For the record I also think it's a bad idea to have features conditionally
> compiled. Either something is worth including, or we have to ask whether
> there's any point having it in qemu at all.
> The exception being debug code, which probably isn't useful unless you're
> already building qemu from source.
>
> Paul
--
Leonardo E. Reiter
Vice President of Product Development, CTO
Win4Lin, Inc.
Virtual Computing from Desktop to Data Center
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com
next prev parent reply other threads:[~2006-04-10 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 16:25 [Qemu-devel] Updated BGR vs. RGB vga patch Leonardo E. Reiter
2006-04-10 16:35 ` Paul Brook
2006-04-10 16:41 ` Leonardo E. Reiter
2006-04-10 16:46 ` Paul Brook
2006-04-10 16:48 ` Leonardo E. Reiter
2006-04-10 16:44 ` Leonardo E. Reiter
2006-04-10 16:49 ` Paul Brook
2006-04-10 16:51 ` Leonardo E. Reiter
2006-04-10 16:59 ` Paul Brook
2006-04-10 18:24 ` Leonardo E. Reiter [this message]
2006-04-10 19:08 ` malc
2006-04-10 19:11 ` Leonardo E. Reiter
2006-04-11 17:06 ` Leonardo E. Reiter
2006-04-11 17:11 ` Leonardo E. Reiter
2006-04-10 18:25 ` Leonardo E. Reiter
2006-04-10 23:12 ` Thiemo Seufer
2006-04-10 23:22 ` Leonardo E. Reiter
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=443AA2DE.3060908@win4lin.com \
--to=lreiter@win4lin.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).