linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Zielinski <grim@undead.cc>
Cc: Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: 2.6 fbcon and 15/16 bpp
Date: Wed, 24 Dec 2003 12:45:11 +1100	[thread overview]
Message-ID: <1072230310.739.25.camel@gaston> (raw)
In-Reply-To: <3FE8CCE3.4010709@undead.cc>


> Here's a patch that fixed things on my machine.  I found it by trial and 
> error since I don't have a hardware reference document and the code is a 
> little confusing to me.  I don't know if this is the root cause or just 
> a fix for the symptoms.  Changing the u16's to u32's fixed the verticle 
> grille appearance and most of the color corruption.  Commenting out that 
> small block of code fixed the rest of the color problems.
> 
> I have a few questions.  Why are we going through the palette instead of 
> just writing the proper directcolor/truecolor bitvalues for that color?  
> Does that have to do with the disabled HW acceleration code?   Or is it 
> because the hw palette color components are 8 bits wide so the displayed 
> colors are more accurate?
> 
> And the code that I commented out, why is it accesing palette array 
> elements that have been set on a previous call or haven't been set yet?  
> Why is it trying to compensate for the wider green field when we're 
> programming 8 bit values to the hw palette?
> 
> My understanding of the low level video hardware control is very limited 
> beyond standard VGA register programming so I'm hoping to learn 
> something with all my questions.  :)
> 

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.

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 ?

Ben.




-------------------------------------------------------
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  1:45 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 [this message]
2003-12-24  2:54             ` John Zielinski
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=1072230310.739.25.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=grim@undead.cc \
    --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).