From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>
Cc: "ismail dönmez" <ismail.donmez@gmail.com>
Subject: Re: Fw: Re: 2.6.8.1-mm2
Date: Fri, 20 Aug 2004 17:11:06 +0800 [thread overview]
Message-ID: <200408201711.07677.adaplas@hotpop.com> (raw)
In-Reply-To: <20040820012902.55fb2aa6.akpm@osdl.org>
On Friday 20 August 2004 16:29, Andrew Morton wrote:
> Begin forwarded message:
>
> Date: Fri, 20 Aug 2004 11:21:27 +0300
> From: ismail dönmez <ismail.donmez@gmail.com>
> To: Andrew Morton <akpm@osdl.org>
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: 2.6.8.1-mm2
>
> On Thu, 19 Aug 2004 01:42:04 -0700, Andrew Morton <akpm@osdl.org> wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8.1/2.6
> >.8.1-mm2/
>
> Minor issue but still no penguin logo on framebuffer. Config attached in
> case.
The latest fbdev changes in the mm tree differentiates between bpp and color depth.
The vesafb driver at 8 bpp has a color depth of 6 only (try fbset -i) allowing only for
64 colors. So fbdev assumes that vesafb at this depth cannot draw a 224-color
logo.
Try using the 16-color logo instead. The correct fix is for vesafb to correctly determine
the true capability of the hardware instead of arbitrarily setting the color depth at 6.
Tony
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-20 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 8:29 Fw: Re: 2.6.8.1-mm2 Andrew Morton
2004-08-20 9:11 ` Antonino A. Daplas [this message]
2004-08-20 9:16 ` Geert Uytterhoeven
2004-08-20 11:03 ` ismail dönmez
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=200408201711.07677.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=ismail.donmez@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 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).