From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
"Antonino A. Daplas" <adaplas@gmail.com>
Subject: Re: logos work/apply when?
Date: Fri, 13 Jul 2007 11:06:29 -0700 [thread overview]
Message-ID: <20070713110629.d6eccbd4.rdunlap@xenotime.net> (raw)
In-Reply-To: <1184284251.4566.3.camel@daplas>
On Fri, 13 Jul 2007 07:50:51 +0800 Antonino A. Daplas wrote:
> On Thu, 2007-07-12 at 13:08 -0700, Randy Dunlap wrote:
> > Hi,
> >
> > Is there some kernel config or video config (possibly set at boot time
> > via vga=xyz or video=wxy) where one or more of the logos is not
> > applicable? or the other way: are there certain kernel or video
> > configs where only certain logos are applicable?
> >
> >
> > I've tested vesafb with LOGO_LINUX_VGA16 but I can't see the logo.
> > I do see an empty space for it at the top of the screen area, however.
> > (booting with vga=0x317 in /etc/lilo.conf file)
> >
> > When I use LOGO_LINUX_CLUT224 instead, I do see the logo.
> >
> > or when I use FB_VGA16 instead of vesafb and also use LOGO_LINUX_VGA16,
> > I can see the logo.
> >
> > I'm just trying to understand when/why I should expect (or not expect)
> > to see a logo (if it is enabled).
>
> It's a bug. And I've been wanting to fix that for some time. Logo's with
> depths <= the fb depth should still be shown. The problem is that VGA16
> and monochrome logos do not contain color information, so we have to use
> the console palette (and not create a new one). Try the attached patch.
That works in my testing. Thanks.
So when all 3 of these are enabled:
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
is the one with most depth that is supported by the fb driver used?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-13 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 20:08 logos work/apply when? Randy Dunlap
2007-07-12 23:50 ` Antonino A. Daplas
2007-07-13 18:06 ` Randy Dunlap [this message]
2007-07-13 22:49 ` 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=20070713110629.d6eccbd4.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=adaplas@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).