From: pieterg@gmx.com (pieterg)
To: linux-arm-kernel@lists.infradead.org
Subject: pxafb: RGBT555 support
Date: Wed, 4 Nov 2009 10:28:28 +0100 [thread overview]
Message-ID: <200911041028.28859.pieterg@gmx.com> (raw)
In-Reply-To: <200910291235.55826.pieterg@gmx.com>
On Thursday 29 October 2009 12:35:55 pieterg wrote:
> Great to see the 'recent' work on overlay support and color format fixes
> in pxafb.c.
> Looks like I no longer need my local patches.
>
> However, there is one thing that I cannot seem to accomplish just yet.
> We have an LCD which is connected in an RGBT555 configuration.
> That means somehow var->transp.length should be set to 1.
> After that, it looks like pxafb_set_pxifmt should do its job just fine.
>
> Would it make sense to add transparency info to pxafb_mode_info?
> After all it is a hardware property, with our LCD and the way it is
> connected we won't be able to do RGB565, so our var->transp.length should
> be fixed at 1.
> If pxafb_setmode could do that, based on the pxafb_mode_info, that would
> probably solve my problem.
> Maybe something could be done by comparing 'depth' and 'bpp', if one is
> 16 and the other 15, one could make the assumption the remaining bit is
> used for transparency.
>
> Or am I overlooking something here, and is there a better way to force
> pxafb to RGBT555 for my LCD?
Sorry to ask again, but is there an official/preferred way to select RGBT555
mode in pxafb, or should I just continue hacking it in for now?
Rgds, Pieter
next prev parent reply other threads:[~2009-11-04 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 11:35 pxafb: RGBT555 support pieterg
2009-11-04 9:28 ` pieterg [this message]
2009-11-04 9:34 ` Eric Miao
2009-11-04 10:05 ` pieterg
2009-11-04 14:33 ` Eric Miao
2009-11-05 16:27 ` pieterg
2009-11-12 10:49 ` pieterg
2009-11-13 3:48 ` Eric Miao
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=200911041028.28859.pieterg@gmx.com \
--to=pieterg@gmx.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.