From: Russell King <rmk@arm.linux.org.uk>
To: Denis Oliver Kropp <dok@directfb.org>
Cc: James Simmons <jsimmons@transvirtual.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [2.5.21] CyberPro 32bit support and other fixes
Date: Sat, 15 Jun 2002 13:30:50 +0100 [thread overview]
Message-ID: <20020615133050.A15283@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020613092323.GA2384@skunk.convergence.de> <Pine.LNX.4.44.0206141550000.21575-100000@www.transvirtual.com> <20020615105547.GA22186@skunk.convergence.de>
On Sat, Jun 15, 2002 at 12:55:47PM +0200, Denis Oliver Kropp wrote:
> > > There's no speed benefit and
> > > applications running in true/direct color would look wrong.
> >
> > For userland no but for the kernel we do have a benifiet.
>
> There's no speed benefit if you write "index|index|index" into the
> framebuffer instead of "red|green|blue".
You're actually asking the wrong question. "Why is there such a thing as
directcolor" would be a better question. After all, if there's no "speed
benefit" when why do manufacturers bother implementing it?
Could it be because it allows colours to be dynamically allocated? Given
a "good enough" allocator which looks over your complete colour usage, you
could probably make better use of the available colours than truecolor
allows.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-06-15 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 8:32 [PATCH] [2.5.21] CyberPro 32bit support and other fixes Denis Oliver Kropp
2002-06-13 9:09 ` Russell King
2002-06-13 9:23 ` Denis Oliver Kropp
2002-06-14 22:53 ` James Simmons
2002-06-15 10:55 ` Denis Oliver Kropp
2002-06-15 12:30 ` Russell King [this message]
2002-06-15 14:03 ` Denis Oliver Kropp
2002-06-28 13:03 ` 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=20020615133050.A15283@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dok@directfb.org \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
/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