From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Antonino Daplas <adaplas@pol.net>
Cc: Sven Luther <luther@dpt-info.u-strasbg.fr>,
James Simmons <jsimmons@infradead.org>,
Petr Vandrovec <vandrove@vc.cvut.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Re: FBdev updates.
Date: Thu, 6 Mar 2003 09:25:21 +0100 [thread overview]
Message-ID: <20030306082521.GA1851@iliana> (raw)
In-Reply-To: <1046937890.1208.29.camel@localhost.localdomain>
On Thu, Mar 06, 2003 at 04:05:32PM +0800, Antonino Daplas wrote:
> On Thu, 2003-03-06 at 15:35, Sven Luther wrote:
> > >
> > > > And one (or two...) generic questions: why is not pseudo_palette
> > > > u32* pseudo_palette, or even directly u32 pseudo_palette[17] ?
> > >
> > > pseudo_palette was originally designed to be a pointer to some kind of
> > > data for color register programming. For example many PPC graphics cards
> > > have a color register region. Now you could have that point to
> >
> > Does this correspond to the LUT i have in my boards ?
> >
> > BTW, what is the point in having a pseudo_palette if you can store
> > the colors in the onchip LUT table.
> >
>
> The hardware clut typically stores each color channel separately. In
> software terms, this is akin to struct fb_cmap. The pseudo_palette, on
> the other hand, is a pixel LUT, the contents of which can be directly
> written to the framebuffer without it ever knowing the format at all, ie
> it does not matter if it's RGB or YUV. This makes the upper layer
> independent of the low-lever driver (at least in terms of colorspace
> formats).
Ok, thanks, ...
Friendly,
Sven Luther
next prev parent reply other threads:[~2003-03-06 8:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 1:09 FBdev updates James Simmons
2003-02-20 1:17 ` Jeff Garzik
2003-02-20 1:22 ` James Simmons
2003-02-20 15:02 ` Dave Jones
2003-02-20 15:07 ` James Simmons
2003-02-20 18:29 ` Petr Vandrovec
2003-02-20 19:03 ` Jurriaan
2003-02-20 19:58 ` James Simmons
2003-02-20 22:00 ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-21 9:09 ` Geert Uytterhoeven
2003-02-21 10:46 ` Antonino Daplas
2003-02-21 11:02 ` Geert Uytterhoeven
2003-02-21 1:45 ` David S. Miller
2003-02-21 9:04 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-02-21 0:24 ` Antonino Daplas
2003-03-03 20:35 ` Petr Vandrovec
2003-03-03 21:25 ` Geert Uytterhoeven
2003-03-03 21:32 ` Antonino Daplas
2003-03-05 20:23 ` James Simmons
2003-03-06 1:18 ` Antonino Daplas
2003-03-04 21:29 ` Jurriaan
2003-03-04 21:46 ` Petr Vandrovec
2003-03-09 21:29 ` Petr Vandrovec
2003-03-09 22:27 ` Antonino Daplas
2003-03-09 22:54 ` Petr Vandrovec
2003-03-09 23:44 ` Antonino Daplas
2003-03-11 15:31 ` James Simmons
2003-03-05 20:22 ` James Simmons
2003-03-06 7:35 ` Sven Luther
2003-03-06 8:05 ` Antonino Daplas
2003-03-06 8:25 ` Sven Luther [this message]
2003-03-28 14:19 ` 2.5.66 fbdev performance (was Re: Re: FBdev updates) Petr Vandrovec
2003-03-28 18:50 ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-20 15:10 ` FBdev updates Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 20:31 [Linux-fbdev-devel] " Petr Vandrovec
2003-03-04 21:53 Petr Vandrovec
2002-06-05 16:50 fbdev updates Russell King
2002-06-05 17:21 ` [Linux-fbdev-devel] " James Simmons
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=20030306082521.GA1851@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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).