linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: "Ville Syrjälä" <syrjala@sci.fi>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [Question] Colour management
Date: Sun, 1 Aug 2004 09:03:43 +0800	[thread overview]
Message-ID: <200408010903.43998.adaplas@hotpop.com> (raw)
In-Reply-To: <20040731221014.GA17669@sci.fi>

On Sunday 01 August 2004 06:10, Ville Syrjälä wrote:
> On Fri, Jul 30, 2004 at 08:12:36PM +0200, Alexander Kern wrote:
> > Hallo Tony,
> >
> > can you explain the deep mining of fb_setcolreg. Background, I observe
> > wrong palette using in 15 and 16 bpp modes, but can not understand, what
> > is the right approach. In both cases from penguin logo I can see only
> > contour in honey yellow and blue vertical string jsimmons, pretty scury
> > ;-) The rest is black! The simple text or ncurses applications have
> > always right colours. Additionally and only by 16bpp fbi shows blurry
> > images.
>
> I just had a look at the fbi code and it's wrong. It was initializing the
> clut to 555. The attached patch fixes the problem.

I know that this is just a test patch but instead of hardwiring the parameters 
of linear_palette, why not do:

linear_palette(var.red.length, var.green.length, var.blue.length)

This way you can catch unusual RGB combinations (ie, RGB484, if there is such 
a thing) and still get correct colors.  You can also eliminate the switch() 
statement, and makes it easier to catch fbdev bugs.

>
> I think the boot logo code is broken. No, I haven't actually looked at it
> but everything else works... Or does it work on some other directcolor hw?

Yes, the logo code is broken, not the drawing code itself, but the logo 
choosing code. As I've mentioned in another thread, 16-bit directcolor cannot 
draw 224-color logos.

Tony




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

  reply	other threads:[~2004-08-01  1:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 18:49 [PATCH] atyfb: vblank irq support Ville Syrjälä
2004-07-24 23:12 ` Alexander Kern
2004-07-25  0:03   ` Antonino A. Daplas
2004-07-25 18:36     ` Alexander Kern
2004-07-25 22:47       ` Antonino A. Daplas
2004-07-30 18:12         ` [Question] Colour management Alexander Kern
2004-07-31 10:26           ` Antonino A. Daplas
2004-07-31 13:31             ` Ville Syrjälä
2004-07-31 21:19               ` Antonino A. Daplas
2004-07-31 22:19                 ` Alexander Kern
2004-07-31 23:37                   ` Antonino A. Daplas
2004-07-31 22:18             ` Ville Syrjälä
2004-07-31 23:47               ` Antonino A. Daplas
2004-07-31 22:10           ` Ville Syrjälä
2004-08-01  1:03             ` Antonino A. Daplas [this message]
2004-07-25 10:16   ` [PATCH] atyfb: vblank irq support Ville Syrjälä
2004-07-25 18:29     ` Alexander Kern
2004-07-25 23:36       ` Ville Syrjälä

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=200408010903.43998.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=syrjala@sci.fi \
    /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).