<div dir="ltr">Acked-by: Jason Ekstrand <<a href="mailto:jason.ekstrand@collabora.com">jason.ekstrand@collabora.com</a>> </div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 1, 2022 at 4:22 AM Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, 1 Dec 2022 at 11:07, Daniel Vetter <<a href="mailto:daniel@ffwll.ch" target="_blank">daniel@ffwll.ch</a>> wrote: > > On Wed, Nov 23, 2022 at 08:24:37PM +0100, Daniel Vetter wrote: > > It's a bit a FAQ, and we really can't claim to be the authoritative > > source for allocating these numbers used in many standard extensions > > if we tell closed source or vendor stacks in general to go away. > > > > Iirc this was already clarified in some vulkan discussions, but I > > can't find that anywhere anymore. At least not in a public link. > > > > Cc: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@linux.intel.com" target="_blank">maarten.lankhorst@linux.intel.com</a>> > > Cc: Maxime Ripard <<a href="mailto:mripard@kernel.org" target="_blank">mripard@kernel.org</a>> > > Cc: Thomas Zimmermann <<a href="mailto:tzimmermann@suse.de" target="_blank">tzimmermann@suse.de</a>> > > Cc: David Airlie <<a href="mailto:airlied@gmail.com" target="_blank">airlied@gmail.com</a>> > > Cc: Daniel Vetter <<a href="mailto:daniel@ffwll.ch" target="_blank">daniel@ffwll.ch</a>> > > Cc: Alex Deucher <<a href="mailto:alexdeucher@gmail.com" target="_blank">alexdeucher@gmail.com</a>> > > Cc: Daniel Stone <<a href="mailto:daniel@fooishbar.org" target="_blank">daniel@fooishbar.org</a>> > > Cc: Bas Nieuwenhuizen <<a href="mailto:bas@basnieuwenhuizen.nl" target="_blank">bas@basnieuwenhuizen.nl</a>> > > Cc: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net" target="_blank">jason@jlekstrand.net</a>> > > Cc: Neil Trevett <<a href="mailto:ntrevett@nvidia.com" target="_blank">ntrevett@nvidia.com</a>> > > Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@intel.com" target="_blank">daniel.vetter@intel.com</a>> > > From irc: > > <airlied> danvet: ack from me Also from irc: <mareko> danvet: Acked -Daniel > > --- > > include/uapi/drm/drm_fourcc.h | 12 ++++++++++++ > > 1 file changed, 12 insertions(+) > > > > diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h > > index bc056f2d537d..de703c6be969 100644 > > --- a/include/uapi/drm/drm_fourcc.h > > +++ b/include/uapi/drm/drm_fourcc.h > > @@ -88,6 +88,18 @@ extern "C" { > > * > > * The authoritative list of format modifier codes is found in > > * `include/uapi/drm/drm_fourcc.h` > > + * > > + * Open Source User Waiver > > + * ----------------------- > > + * > > + * Because this is the authoritative source for pixel formats and modifiers > > + * referenced by GL, Vulkan extensions and other standards and hence used both > > + * by open source and closed source driver stacks, the usual requirement for an > > + * upstream in-kernel or open source userspace user does not apply. > > + * > > + * To ensure, as much as feasible, compatibility across stacks and avoid > > + * confusion with incompatible enumerations stakeholders for all relevant driver > > + * stacks should approve additions. > > */ > > > > #define fourcc_code(a, b, c, d) ((__u32)(a) | ((__u32)(b) << 8) | \ > > -- > > 2.37.2 > > > > -- > Daniel Vetter > Software Engineer, Intel Corporation > <a href="http://blog.ffwll.ch" rel="noreferrer" target="_blank">http://blog.ffwll.ch</a> -- Daniel Vetter Software Engineer, Intel Corporation <a href="http://blog.ffwll.ch" rel="noreferrer" target="_blank">http://blog.ffwll.ch</a> </blockquote></div>