From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Updated BGR vs. RGB vga patch...
Date: Mon, 10 Apr 2006 12:51:24 -0400 [thread overview]
Message-ID: <443A8D0C.4030807@win4lin.com> (raw)
In-Reply-To: <200604101749.00725.paul@codesourcery.com>
I was talking about enabling the use of the -bgr flag at compile time,
to save the check at runtime if the user doesn't even care about the
flag, not forcing the determination of the blit order altogether at
compile-time. In any case, this is moot, your clarification on how to
better implement it makes it much more clear to me and is a much better
idea. Mails to the list are a bit delayed, that's all ;)
Thanks,
Leo
Paul Brook wrote:
> On Monday 10 April 2006 17:44, Leonardo E. Reiter wrote:
>
>>Actually it should probably be made conditionally compiled for now,
>>until the VGA architecture changes to something more efficient. Would
>>you agree with that? That way, people who know they will need the hack
>>can enable it at configure/compile time, and the rest will not be affected.
>>
>>How does that sound? I'd be happy to post an updated patch that does that.
>
>
> Making it a configure option sounds a stunningly bad idea. If you're going
> down that route you may as well make all the output format selection a
> compile-time option.
>
> 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 16:51 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 [this message]
2006-04-10 16:59 ` Paul Brook
2006-04-10 18:24 ` Leonardo E. Reiter
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=443A8D0C.4030807@win4lin.com \
--to=lreiter@win4lin.com \
--cc=paul@codesourcery.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).