From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Luotao Fu <l.fu@pengutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andres Salomon <dilinger@debian.org>,
Alessandro Rubini <rubini@unipv.it>,
Krzysztof Helt <krzysztof.h1@wp.pl>,
Kevin Wells <wellsk40@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amba-clcd: add RGB444 support
Date: Mon, 15 Mar 2010 14:13:04 +0000 [thread overview]
Message-ID: <20100315141304.GF700@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100315135945.GA4584@pengutronix.de>
On Mon, Mar 15, 2010 at 02:59:45PM +0100, Luotao Fu wrote:
> Hi Russell,
>
> On Mon, Mar 15, 2010 at 01:38:10PM +0000, Russell King - ARM Linux wrote:
> > On Mon, Mar 15, 2010 at 02:30:09PM +0100, Luotao Fu wrote:
> > > This one adds RGB444 (bpp=12) support to amba clcd drivers. Tested on a lpc3250
> > > based platform.
> >
> > No - this is wrong. You have a 16bpp display. bpp is the number of bits
> > in the framebuffer between two successive pixels. It is not the number of
> > bits used for the pixel information.
> >
>
> > The only case where you have a 12bpp display is if you have two pixels
> > packed into three bytes.
> >
> For 12bpp actually 16bits/pixel is used. I'm aware of that. That's the
> reason why the fb.var.bits_per_pixel is set to 16 in clcdfb_decode if
> it is originally set to 12 from the platform file to make usage of 16bpp
> display. omapfb driver does quite the same.
Then omapfb is also buggy and needs fixing in a similar manner.
The de-facto way of determining the bitfield structure is as I highlighted,
which is used by all the x86 drivers supporting RGB555 and RGB565.
We don't use bits_per_pixel=15 for RGB555, and using bits_per_pixel=12 for
RGB444 is wrong for all the same reasons.
prev parent reply other threads:[~2010-03-15 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 13:30 Luotao Fu
2010-03-15 13:38 ` Russell King - ARM Linux
2010-03-15 13:59 ` Luotao Fu
2010-03-15 14:13 ` Russell King - ARM Linux [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=20100315141304.GF700@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dilinger@debian.org \
--cc=krzysztof.h1@wp.pl \
--cc=l.fu@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@unipv.it \
--cc=wellsk40@gmail.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
all inboxes | Powered by JetHome®