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 14:31:23 +1100 [thread overview]
Message-ID: <1072236683.739.32.camel@gaston> (raw)
In-Reply-To: <3FE90001.3080207@undead.cc>
On Wed, 2003-12-24 at 13:54, John Zielinski wrote:
> 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?
Possible.
> >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:
Well, the interesting thing is does X using "fbdev" has proper colors
(or X using "ati" driver with UseFBDev option). If yes, then that code
is right. It's the console/blit code that is wrong.
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
next prev parent reply other threads:[~2003-12-24 3:31 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
2003-12-24 3:31 ` Benjamin Herrenschmidt [this message]
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=1072236683.739.32.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