From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
linux-fbdev@vger.kernel.org, linux-m68k@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/10] drm: Add support for low-color frame buffer formats
Date: Mon, 11 Jul 2022 11:12:51 +0200 [thread overview]
Message-ID: <Ysvpk4fzef6caO5y@ravnborg.org> (raw)
In-Reply-To: <d6e5204e-5bbb-fe51-fd29-5452198bf368@suse.de>
Hi Thomas,
On Mon, Jul 11, 2022 at 10:50:00AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 09.07.22 um 15:38 schrieb Sam Ravnborg:
> > Hi Geert,
> >
> > On Fri, Jul 08, 2022 at 08:20:45PM +0200, Geert Uytterhoeven wrote:
> > > Hi all,
> > >
> > > A long outstanding issue with the DRM subsystem has been the lack of
> > > support for low-color displays, as used typically on older desktop
> > > systems, and on small embedded displays.
>
> For the patchset
>
> Acked-by: Thomas Zimemrmann <tzimmermann@suse.de>
>
> >
> > IT is super to have this addressed - thanks!
> >
> > >
> > > This patch series adds support for color-indexed frame buffer formats
> > > with 2, 4, and 16 colors. It has been tested on ARAnyM using a
> > > work-in-progress Atari DRM driver supporting 2, 4, 16, 256, and 65536
> > > colors, with text console operation, fbtest, and modetest.
> > >
> > > Overview:
> > > - Patch 1 introduces a helper, to be used by later patches in the
> > > series,
> > > - Patch 2 introduces a flag to indicate color-indexed formats,
> > > - Patches 3 and 4 correct calculations of bits per pixel for sub-byte
> > > pixel formats,
> > > - Patches 5 and 6 introduce the new C[124] formats,
> > > - Patch 7 fixes an untested code path,
> > > - Patch 8 documents the use of "red" for light-on-dark displays,
> > > - Patches 9 and 10 add more fourcc codes for light-on-dark and
> > > dark-on-light frame buffer formats, which may be useful for e.g. the
> > > ssd130x and repaper drivers.
> >
> > Applied all patches to drm-misc (drm-misc-next), including the last two
> > RFC patches as we then have the formats ready when a user pops up.
>
> I know it's v3 already, but give people at least a workday for reviewing
> before merging patches of this size and impact. Friday-evening patches are
> not supposed to be merged on Saturday afternoons.
Sorry for being too enthusiastic on this one.
Will wait a bit more in the future for these kind of patches.
Sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: linux-fbdev@vger.kernel.org, David Airlie <airlied@linux.ie>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 00/10] drm: Add support for low-color frame buffer formats
Date: Mon, 11 Jul 2022 11:12:51 +0200 [thread overview]
Message-ID: <Ysvpk4fzef6caO5y@ravnborg.org> (raw)
In-Reply-To: <d6e5204e-5bbb-fe51-fd29-5452198bf368@suse.de>
Hi Thomas,
On Mon, Jul 11, 2022 at 10:50:00AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 09.07.22 um 15:38 schrieb Sam Ravnborg:
> > Hi Geert,
> >
> > On Fri, Jul 08, 2022 at 08:20:45PM +0200, Geert Uytterhoeven wrote:
> > > Hi all,
> > >
> > > A long outstanding issue with the DRM subsystem has been the lack of
> > > support for low-color displays, as used typically on older desktop
> > > systems, and on small embedded displays.
>
> For the patchset
>
> Acked-by: Thomas Zimemrmann <tzimmermann@suse.de>
>
> >
> > IT is super to have this addressed - thanks!
> >
> > >
> > > This patch series adds support for color-indexed frame buffer formats
> > > with 2, 4, and 16 colors. It has been tested on ARAnyM using a
> > > work-in-progress Atari DRM driver supporting 2, 4, 16, 256, and 65536
> > > colors, with text console operation, fbtest, and modetest.
> > >
> > > Overview:
> > > - Patch 1 introduces a helper, to be used by later patches in the
> > > series,
> > > - Patch 2 introduces a flag to indicate color-indexed formats,
> > > - Patches 3 and 4 correct calculations of bits per pixel for sub-byte
> > > pixel formats,
> > > - Patches 5 and 6 introduce the new C[124] formats,
> > > - Patch 7 fixes an untested code path,
> > > - Patch 8 documents the use of "red" for light-on-dark displays,
> > > - Patches 9 and 10 add more fourcc codes for light-on-dark and
> > > dark-on-light frame buffer formats, which may be useful for e.g. the
> > > ssd130x and repaper drivers.
> >
> > Applied all patches to drm-misc (drm-misc-next), including the last two
> > RFC patches as we then have the formats ready when a user pops up.
>
> I know it's v3 already, but give people at least a workday for reviewing
> before merging patches of this size and impact. Friday-evening patches are
> not supposed to be merged on Saturday afternoons.
Sorry for being too enthusiastic on this one.
Will wait a bit more in the future for these kind of patches.
Sam
next prev parent reply other threads:[~2022-07-11 9:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:20 [PATCH v3 00/10] drm: Add support for low-color frame buffer formats Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH v3 01/10] drm/fourcc: Add drm_format_info_bpp() helper Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-08-10 15:59 ` Daniel Vetter
2022-08-10 15:59 ` Daniel Vetter
2022-08-11 7:59 ` Geert Uytterhoeven
2022-08-11 7:59 ` Geert Uytterhoeven
2022-08-11 16:11 ` Daniel Vetter
2022-08-11 16:11 ` Daniel Vetter
2022-08-11 18:29 ` Sam Ravnborg
2022-08-11 18:49 ` Geert Uytterhoeven
2022-08-11 18:49 ` Geert Uytterhoeven
2022-08-11 19:30 ` Sam Ravnborg
2022-08-11 19:30 ` Sam Ravnborg
2022-07-08 18:20 ` [PATCH v3 02/10] drm/fourcc: Add drm_format_info.is_color_indexed flag Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH v3 03/10] drm/client: Use actual bpp when allocating frame buffers Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH v3 04/10] drm/framebuffer: Use actual bpp for DRM_IOCTL_MODE_GETFB Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH v3 05/10] drm/fourcc: Add DRM_FORMAT_C[124] Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH v3 06/10] drm/fb-helper: Add support for DRM_FORMAT_C[124] Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-11 8:42 ` Thomas Zimmermann
2022-07-11 8:42 ` Thomas Zimmermann
2022-07-08 18:20 ` [PATCH v3 07/10] drm/gem-fb-helper: Use actual bpp for size calculations Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH v3 08/10] drm/fourcc: Clarify the meaning of single-channel "red" Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH/RFC v3 09/10] drm/fourcc: Add DRM_FORMAT_R[124] Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-08 18:20 ` [PATCH/RFC v3 10/10] drm/fourcc: Add DRM_FORMAT_D[1248] Geert Uytterhoeven
2022-07-08 18:20 ` Geert Uytterhoeven
2022-07-09 13:38 ` [PATCH v3 00/10] drm: Add support for low-color frame buffer formats Sam Ravnborg
2022-07-09 13:38 ` Sam Ravnborg
2022-07-11 8:50 ` Thomas Zimmermann
2022-07-11 8:50 ` Thomas Zimmermann
2022-07-11 9:12 ` Sam Ravnborg [this message]
2022-07-11 9:12 ` Sam Ravnborg
2022-08-10 16:02 ` Daniel Vetter
2022-08-10 16:02 ` Daniel Vetter
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=Ysvpk4fzef6caO5y@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.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: link
Be 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.