From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bryan Stillwell <bryan@bokeoa.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: radeonfb and 16bit color problem
Date: Mon, 24 Jun 2002 07:41:46 +0200 [thread overview]
Message-ID: <20020624054147.21846@192.168.4.1> (raw)
In-Reply-To: <20020625104117.A31689@bokeoa.com>
>I thought that piece of code looked weird because it's setting green
>equal to rinfo->palette[regno<<1].green, but doesn't seem to ever use
>green during the rest of the function...
It should about 2 lines below ... at least in my tree.
>BTW, don't you mean 64 palette entries for green (being that it's 6
>bits)?
Yah, sorry, typing too fast ;)
>Anyways, I took some time this weekend to look over the code
>some more, and I really doubt my problems originates in that function.
>As I understand it, the palette (colormap?) will only be used when
>displaying colors in text mode.
Hrm... there HW colormap is used in all modes in recent drivers, thus
you can actually set a gamma table. The driver should set it to a
linear ramp by default though that may be broken.
>My problem seems to affect many more colors (practically all 65536 of
>them), but I've yet to track it down. I put in a request on ATI's
>website to get access to the specs (hoping that'll help me), but I
>haven't heard anything back from them yet.
Ben.
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
prev parent reply other threads:[~2002-06-25 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 3:29 radeonfb and 16bit color problem Bryan Stillwell
2002-06-24 3:24 ` Benjamin Herrenschmidt
2002-06-25 16:41 ` Bryan Stillwell
2002-06-24 5:41 ` Benjamin Herrenschmidt [this message]
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=20020624054147.21846@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=bryan@bokeoa.com \
--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).