From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Jon Smirl <jonsmirl@gmail.com>
Subject: Re: mono, gray and index configs
Date: Fri, 12 Aug 2005 18:28:52 +0800 [thread overview]
Message-ID: <42FC79E4.2010209@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0508120923170.18366@numbat.sonytel.be>
Geert Uytterhoeven wrote:
> On Fri, 12 Aug 2005, Antonino A. Daplas wrote:
>> Geert Uytterhoeven wrote:
>>> On Thu, 11 Aug 2005, Antonino Daplas wrote:
>>>> (Depending on how correct I am with the interpretation, there might be
>>>> some bugs in fbdev on how it determines the color depth. No one is
>>>> complaining yet though, so greater than 1-bit monochrome is probably
>>>> rare if not nonexistent.)
>>> There definitely are bugs w.r.t. this, especially in the 2.4 logo code ;-)
>>>
>> Yes, I would agree. Do you know of any outstanding bugs on color handling
>> in 2.6 code, especially for hardware with bitdepths < 8? I would like to
>> fix them.
>
> Unfortunately not. Due to personel reasons, I temporarily don't have much
> time left to do real coding.
>
> You can always try vgafb's 16 color mode and check for yourself.
That's okay. I'm actually emulating these low bit depths using pseudocolor whenever
I look for bugs for depths < 4 (ie monochrome text attributes). I haven't found
any yet except for the greater than 1-bit monochrome color handling which I've
already fixed in my tree.
Tony
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-12 10:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 3:21 mono, gray and index configs Jon Smirl
2005-08-11 5:36 ` Antonino A. Daplas
2005-08-11 8:22 ` Geert Uytterhoeven
2005-08-11 11:08 ` Antonino Daplas
2005-08-11 11:49 ` Geert Uytterhoeven
2005-08-11 17:34 ` Antonino A. Daplas
2005-08-11 19:14 ` Jon Smirl
2005-08-20 1:13 ` Jon Smirl
2005-08-20 2:56 ` Antonino A. Daplas
2005-08-20 3:09 ` Jon Smirl
2005-08-22 10:17 ` Geert Uytterhoeven
2005-08-22 13:30 ` Richard Smith
2005-08-22 14:06 ` Geert Uytterhoeven
2005-08-22 14:36 ` Richard Smith
2005-08-22 15:47 ` Antonino A. Daplas
2005-08-22 17:19 ` Geert Uytterhoeven
2005-08-22 19:00 ` Richard Smith
2005-08-22 19:44 ` Richard Smith
2005-08-22 15:57 ` Jon Smirl
2005-08-12 7:24 ` Geert Uytterhoeven
2005-08-12 10:28 ` Antonino A. Daplas [this message]
2005-08-11 8:20 ` Geert Uytterhoeven
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=42FC79E4.2010209@gmail.com \
--to=adaplas@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jonsmirl@gmail.com \
--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 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.