[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANq1E4SZPhzYKUi-VRQon90R8wC9wRncN7ah60CqwwAL-x6EHQ@mail.gmail.com>
Date: Fri, 5 Jul 2013 15:09:42 +0200
From: David Herrmann <dh.herrmann@...il.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
David Airlie <airlied@...ux.ie>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Stephen Warren <swarren@...dotorg.org>,
Peter Jones <pjones@...hat.com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
x86@...nel.org, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2 00/14] Platform Framebuffers and SimpleDRM
Hi
On Thu, Jul 4, 2013 at 7:48 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 07/04/2013 05:25 AM, David Herrmann wrote:
>>
>> - What FB formats are common on x86 that we should add to
>> SIMPLEFB_FORMATS?
>> (other than ARGB/XRGB32)
>
>
> The common pixel formats on x86 are:
>
> - Palettized 4-bit planar (bigendian, i.e. MSB to the left)
> - Palettized 8-bit packed (one byte per pixel)
Unlikely to be supported with DRM. But if users want it, we can always
add a shadow-buffer and advertise it as RGB332 or alike. Otherwise,
they have to use fbdev as usual, which sounds reasonable to me.
> - 16-bit RGB555 (16-bit littleendian words with R=14:10, G=9:5, B=4:0)
DRM_FORMAT_XRGB1555
> - 16-bit RGB565 (16-bit littleendian words with R=15:11, G=10:5, B=4:0)
DRM_FORMAT_RGB565
> - 24-bit RGB888 in littleendian order (first byte in memory is B,
> second is G, third is R)
DRM_FORMAT_RGB888
> - 32-bit ARGB8888 (first byte in memory is B, second G, third R, fourth
> unused in the framebuffer proper)
DRM_FORMAT_ARGB8888
> - 32-bit RGB10:10:10 (I *believe* 32-bit littleendian words with
> R=29:20, G=19:10, B=9:0)
DRM_FORMAT_XRGB2101010
Thanks for the hints, I will add these to patch #5.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists