[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221128082849.jixumay2q5r3f23r@houat>
Date: Mon, 28 Nov 2022 09:28:49 +0100
From: Maxime Ripard <maxime@...no.tech>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>, Helge Deller <deller@....de>,
Michael Schmitz <schmitzmic@...il.com>,
dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
linux-m68k@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH/RFC 3/3] drm: atari: Add a DRM driver for Atari graphics
hardware
Hi,
On Fri, Nov 25, 2022 at 09:31:10PM +0100, Geert Uytterhoeven wrote:
> +// FIXME create dynamically from atari_drm_modes[]?
Not necessarily, but they should have proper descriptors at the very least.
> +static const struct drm_named_mode atari_drm_named_modes[] =
> +{
> + { .name = "st-low" },
> + { .name = "st-mid" },
> + { .name = "st-high" },
> + { .name = "tt-low" },
> + { .name = "tt-mid" },
> + { .name = "tt-high" },
> + { .name = "vga" },
> + { .name = "vga70" },
> + { .name = "qvga" },
> + { .name = "hvga" },
> + { .name = "falh" },
> + { /* sentinel */ }
> +};
I'm really not convinced about per-driver named modes. This will only
lead to each driver having its own set of undocumented and obscure mode
names that will just make everything work.
And some of them in that list are completely generic: VGA, QVGA, HVGA at
least should definitely be part of the generic named modes.
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists