linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Voyager GX color mapping
Date: Tue, 14 Dec 2004 18:14:52 +0100	[thread overview]
Message-ID: <41BF1F8C.6030501@anagramm.de> (raw)
In-Reply-To: <Pine.GSO.4.61.0412141744200.10558@waterleaf.sonytel.be>

Hello, Geert!

>>well, my version of the Silicon Motion SM501 driver works now
>>quite well on the PowerMac (after some data integrity problems
>>with the card having in a dusty PCI slot. :-(( )
>>
>>Only one thing is missing: The color mapping in the
>>32bit mode doesn't fit with X. The fb memory map has a BGRA
>>color mapping but X11 writes it in RGBA.
>>
>>I have tried to change the fb_var_screeninfo.fb_bitfield
> 
> You should indeed make sure the fb_var_screeninfo.fb_bitfield values are
> correct.  BTW, have you tried fbtest to verify the correctness of your driver?
> You can check it out from CVS on SourceForge.

I got fbset already... thanks.

Well, whenever I change the (yet hardcoded) structs in the driver,
fbset -fb /dev/fb2 shows me the correct (changed) values.
But there is no change in X at all if I play around with the values.
Is it possible that X doesn't get my fb_var_screeninfo? Maybe I need
to check xorg.cfg again...
The same things happen in all 32bit (RGBA8888) as well as in
16bit (RGB565) modes (i haven't tried 8bit, as I don't need it).
Is this an PPC-endian related problem?
Is the SM501's BGRA mapping usual?
Hmm...

>>Where do I need to tweak to get it working?
> X should obey the fb_var_screeninfo.fb_bitfield values. If it doesn't, it's a
> bug in X.

Unlikely, I think?

I use a primary "ATI Radeon If" (fb0, fb1) on Depth 16 successfuly.
The SMI501 is the secondary graphics board (fb2) on Depth 16, 24, 32.
Does X listen only to the mapping of the primary card? I guess I will
get offtopic with the X questions.

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-14 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 16:40 Voyager GX color mapping Clemens Koller
2004-12-14 16:46 ` Geert Uytterhoeven
2004-12-14 17:14   ` Clemens Koller [this message]
2004-12-14 17:19     ` Geert Uytterhoeven
2004-12-14 17:40       ` Clemens Koller
2004-12-14 18:55         ` Geert Uytterhoeven
2004-12-14 16:57 ` Paul Mundt
2004-12-14 17:23   ` Clemens Koller

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=41BF1F8C.6030501@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --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).