linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Zielinski <grim@undead.cc>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: 2.6 fbcon and 15/16 bpp
Date: Tue, 23 Dec 2003 21:54:57 -0500	[thread overview]
Message-ID: <3FE90001.3080207@undead.cc> (raw)
In-Reply-To: <1072230310.739.25.camel@gaston>

Benjamin Herrenschmidt wrote:

>Intersting. The pseudo palette thing might have to be u32 indeed, I have
>to double check. That sounds like a typical misdesign crap vs. endian
>assuming a given value can be accessed via any size is a little endian
>"feature" that doesn't work on BE.
>  
>

Except that this machine is LE.  Perhaps the software blit routine is 
writing the entire 32 bit value to the frambuffer?

>The HW palette stuff for 16 bits is fine afaik (well, i wrote it ;), and it
>works for XFree. What color problems do you have fixed when you comment
>it out ?
>  
>

With the commented code left in or just the OUTREG's commented:

Black        ->   Black
Blue         ->   Cyan
Green        ->   Black
Cyan         ->   Blue
Red          ->   Brown
Magenta      ->   Lt Green
Brown        ->   Brown
Lt Gray      ->   Lt Green
Dk Grey      ->   Dk Purple
Lt Blue      ->   Lt Blue
Lt Green     ->   Dk Purple
Lt Cyan      ->   Lt Blue
Lt Red       ->   Lt Red
Lt Magenta   ->   Lt Magenta
Yellow       ->   Lt Red
White        ->   Lt Magenta


With the OUTREG's left in and the "green =" line commented out:

Black        ->   Black
Blue         ->   Cyan
Green        ->   Black
Cyan         ->   Blue
Red          ->   Brown
Magenta      ->   Lt Green
Brown        ->   Brown
Lt Gray      ->   Lt Green
Dk Gray      ->   Dk Gray
Lt Blue      ->   Lt Blue
Lt Green     ->   Lt Green
Lt Cyan      ->   Lt Cyan
Lt Red       ->   Lt Red
Lt Magenta   ->   Lt Magenta
Yellow       ->   Yellow
White        ->   White


John




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

  reply	other threads:[~2003-12-24  2:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02  7:04 2.6 fbcon and 15/16 bpp Benjamin Herrenschmidt
2003-12-02  7:32 ` John Zielinski
2003-12-02 22:22   ` Benjamin Herrenschmidt
2003-12-02 22:53     ` John Zielinski
2003-12-03  0:19       ` Benjamin Herrenschmidt
2003-12-10  6:43         ` John Zielinski
2003-12-23 23:16         ` John Zielinski
2003-12-24  1:45           ` Benjamin Herrenschmidt
2003-12-24  2:54             ` John Zielinski [this message]
2003-12-24  3:31               ` Benjamin Herrenschmidt
2003-12-24  4:45                 ` John Zielinski
2003-12-24  5:23                   ` Benjamin Herrenschmidt
2003-12-24  6:02                     ` John Zielinski
2003-12-24 12:10                       ` Geert Uytterhoeven
2003-12-24 21:34                         ` John Zielinski
2003-12-24 22:44                           ` Benjamin Herrenschmidt
2003-12-25  0:55                             ` John Zielinski
2003-12-26 11:01                             ` Geert Uytterhoeven
2003-12-24 12:08             ` 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=3FE90001.3080207@undead.cc \
    --to=grim@undead.cc \
    --cc=benh@kernel.crashing.org \
    --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).