From: John Zielinski <grim@undead.cc>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
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 19:55:12 -0500 [thread overview]
Message-ID: <3FEA3570.6050905@undead.cc> (raw)
In-Reply-To: <1072305863.15477.15.camel@gaston>
Benjamin Herrenschmidt wrote:
>64 but with only green mattering above 32 iirc, look what XFree does.
>
>
Good. I'll make a patch for fbtest then.
>If XFree/fbdev works, then the fbdev is ok :)
>
>
I'll have to look at the XFree code then to see what they're up to.
There's a lot of extra dac updates going on that just get overwritten
again. If you look at my simulation you can see that all the updates
by the second set of OUTREGs gets overwritten by the first set later
on. I even disabled the second set in my kernel for 16 bit modes and
everything still looks the same. That code is probably there for a
reason. I'm just trying to figure out why. :)
>>PARM: 00 R: 00 (Par:00) G: 00 (Par:00) B: 00 (Par:00)
>>OUT1: 00 R: 00 (Pal:00) G: 00 (Par:00) B: 00 (Pal:00)
>>OUT2: 00 R: 00 (Par:00) G: 00 (Pal:00) B: 00 (Par:00)
>>
>>PARM: 01 R: 01 (Par:01) G: 01 (Par:01) B: 01 (Par:01)
>>OUT1: 04 R: 00 (Pal:00) G: 01 (Par:01) B: 00 (Pal:00)
>>*** Palette green 02 read uninitialized data ***
>>OUT2: 08 R: 01 (Par:01) G: !! (Pal:02) B: 01 (Par:01)
>>
>>PARM: 02 R: 02 (Par:02) G: 02 (Par:02) B: 02 (Par:02)
>>OUT1: 08 R: 01 (Pal:01) G: 02 (Par:02) B: 01 (Pal:01)
>>*** Palette green 04 read uninitialized data ***
>>OUT2: 10 R: 02 (Par:02) G: !! (Pal:04) B: 02 (Par:02)
>>
>>
As you can see, the dac register 08 is written on the second call by the
second set of OUTREGs (OUT2:) and then overwritten by the first on the
third call to the function (OUT1). It's also grabbing a value for the
green component from palette array index 2 which hasn't beet updated yet
(that's what the !! means). I'm just curious why it's doing this and
what special case requires it....
John
-------------------------------------------------------
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-25 0:55 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
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 [this message]
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=3FEA3570.6050905@undead.cc \
--to=grim@undead.cc \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.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).