From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Linux/m68k on Mac <linux-mac68k@mac.linux-m68k.org>,
Andrew Morton <akpm@osdl.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 10/12] fbdev: Static pseudocolor with depth less than 4 does exist
Date: Sat, 29 Apr 2006 20:34:15 +0800 [thread overview]
Message-ID: <44535D47.5060000@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0604290935310.4557@pademelon.sonytel.be>
Geert Uytterhoeven wrote:
> On Sat, 29 Apr 2006, Antonino A. Daplas wrote:
>> A static pseudocolor visual with depth less than 4 does exist, so let's
>> not accidentally upscale the depth with this configuration
>
> Yes it does, at least on Mac/m68k.
>
> Now the real question is: why doesn't macfb set FB_VISUAL_STATIC_PSEUDOCOLOR if
> there's no macfb_setpalette routine?
It should. The other question is, what to do with static pseudocolor?
Do we always assume console colors? Or do we make drivers fill their own
info->cmap entries and not alter the contents when fb_set_cmap() is called?
Also, I made vesafb's visual static_pseudocolor if the mode is not VGA compatible
and the protected mode interface is absent. Fortunately, the VGA colormap is carried
over to vesafb, so by accident, the console color map coincides with the hardware
CLUT and the logo and console displays correctly.
Tony
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-04-29 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 0:41 [PATCH 10/12] fbdev: Static pseudocolor with depth less than 4 does exist Antonino A. Daplas
2006-04-29 7:38 ` Geert Uytterhoeven
2006-04-29 12:34 ` Antonino A. Daplas [this message]
2006-04-29 18:28 ` Geert Uytterhoeven
2006-04-29 15:50 ` Brad Boyer
2006-04-29 21:42 ` Antonino A. Daplas
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=44535D47.5060000@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mac68k@mac.linux-m68k.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).