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 23:45:21 -0500	[thread overview]
Message-ID: <3FE919E1.7050609@undead.cc> (raw)
In-Reply-To: <1072236683.739.32.camel@gaston>

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

Benjamin Herrenschmidt wrote:

>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.
>  
>
Confirmed using fbtest.  With that section commented out fbtest's colors 
are messed up.

Hmmm....  Just found something.  Here's an updated patch.  Notice the 6 
changing to a 5 in the 16 bit case.  This makes the console and fbtest 
look right.... except for the penguins.  Their colors are messed up 
depending on the test order.

John


[-- Attachment #2: patch.16bppfix --]
[-- Type: text/plain, Size: 765 bytes --]

diff -urNX dontdiff linux.old/drivers/video/aty/radeon_base.c linux/drivers/video/aty/radeon_base.c
--- linux.old/drivers/video/aty/radeon_base.c	2003-12-21 17:54:33.000000000 -0500
+++ linux/drivers/video/aty/radeon_base.c	2003-12-23 23:23:03.000000000 -0500
@@ -1197,12 +1197,12 @@
  	if (regno < 16) {
         	switch (rinfo->depth) {
 		case 15:
-			((u16 *) (info->pseudo_palette))[regno] =
+			((u32 *) (info->pseudo_palette))[regno] =
 			    (regno << 10) | (regno << 5) | regno;
 			break;
 		case 16:
-			((u16 *) (info->pseudo_palette))[regno] =
-			    (regno << 11) | (regno << 6) | regno;
+			((u32 *) (info->pseudo_palette))[regno] =
+			    (regno << 11) | (regno << 5) | regno;
 			break;
 		case 24:
 			((u32 *) (info->pseudo_palette))[regno] =

  reply	other threads:[~2003-12-24  4: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
2003-12-24  2:54             ` John Zielinski
2003-12-24  3:31               ` Benjamin Herrenschmidt
2003-12-24  4:45                 ` John Zielinski [this message]
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=3FE919E1.7050609@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).