From: Paulo Marques <pmarques@grupopie.com>
To: Lothar Wassmann <LW@KARO-electronics.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-fbdev-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] pxafb: Add support for other palette formats
Date: Wed, 04 Jul 2007 12:00:48 +0100 [thread overview]
Message-ID: <468B7DE0.9020506@grupopie.com> (raw)
In-Reply-To: <18059.18815.378793.220680@ipc1.karo>
Lothar Wassmann wrote:
> Hi,
Hi,
>> I assume the "red 6@16" is a typo for "red 6@12", since the "3 byte /
>> green 6@6 and blue 6@0" match exactly the 18bpp packed format. Even
>>
> Take a closer look at the actual pixel format of the PXA270.
> The usual graphics packages AFAIK support either packed pixels
> (i.e. 18 bit on screen => 18 bit in memory)
This mode would be quite insane: 16 pixels in 9 words? :P
No, I don't think there are graphics packages out there supporting this
mode.
> or unpacked (i.e. 18/24
> or whatever bits => 32 bit in memory).
> The PXA supports either the unpacked pixel format (which is a waste of
> memory especially on embedded systems)
...but is very good for alignment. Access to any individual pixel is
always aligned on a 4 byte boundary. So, I guess it depends on the
application.
> or a strange format which is
> neither: 18bit on screen in 24bit in memory (IOW 4 pixels in 3
> words in memory).
Take a closer look at my post, specially at the "3 byte" part. The mode
supported by DirectFB is really the packed mode of the PXA270: 18bit on
screen in 24bit in memory.
--
Paulo Marques - www.grupopie.com
"All I ask is a chance to prove that money can't make me happy."
-------------------------------------------------------------------
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 prev parent reply other threads:[~2007-07-04 11:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 14:07 [PATCH] pxafb: Add support for other palette formats Hans-Jürgen Koch
2007-07-03 14:46 ` Paulo Marques
2007-07-03 15:03 ` Hans-Jürgen Koch
2007-07-03 15:24 ` Paulo Marques
2007-07-03 15:50 ` Lothar Wassmann
2007-07-03 15:58 ` Geert Uytterhoeven
2007-07-12 7:56 ` Antonino A. Daplas
2007-07-12 8:01 ` Antonino A. Daplas
2007-07-03 16:03 ` Paulo Marques
2007-07-03 16:45 ` Hans-Jürgen Koch
2007-07-03 17:21 ` Paulo Marques
2007-07-03 17:44 ` Hans-Jürgen Koch
2007-07-03 18:18 ` Paulo Marques
2007-07-04 7:17 ` Lothar Wassmann
2007-07-04 11:00 ` Paulo Marques [this message]
2007-07-04 6:56 ` Lothar Wassmann
2007-07-03 16:39 ` Hans-Jürgen Koch
2007-07-03 17:14 ` Lothar Wassmann
2007-07-03 17:33 ` Hans-Jürgen Koch
2007-07-13 12:20 ` Antonino A. Daplas
2007-07-13 12:39 ` Hans-Jürgen Koch
2007-07-03 19:01 ` Clemens Koller
2007-07-03 19:11 ` Hans-Jürgen Koch
2007-07-03 20:36 ` Hans-Jürgen Koch
2007-07-04 6:38 ` eric miao
2007-07-04 7:51 ` Lothar Wassmann
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=468B7DE0.9020506@grupopie.com \
--to=pmarques@grupopie.com \
--cc=LW@KARO-electronics.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=tglx@linutronix.de \
/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).