From: stefan@datenfreihafen.org
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: [Patch 01/10] pxafb: More LCCR3 depth defines
Date: Mon, 07 Jul 2008 20:40:01 +0200 [thread overview]
Message-ID: <20080707184125.173098306@datenfreihafen.org> (raw)
In-Reply-To: 20080707184000.411913919@datenfreihafen.org
[-- Attachment #1: pxafb-add-18+bpp-lccr3.patch --]
[-- Type: text/plain, Size: 1056 bytes --]
Add missing depth definitions to LCCR3.
Signed-off-by: Daniel Ribeiro <drwyrm@gmail.com>
PATCH FOLLOWS
KernelVersion: 2.6-arm-git pxa branch
Index: linux-2.6-arm/include/asm-arm/arch-pxa/regs-lcd.h
===================================================================
--- linux-2.6-arm.orig/include/asm-arm/arch-pxa/regs-lcd.h
+++ linux-2.6-arm/include/asm-arm/arch-pxa/regs-lcd.h
@@ -24,6 +24,12 @@
#define LCCR3_4BPP (2 << 24)
#define LCCR3_8BPP (3 << 24)
#define LCCR3_16BPP (4 << 24)
+#define LCCR3_18BPP (5 << 24)
+#define LCCR3_18BPP_P (6 << 24)
+#define LCCR3_19BPP (7 << 24)
+#define LCCR3_19BPP_P (1 << 29)
+#define LCCR3_24BPP ((1 << 29) | (1 << 24))
+#define LCCR3_25BPP ((1 << 29) | (2 << 24))
#define LCCR3_PDFOR_0 (0 << 30)
#define LCCR3_PDFOR_1 (1 << 30)
--
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next parent reply other threads:[~2008-07-07 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080707184000.411913919@datenfreihafen.org>
2008-07-07 18:40 ` stefan [this message]
2008-07-08 7:43 ` [Patch 01/10] pxafb: More LCCR3 depth defines Eric Miao
2008-07-07 18:40 ` [Patch 02/10] pxafb: Support for RGB666, RGBT666, RGB888 and RGBT888 stefan
2008-07-08 7:45 ` Eric Miao
2008-07-08 20:13 ` Stefan Schmidt
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=20080707184125.173098306@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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).