From: Antonino Daplas <adaplas@pol.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: LCD scaling type
Date: 11 Jan 2003 21:27:35 +0800 [thread overview]
Message-ID: <1042291653.1389.88.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.21.0301111428410.18570-100000@vervain.sonytel.be>
On Sat, 2003-01-11 at 21:29, Geert Uytterhoeven wrote:
> On 11 Jan 2003, Antonino Daplas wrote:
> > I also have a couple of things that come to mind (like switching from
> > truecolor to directcolor and vice versa without rebooting). I currently
> > use var->nonstd which is probably not the the right thing to do.
>
> Since directcolor is a superset of truecolor, shouldn't a driver always use
> directcolor, if the hardware supports it?
>
Some apps don't know how to treat directcolor. DirectFB-0.9.15 is
messed up when visual is in directcolor, so I need truecolor here. I
submitted a patch to them so it should get fixed with their next
release.
However, when I go to X, I want it to be in directcolor, for gamma
utilities to work
Tony
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-01-11 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 19:42 LCD scaling type Benjamin Herrenschmidt
2003-01-11 6:58 ` Antonino Daplas
2003-01-11 9:47 ` Benjamin Herrenschmidt
2003-01-11 10:16 ` Antonino Daplas
2003-01-11 11:08 ` Benjamin Herrenschmidt
2003-01-11 11:35 ` Antonino Daplas
2003-01-11 12:08 ` Benjamin Herrenschmidt
2003-01-11 12:42 ` Antonino Daplas
2003-01-11 13:29 ` Geert Uytterhoeven
2003-01-11 13:27 ` Antonino Daplas [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=1042291653.1389.88.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).