From: Clemens Koller <clemens.koller@anagramm.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
surendra.yadav@softdel.com
Subject: Re: [F]Framebuffer driver using SM501 hardware.
Date: Wed, 17 Aug 2005 16:31:53 +0200 [thread overview]
Message-ID: <43034A59.6000008@anagramm.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508171439060.6073@numbat.sonytel.be>
Hi Geert, Andrey and friends...
I am working on ppc, MPC8540, SM501 on PCI,
drivers=voyagerfb-0.2.tar.gz from last post.
on linux-2.6
Geert wrote:
> Sorry, I cannot follow.
>
> 1. If it's a palette issue, your setcolreg() routine doesn't fill in correctly
> the pseudo palette,
> 2. If it's a RGB565 vs. BGR565 issue, you don't fill in correctly the offsets
> in the color bitfields in fb_var_screeninfo,
> 3. If it's an endian issue, it's RRRRRGGGGGGBBBBB vs.GGBBBBBRRRRGGGG, right?
> And then there's no much we can do...
It looks for me like 3. = bytes are flipped = an endian issue:
In 32 (RGBAlpha) mode (the one we want to use) the colors appear
wrong. I get my /dev/fb0 appear as
BB GG RR aa BB GG RR aa BB GG RR aa ...
In the great SM501 Databook Version 1.02, Page 2-39, it says:
Configuration 2, Endian Control at MMIO_base+0x00005c:
write 0x00000000 for little endian or
write 0xffffffff for big endian
into this register before touching any other register of the sm501.
I've tried that, but it didn't change anything on my system. :-(
(Well, we can flip the DAC outputs in our hw design ;-)
Best greets,
Clemens
_______________________________
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
------------------------------------------------
details:
$ cp red /dev/fb0
gives me a some red color...
$ bvi red
00000000 00 00 FF 00 00 00 FF 00 00 00 FF 00 00 00 FF 00 ................
00000010 00 00 FF 00 00 00 FF 00 00 00 FF 00 00 00 FF 00 ................
00000020 00 00 FF 00 00 00 FF 00 00 00 FF 00 00 00 FF 00 ................
...
$ cp green /dev/fb0
gives me a some green color...
00 FF 00 00 00 FF 00 00 00 FF 00 00 00 FF 00 00
...
$ cp blue /dev/fb0
well... blue
FF 00 00 00 FF 00 00 00 FF 00 00 00 FF 00 00 00
next prev parent reply other threads:[~2005-08-17 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 13:34 Framebuffer driver using SM501 hardware Surendra Yadav
2005-08-16 16:38 ` Dan Malek
2005-08-16 18:23 ` Clemens Koller
2005-08-16 19:48 ` Wolfgang Denk
2005-08-17 10:11 ` [F]Framebuffer " Andrey Volkov
2005-08-17 11:04 ` Clemens Koller
2005-08-17 11:50 ` Matej Kupljen
2005-08-17 12:37 ` Andrey Volkov
2005-08-17 11:18 ` Geert Uytterhoeven
2005-08-17 12:15 ` Andrey Volkov
2005-08-17 12:42 ` Geert Uytterhoeven
2005-08-17 14:23 ` Andrey Volkov
2005-08-17 14:31 ` Clemens Koller [this message]
2005-08-17 14:52 ` Andrey Volkov
2005-08-16 19:42 ` Framebuffer " Wolfgang Denk
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=43034A59.6000008@anagramm.de \
--to=clemens.koller@anagramm.de \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=surendra.yadav@softdel.com \
/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).