On Tue, 15 Mar 2022 09:57:23 +0100
Geert Uytterhoeven wrote:
> Hi Pekka,
>
> On Tue, Mar 15, 2022 at 9:46 AM Pekka Paalanen wrote:
> > On Tue, 15 Mar 2022 08:51:31 +0100
> > Geert Uytterhoeven wrote:
> > > On Tue, Mar 15, 2022 at 8:33 AM Pekka Paalanen
> > > wrote:
> > > > On Tue, 15
Hi Pekka,
On Tue, Mar 15, 2022 at 9:46 AM Pekka Paalanen wrote:
> On Tue, 15 Mar 2022 08:51:31 +0100
> Geert Uytterhoeven wrote:
> > On Tue, Mar 15, 2022 at 8:33 AM Pekka Paalanen wrote:
> > > On Tue, 15 Mar 2022 09:15:08 +1100 (AEDT)
> > > Finn Thain wrote:
> > > > On Mon, 14 Mar 2022, Geert
On Tue, 15 Mar 2022 08:51:31 +0100
Geert Uytterhoeven wrote:
> Hi Pekka,
>
> On Tue, Mar 15, 2022 at 8:33 AM Pekka Paalanen wrote:
> > On Tue, 15 Mar 2022 09:15:08 +1100 (AEDT)
> > Finn Thain wrote:
> > > On Mon, 14 Mar 2022, Geert Uytterhoeven wrote:
> > > > On Mon, Mar 14, 2022 at 4:05
On Tue, Mar 15, 2022 at 8:51 AM Geert Uytterhoeven wrote:
> > Also, when drm_fourcc.h is describing pixel formats, it needs to
> > consider only how a little-endian CPU accesses them. That's how pixel
> > data in memory is described. Display hardware plays no part in that.
> > It is the driver's
Hi Pekka,
On Tue, Mar 15, 2022 at 8:33 AM Pekka Paalanen wrote:
> On Tue, 15 Mar 2022 09:15:08 +1100 (AEDT)
> Finn Thain wrote:
> > On Mon, 14 Mar 2022, Geert Uytterhoeven wrote:
> > > On Mon, Mar 14, 2022 at 4:05 PM Pekka Paalanen
> > > wrote:
> > > > On Mon, 14 Mar 2022 14:30:18 +0100
> > >
Hi Geert,
On Mon, 14 Mar 2022, Geert Uytterhoeven wrote:
> On Mon, Mar 14, 2022 at 4:05 PM Pekka Paalanen wrote:
> > On Mon, 14 Mar 2022 14:30:18 +0100
> > Geert Uytterhoeven wrote:
> > > On Mon, Mar 7, 2022 at 9:53 PM Geert Uytterhoeven
> > > wrote:
> > > > Introduce fourcc codes for
On Tue, 15 Mar 2022 09:15:08 +1100 (AEDT)
Finn Thain wrote:
> Hi Geert,
>
> On Mon, 14 Mar 2022, Geert Uytterhoeven wrote:
>
> > On Mon, Mar 14, 2022 at 4:05 PM Pekka Paalanen wrote:
> >
> > > On Mon, 14 Mar 2022 14:30:18 +0100
> > > Geert Uytterhoeven wrote:
> > > > On Mon, Mar 7, 2022
Hi Pekka,
On Mon, Mar 14, 2022 at 4:05 PM Pekka Paalanen wrote:
> On Mon, 14 Mar 2022 14:30:18 +0100
> Geert Uytterhoeven wrote:
> > On Mon, Mar 7, 2022 at 9:53 PM Geert Uytterhoeven
> > wrote:
> > > Introduce fourcc codes for color-indexed frame buffer formats with two,
> > > four, and
On Mon, 14 Mar 2022 14:30:18 +0100
Geert Uytterhoeven wrote:
> On Mon, Mar 7, 2022 at 9:53 PM Geert Uytterhoeven
> wrote:
> > Introduce fourcc codes for color-indexed frame buffer formats with two,
> > four, and sixteen colors, and provide a mapping from bit per pixel and
> > depth to fourcc
On Mon, Mar 7, 2022 at 9:53 PM Geert Uytterhoeven wrote:
> Introduce fourcc codes for color-indexed frame buffer formats with two,
> four, and sixteen colors, and provide a mapping from bit per pixel and
> depth to fourcc codes.
>
> As the number of bits per pixel is less than eight, these rely
On 3/7/22 21:52, Geert Uytterhoeven wrote:
> Introduce fourcc codes for color-indexed frame buffer formats with two,
> four, and sixteen colors, and provide a mapping from bit per pixel and
> depth to fourcc codes.
>
> As the number of bits per pixel is less than eight, these rely on proper
>
On Mon, 7 Mar 2022 21:52:40 +0100
Geert Uytterhoeven wrote:
> Introduce fourcc codes for color-indexed frame buffer formats with two,
> four, and sixteen colors, and provide a mapping from bit per pixel and
> depth to fourcc codes.
>
> As the number of bits per pixel is less than eight, these
Introduce fourcc codes for color-indexed frame buffer formats with two,
four, and sixteen colors, and provide a mapping from bit per pixel and
depth to fourcc codes.
As the number of bits per pixel is less than eight, these rely on proper
block handling for the calculation of bits per pixel and
13 matches
Mail list logo
