linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Kern <alex.kern@gmx.de>
To: linux-fbdev-devel@lists.sourceforge.net, adaplas@pol.net
Cc: "Ville Syrjälä" <syrjala@sci.fi>
Subject: Re: Re: [Question] Colour management
Date: Sun, 1 Aug 2004 00:19:41 +0200	[thread overview]
Message-ID: <200408010019.41627.alex.kern@gmx.de> (raw)
In-Reply-To: <200408010519.58517.adaplas@hotpop.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

Am Samstag, 31. Juli 2004 23:19 schrieb Antonino A. Daplas:
> On Saturday 31 July 2004 21:31, Ville Syrjälä wrote:
> > > red_reg[index * 8] = red
> > > green_reg[index * 8] = green
> > > blue_reg[index * 8] = blue
> > >
> > > Some hardware require that all 8 entries needs to be filled up.
> >
> > I noticed you do this in i810fb. What happens if you don't do this?
>
>  
> Wrong colors.
>
> > AFAIK mach64 doesn't need this.
>
> Yes, it's hardware dependent. When I decided to add directcolor support,
> I initially copied the mach64's setcolreg function but I got wrong
> colors at bpp16.  Found out by experimentation that I need to set all
> 256 entries of the CLUT.
>
> Tony
Very scurry, even mach64 give wrong colors for me ;-))

Here are the pics, that demonstrate my errors.

empty-penguin.jpg shows how looks my boot logo at 15 and 16bpp
Sorry for wrong description in previous mail. Text string is not JSimmons but 
simple Simmons.

fbi-shows-wrongcolors.jpg shows fbi gives wrong colors at 16bpp, must be 
yellow, got red.

Regards Alex

P.S. maybe boot logo function is not too good client?

[-- Attachment #2: empty-penguin.jpg --]
[-- Type: image/jpeg, Size: 35642 bytes --]

[-- Attachment #3: fbi-shows-wrongcolors.jpg --]
[-- Type: image/jpeg, Size: 71923 bytes --]

  reply	other threads:[~2004-07-31 22:20 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 [this message]
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
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=200408010019.41627.alex.kern@gmx.de \
    --to=alex.kern@gmx.de \
    --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).