From: Pekka Paalanen <ppaalanen@gmail.com> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>, Finn Thain <fthain@linux-m68k.org>, David Airlie <airlied@linux.ie>, Helge Deller <deller@gmx.de>, Javier Martinez Canillas <javierm@redhat.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux/m68k <linux-m68k@vger.kernel.org>, DRI Development <dri-devel@lists.freedesktop.org>, Thomas Zimmermann <tzimmermann@suse.de>, Sam Ravnborg <sam@ravnborg.org> Subject: Re: [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124] Date: Tue, 15 Mar 2022 12:48:23 +0200 [thread overview] Message-ID: <20220315124823.2500efe2@eldfell> (raw) In-Reply-To: <CAMuHMdUK2T4HzN6+ShVgbBUjh6S6oTFD_G79k-QMUwo32COJjQ@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 10709 bytes --] On Tue, 15 Mar 2022 09:57:23 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote: > Hi Pekka, > > On Tue, Mar 15, 2022 at 9:46 AM Pekka Paalanen <ppaalanen@gmail.com> wrote: > > On Tue, 15 Mar 2022 08:51:31 +0100 > > Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > > On Tue, Mar 15, 2022 at 8:33 AM Pekka Paalanen <ppaalanen@gmail.com> wrote: > > > > On Tue, 15 Mar 2022 09:15:08 +1100 (AEDT) > > > > Finn Thain <fthain@linux-m68k.org> wrote: > > > > > On Mon, 14 Mar 2022, Geert Uytterhoeven wrote: > > > > > > On Mon, Mar 14, 2022 at 4:05 PM Pekka Paalanen <ppaalanen@gmail.com> wrote: > > > > > > > On Mon, 14 Mar 2022 14:30:18 +0100 > > > > > > > Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > > > > > > > On Mon, Mar 7, 2022 at 9:53 PM Geert Uytterhoeven <geert@linux-m68k.org> 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 block handling for the calculation of bits per pixel and > > > > > > > > > pitch. > > > > > > > > > > > > > > > > > > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> > > > > > > > > > > > > > > > > > --- a/include/uapi/drm/drm_fourcc.h > > > > > > > > > +++ b/include/uapi/drm/drm_fourcc.h > > > > > > > > > @@ -99,7 +99,10 @@ extern "C" { > > > > > > > > > #define DRM_FORMAT_INVALID 0 > > > > > > > > > > > > > > > > > > /* color index */ > > > > > > > > > -#define DRM_FORMAT_C8 fourcc_code('C', '8', ' ', ' ') /* [7:0] C */ > > > > > > > > > +#define DRM_FORMAT_C1 fourcc_code('C', '1', ' ', ' ') /* [7:0] C0:C1:C2:C3:C4:C5:C6:C7 1:1:1:1:1:1:1:1 eight pixels/byte */ > > > > > > > > > +#define DRM_FORMAT_C2 fourcc_code('C', '2', ' ', ' ') /* [7:0] C0:C1:C2:C3 2:2:2:2 four pixels/byte */ > > > > > > > > > +#define DRM_FORMAT_C4 fourcc_code('C', '4', ' ', ' ') /* [7:0] C0:C1 4:4 two pixels/byte */ > > > > > > > > > +#define DRM_FORMAT_C8 fourcc_code('C', '8', ' ', ' ') /* [7:0] C 8 one pixel/byte */ > > > > > > > > > > > > > > > > > > /* 8 bpp Red */ > > > > > > > > > #define DRM_FORMAT_R8 fourcc_code('R', '8', ' ', ' ') /* [7:0] R */ > > > > > > > > > > > > > > > > After replying to Ilia's comment[1], I realized the CFB drawing > > > > > > > > operations use native byte and bit ordering, unless > > > > > > > > FBINFO_FOREIGN_ENDIAN is set. > > > > > > > > While Amiga, Atari, and Sun-3 use big-endian bit ordering, > > > > > > > > e.g. Acorn VIDC[2] uses little endian, and SH7760[3] is configurable > > > > > > > > (sh7760fb configures ordering to match host order). > > > > > > > > BTW, ssd130{7fb,x}_update_rect() both assume little-endian, so I > > > > > > > > guess they are broken on big-endian. > > > > > > > > Fbtest uses big-endian bit ordering, so < 8 bpp is probably broken > > > > > > > > on little-endian. > > > > > > > > > > > > > > > > Hence the above should become: > > > > > > > > > > > > > > > > #define DRM_FORMAT_C1 fourcc_code('C', '1', ' ', ' ') /* > > > > > > > > [7:0] C7:C6:C5:C4:C3:C2:C1:C0 1:1:1:1:1:1:1:1 eight pixels/byte */ > > > > > > > > #define DRM_FORMAT_C2 fourcc_code('C', '2', ' ', ' ') /* > > > > > > > > [7:0] C3:C2:C1:C0 2:2:2:2 four pixels/byte */ > > > > > > > > #define DRM_FORMAT_C4 fourcc_code('C', '4', ' ', ' ') /* > > > > > > > > [7:0] C1:C0 4:4 two pixels/byte */ > > > > > > > > > > > > > > > > The same changes should be made for DRM_FORMAT_[RD][124]. > > > > > > > > > > > > > > > > The fbdev emulation code should gain support for these with and without > > > > > > > > DRM_FORMAT_BIG_ENDIAN, the latter perhaps only on big-endian platforms? > > > > > > > > > > > > > > > > [1] https://lore.kernel.org/r/CAKb7UvgEdm9U=+RyRwL0TGRfA_Qc7NbhCWoZOft2DKdXggtKYw@mail.gmail.com/ > > > > > > > > [2] See p.30 of the VIDC datasheet > > > > > > > > http://chrisacorns.computinghistory.org.uk/docs/Acorn/Misc/Acorn_VIDC_Datasheet.pdf > > > > > > > > [3] See p.1178 of the SH7660 datasheet > > > > > > > > https://datasheet.octopart.com/HD6417760BL200AV-Renesas-datasheet-14105759.pdf > > > > > > > > > > > > > > why would CPU endianess affect the order of bits in a byte? > > > > > > > > > > > > It doesn't, but see below. > > > > > > > > > > > > > Do you mean that bit 0 one machine is (1 << 0), and on another machine > > > > > > > bit 0 is (1 << 7)? > > > > > > > > > > > > No, I mean that in case of multiple pixels per byte, the display > > > > > > hardware pumps out pixels to the CRTC starting from either the MSB > > > > > > or the LSB of the first display byte. Which order depends on the > > > > > > display hardware, not on the CPU. > > > > > > > > > > > > > In C, we have only one way to address bits of a byte and that is with > > > > > > > arithmetic. You cannot take the address of a bit any other way, can you? > > > > > > > > > > > > > > Can we standardise on "bit n of a byte is addressed as (1 << n)"? > > > > > > > > > > > > BIT(n) in Linux works the same for little- and big-endian CPUs. > > > > > > But display hardware may use a different bit order. > > > > > > > > > > Perhaps some of this confusion could be avoided if you describe the > > > > > problem in terms of the sequence of scan-out of pixels, rather than in > > > > > terms of the serialization of bits. The significance of bits within each > > > > > pixel and the ordering of pixels within each memory word are independent, > > > > > right? > > > > > > > > Yes, that might help. > > > > > > Display: > > > > > > P0 P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15 > > > > > > P15 P14 P13 P12 P11 P10 P9 P8 P7 P6 P5 P4 P3 P2 P1 P0 > > > > Hi Geert, > > > > does this mean the display hardware emits even rows from left to right > > and odd rows from right to left? > > No, it means I should have my morning coffee first, and remove all > temporary cruft before pressing send :-( > > The above paragraph should have read: > > Display (16 pixels): > > P0 P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15 > > > I'm guessing P stands for "pixel". > > Exactly. > > > > Memory: > > > > > > 1 bpp (MSB first): > > > > > > bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 > > > ---- ---- ---- ---- ---- ---- ---- ---- > > > byte 0: P0 P1 P2 P3 P4 P5 P6 P7 > > > byte 1: P8 P9 P10 P11 P12 P13 P14 P15 > > > > > > 1 bpp (LSB first): > > > > > > bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 > > > ---- ---- ---- ---- ---- ---- ---- ---- > > > byte 0: P7 P6 P5 P4 P3 P2 P1 P0 > > > byte 1: P15 P14 P13 P12 P11 P10 P9 P8 > > > > > > 2 bpp (MSB first): > > > > > > bits7-6 bits5-4 bits3-2 bits1-0 > > > ------- ------- ------- ------- > > > byte 0: P0 P1 P2 P3 > > > byte 1: P4 P5 P6 P7 > > > byte 2: P8 P9 P10 P11 > > > byte 3: P12 P13 P14 P15 > > > > > > 2 bpp (LSB first): > > > > > > bits7-6 bits5-4 bits3-2 bits1-0 > > > ------- ------- ------- ------- > > > byte 0: P3 P2 P1 P0 > > > byte 1: P7 P6 P5 P4 > > > byte 2: P11 P10 P9 P8 > > > byte 3: P15 P14 P13 P12 > > > > > > 4 bpp (MSB first): > > > > > > bits7-4 bits3-0 > > > ------- ------- > > > byte 0: P0 P1 > > > byte 1: P2 P3 > > > byte 2: P4 P5 > > > byte 3: P6 P7 > > > byte 4: P8 P9 > > > byte 5: P10 P11 > > > byte 6: P12 P13 > > > byte 7: P14 P15 > > > > > > 4 bpp (LSB first): > > > > > > bits7-4 bits3-0 > > > ------- ------- > > > byte 0: P1 P0 > > > byte 1: P3 P2 > > > byte 2: P5 P4 > > > byte 3: P7 P6 > > > byte 4: P9 P8 > > > byte 5: P11 P10 > > > byte 6: P13 P12 > > > byte 7: P15 P14 > > > > I think I can guess what you meant there, and it looks understandable > > to me. These tables are actually very clear, and leave only one thing > > undefined: when multiple bits form a pixel, in which order do the bits > > form the value. I recall you said fbdev allows for both orderings but > > only one order is ever used if I understood right. > > Indeed. The third ordering is the ordering of the bits in a pixel. > As fb_bitfield.msb_right is always false, no hardware ever supported by > fbdev used the other ordering, so we only have to care about: > > 1 bpp: P = [ bitN ] > 2 bpp: P = [ bitN bitN-1 ] > 4 bpp: P = [ bitN bitN-1 bitN-2 bitN-3 ] Excellent! > > > > 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 job to expose the pixel formats that match display > > > > hardware behaviour. > > > > > > But if the "CPU format" does not match the "display support", > > > all pixel data must be converted? > > > > Of course. If the driver author does not want to convert pixel data in > > flight, then the author should not let the driver expose a format that > > needs conversion. > > ... in which case we need a DRM fourcc code for the format? Yes. You can define any new formats you need as long as the format definition does not depend on (is not affected/modified by) CPU endianess or any other CPU or display hardware property. I believe this is the convention used with drm_fourcc. If the format wanted by display hardware depends on something, then you need all relevant pixel formats defined and choose at build or driver initialisation time which ones to expose. > BTW, Atari and Amiga use bitplanes for bpp <= 8, so they need > conversion anyway. Right, that's probably the most reasonable approach. If you really wanted to expose bitplanes, I could imagine that some new format modifiers could achieve that. Thanks, pq [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pekka Paalanen <ppaalanen@gmail.com> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Finn Thain <fthain@linux-m68k.org>, Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Javier Martinez Canillas <javierm@redhat.com>, Sam Ravnborg <sam@ravnborg.org>, Helge Deller <deller@gmx.de>, Linux Fbdev development list <linux-fbdev@vger.kernel.org>, "Linux/m68k" <linux-m68k@vger.kernel.org>, DRI Development <dri-devel@lists.freedesktop.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124] Date: Tue, 15 Mar 2022 12:48:23 +0200 [thread overview] Message-ID: <20220315124823.2500efe2@eldfell> (raw) In-Reply-To: <CAMuHMdUK2T4HzN6+ShVgbBUjh6S6oTFD_G79k-QMUwo32COJjQ@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 10709 bytes --] On Tue, 15 Mar 2022 09:57:23 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote: > Hi Pekka, > > On Tue, Mar 15, 2022 at 9:46 AM Pekka Paalanen <ppaalanen@gmail.com> wrote: > > On Tue, 15 Mar 2022 08:51:31 +0100 > > Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > > On Tue, Mar 15, 2022 at 8:33 AM Pekka Paalanen <ppaalanen@gmail.com> wrote: > > > > On Tue, 15 Mar 2022 09:15:08 +1100 (AEDT) > > > > Finn Thain <fthain@linux-m68k.org> wrote: > > > > > On Mon, 14 Mar 2022, Geert Uytterhoeven wrote: > > > > > > On Mon, Mar 14, 2022 at 4:05 PM Pekka Paalanen <ppaalanen@gmail.com> wrote: > > > > > > > On Mon, 14 Mar 2022 14:30:18 +0100 > > > > > > > Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > > > > > > > On Mon, Mar 7, 2022 at 9:53 PM Geert Uytterhoeven <geert@linux-m68k.org> 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 block handling for the calculation of bits per pixel and > > > > > > > > > pitch. > > > > > > > > > > > > > > > > > > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> > > > > > > > > > > > > > > > > > --- a/include/uapi/drm/drm_fourcc.h > > > > > > > > > +++ b/include/uapi/drm/drm_fourcc.h > > > > > > > > > @@ -99,7 +99,10 @@ extern "C" { > > > > > > > > > #define DRM_FORMAT_INVALID 0 > > > > > > > > > > > > > > > > > > /* color index */ > > > > > > > > > -#define DRM_FORMAT_C8 fourcc_code('C', '8', ' ', ' ') /* [7:0] C */ > > > > > > > > > +#define DRM_FORMAT_C1 fourcc_code('C', '1', ' ', ' ') /* [7:0] C0:C1:C2:C3:C4:C5:C6:C7 1:1:1:1:1:1:1:1 eight pixels/byte */ > > > > > > > > > +#define DRM_FORMAT_C2 fourcc_code('C', '2', ' ', ' ') /* [7:0] C0:C1:C2:C3 2:2:2:2 four pixels/byte */ > > > > > > > > > +#define DRM_FORMAT_C4 fourcc_code('C', '4', ' ', ' ') /* [7:0] C0:C1 4:4 two pixels/byte */ > > > > > > > > > +#define DRM_FORMAT_C8 fourcc_code('C', '8', ' ', ' ') /* [7:0] C 8 one pixel/byte */ > > > > > > > > > > > > > > > > > > /* 8 bpp Red */ > > > > > > > > > #define DRM_FORMAT_R8 fourcc_code('R', '8', ' ', ' ') /* [7:0] R */ > > > > > > > > > > > > > > > > After replying to Ilia's comment[1], I realized the CFB drawing > > > > > > > > operations use native byte and bit ordering, unless > > > > > > > > FBINFO_FOREIGN_ENDIAN is set. > > > > > > > > While Amiga, Atari, and Sun-3 use big-endian bit ordering, > > > > > > > > e.g. Acorn VIDC[2] uses little endian, and SH7760[3] is configurable > > > > > > > > (sh7760fb configures ordering to match host order). > > > > > > > > BTW, ssd130{7fb,x}_update_rect() both assume little-endian, so I > > > > > > > > guess they are broken on big-endian. > > > > > > > > Fbtest uses big-endian bit ordering, so < 8 bpp is probably broken > > > > > > > > on little-endian. > > > > > > > > > > > > > > > > Hence the above should become: > > > > > > > > > > > > > > > > #define DRM_FORMAT_C1 fourcc_code('C', '1', ' ', ' ') /* > > > > > > > > [7:0] C7:C6:C5:C4:C3:C2:C1:C0 1:1:1:1:1:1:1:1 eight pixels/byte */ > > > > > > > > #define DRM_FORMAT_C2 fourcc_code('C', '2', ' ', ' ') /* > > > > > > > > [7:0] C3:C2:C1:C0 2:2:2:2 four pixels/byte */ > > > > > > > > #define DRM_FORMAT_C4 fourcc_code('C', '4', ' ', ' ') /* > > > > > > > > [7:0] C1:C0 4:4 two pixels/byte */ > > > > > > > > > > > > > > > > The same changes should be made for DRM_FORMAT_[RD][124]. > > > > > > > > > > > > > > > > The fbdev emulation code should gain support for these with and without > > > > > > > > DRM_FORMAT_BIG_ENDIAN, the latter perhaps only on big-endian platforms? > > > > > > > > > > > > > > > > [1] https://lore.kernel.org/r/CAKb7UvgEdm9U=+RyRwL0TGRfA_Qc7NbhCWoZOft2DKdXggtKYw@mail.gmail.com/ > > > > > > > > [2] See p.30 of the VIDC datasheet > > > > > > > > http://chrisacorns.computinghistory.org.uk/docs/Acorn/Misc/Acorn_VIDC_Datasheet.pdf > > > > > > > > [3] See p.1178 of the SH7660 datasheet > > > > > > > > https://datasheet.octopart.com/HD6417760BL200AV-Renesas-datasheet-14105759.pdf > > > > > > > > > > > > > > why would CPU endianess affect the order of bits in a byte? > > > > > > > > > > > > It doesn't, but see below. > > > > > > > > > > > > > Do you mean that bit 0 one machine is (1 << 0), and on another machine > > > > > > > bit 0 is (1 << 7)? > > > > > > > > > > > > No, I mean that in case of multiple pixels per byte, the display > > > > > > hardware pumps out pixels to the CRTC starting from either the MSB > > > > > > or the LSB of the first display byte. Which order depends on the > > > > > > display hardware, not on the CPU. > > > > > > > > > > > > > In C, we have only one way to address bits of a byte and that is with > > > > > > > arithmetic. You cannot take the address of a bit any other way, can you? > > > > > > > > > > > > > > Can we standardise on "bit n of a byte is addressed as (1 << n)"? > > > > > > > > > > > > BIT(n) in Linux works the same for little- and big-endian CPUs. > > > > > > But display hardware may use a different bit order. > > > > > > > > > > Perhaps some of this confusion could be avoided if you describe the > > > > > problem in terms of the sequence of scan-out of pixels, rather than in > > > > > terms of the serialization of bits. The significance of bits within each > > > > > pixel and the ordering of pixels within each memory word are independent, > > > > > right? > > > > > > > > Yes, that might help. > > > > > > Display: > > > > > > P0 P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15 > > > > > > P15 P14 P13 P12 P11 P10 P9 P8 P7 P6 P5 P4 P3 P2 P1 P0 > > > > Hi Geert, > > > > does this mean the display hardware emits even rows from left to right > > and odd rows from right to left? > > No, it means I should have my morning coffee first, and remove all > temporary cruft before pressing send :-( > > The above paragraph should have read: > > Display (16 pixels): > > P0 P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15 > > > I'm guessing P stands for "pixel". > > Exactly. > > > > Memory: > > > > > > 1 bpp (MSB first): > > > > > > bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 > > > ---- ---- ---- ---- ---- ---- ---- ---- > > > byte 0: P0 P1 P2 P3 P4 P5 P6 P7 > > > byte 1: P8 P9 P10 P11 P12 P13 P14 P15 > > > > > > 1 bpp (LSB first): > > > > > > bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 > > > ---- ---- ---- ---- ---- ---- ---- ---- > > > byte 0: P7 P6 P5 P4 P3 P2 P1 P0 > > > byte 1: P15 P14 P13 P12 P11 P10 P9 P8 > > > > > > 2 bpp (MSB first): > > > > > > bits7-6 bits5-4 bits3-2 bits1-0 > > > ------- ------- ------- ------- > > > byte 0: P0 P1 P2 P3 > > > byte 1: P4 P5 P6 P7 > > > byte 2: P8 P9 P10 P11 > > > byte 3: P12 P13 P14 P15 > > > > > > 2 bpp (LSB first): > > > > > > bits7-6 bits5-4 bits3-2 bits1-0 > > > ------- ------- ------- ------- > > > byte 0: P3 P2 P1 P0 > > > byte 1: P7 P6 P5 P4 > > > byte 2: P11 P10 P9 P8 > > > byte 3: P15 P14 P13 P12 > > > > > > 4 bpp (MSB first): > > > > > > bits7-4 bits3-0 > > > ------- ------- > > > byte 0: P0 P1 > > > byte 1: P2 P3 > > > byte 2: P4 P5 > > > byte 3: P6 P7 > > > byte 4: P8 P9 > > > byte 5: P10 P11 > > > byte 6: P12 P13 > > > byte 7: P14 P15 > > > > > > 4 bpp (LSB first): > > > > > > bits7-4 bits3-0 > > > ------- ------- > > > byte 0: P1 P0 > > > byte 1: P3 P2 > > > byte 2: P5 P4 > > > byte 3: P7 P6 > > > byte 4: P9 P8 > > > byte 5: P11 P10 > > > byte 6: P13 P12 > > > byte 7: P15 P14 > > > > I think I can guess what you meant there, and it looks understandable > > to me. These tables are actually very clear, and leave only one thing > > undefined: when multiple bits form a pixel, in which order do the bits > > form the value. I recall you said fbdev allows for both orderings but > > only one order is ever used if I understood right. > > Indeed. The third ordering is the ordering of the bits in a pixel. > As fb_bitfield.msb_right is always false, no hardware ever supported by > fbdev used the other ordering, so we only have to care about: > > 1 bpp: P = [ bitN ] > 2 bpp: P = [ bitN bitN-1 ] > 4 bpp: P = [ bitN bitN-1 bitN-2 bitN-3 ] Excellent! > > > > 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 job to expose the pixel formats that match display > > > > hardware behaviour. > > > > > > But if the "CPU format" does not match the "display support", > > > all pixel data must be converted? > > > > Of course. If the driver author does not want to convert pixel data in > > flight, then the author should not let the driver expose a format that > > needs conversion. > > ... in which case we need a DRM fourcc code for the format? Yes. You can define any new formats you need as long as the format definition does not depend on (is not affected/modified by) CPU endianess or any other CPU or display hardware property. I believe this is the convention used with drm_fourcc. If the format wanted by display hardware depends on something, then you need all relevant pixel formats defined and choose at build or driver initialisation time which ones to expose. > BTW, Atari and Amiga use bitplanes for bpp <= 8, so they need > conversion anyway. Right, that's probably the most reasonable approach. If you really wanted to expose bitplanes, I could imagine that some new format modifiers could achieve that. Thanks, pq [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-15 10:48 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-07 20:52 [PATCH v2 00/10] drm: Add support for low-color frame buffer formats Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-07 20:52 ` [PATCH v2 01/10] drm/fourcc: Add drm_format_info_bpp() helper Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:46 ` Javier Martinez Canillas 2022-03-09 12:46 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 02/10] drm/fourcc: Add drm_format_info.is_color_indexed flag Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:50 ` Javier Martinez Canillas 2022-03-09 12:50 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 03/10] drm/client: Use actual bpp when allocating frame buffers Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:51 ` Javier Martinez Canillas 2022-03-09 12:51 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 04/10] drm/framebuffer: Use actual bpp for DRM_IOCTL_MODE_GETFB Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:53 ` Javier Martinez Canillas 2022-03-09 12:53 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-08 9:04 ` Pekka Paalanen 2022-03-08 9:04 ` Pekka Paalanen 2022-03-09 12:57 ` Javier Martinez Canillas 2022-03-09 12:57 ` Javier Martinez Canillas 2022-03-14 13:30 ` Geert Uytterhoeven 2022-03-14 13:30 ` Geert Uytterhoeven 2022-03-14 15:05 ` Pekka Paalanen 2022-03-14 15:05 ` Pekka Paalanen 2022-03-14 19:01 ` Geert Uytterhoeven 2022-03-14 19:01 ` Geert Uytterhoeven 2022-03-14 22:15 ` Finn Thain 2022-03-14 22:15 ` Finn Thain 2022-03-15 7:32 ` Pekka Paalanen 2022-03-15 7:32 ` Pekka Paalanen 2022-03-15 7:51 ` Geert Uytterhoeven 2022-03-15 7:51 ` Geert Uytterhoeven 2022-03-15 7:52 ` Geert Uytterhoeven 2022-03-15 7:52 ` Geert Uytterhoeven 2022-03-15 8:45 ` Pekka Paalanen 2022-03-15 8:45 ` Pekka Paalanen 2022-03-15 8:57 ` Geert Uytterhoeven 2022-03-15 8:57 ` Geert Uytterhoeven 2022-03-15 10:48 ` Pekka Paalanen [this message] 2022-03-15 10:48 ` Pekka Paalanen 2022-03-07 20:52 ` [PATCH v2 06/10] drm/fb-helper: Add support for DRM_FORMAT_C[124] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:10 ` Javier Martinez Canillas 2022-03-09 13:10 ` Javier Martinez Canillas 2022-03-09 13:14 ` Geert Uytterhoeven 2022-03-09 13:14 ` Geert Uytterhoeven 2022-03-07 20:52 ` [PATCH v2 RFC 07/10] drm/gem-fb-helper: Use actual bpp for size calculations Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:16 ` Javier Martinez Canillas 2022-03-09 13:16 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 RFC 08/10] drm/fourcc: Document that single-channel "red" can be any color Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-08 9:06 ` Pekka Paalanen 2022-03-08 9:06 ` Pekka Paalanen 2022-03-09 13:33 ` Javier Martinez Canillas 2022-03-09 13:33 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 RFC 09/10] drm/fourcc: Add DRM_FORMAT_R[124] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:39 ` Javier Martinez Canillas 2022-03-09 13:39 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 RFC 10/10] drm/fourcc: Add DRM_FORMAT_D[1248] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:41 ` Javier Martinez Canillas 2022-03-09 13:41 ` Javier Martinez Canillas
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=20220315124823.2500efe2@eldfell \ --to=ppaalanen@gmail.com \ --cc=airlied@linux.ie \ --cc=deller@gmx.de \ --cc=dri-devel@lists.freedesktop.org \ --cc=fthain@linux-m68k.org \ --cc=geert@linux-m68k.org \ --cc=javierm@redhat.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-m68k@vger.kernel.org \ --cc=sam@ravnborg.org \ --cc=tzimmermann@suse.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: linkBe 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.