[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a42cadc2845c67357d98580e094a8d59c48f7bd8.camel@ndufresne.ca>
Date: Fri, 04 Aug 2023 16:19:18 -0400
From: Nicolas Dufresne <nicolas@...fresne.ca>
To: Tomasz Figa <tfiga@...omium.org>
Cc: Randy Li <ayaka@...lik.info>, linux-media@...r.kernel.org,
randy.li@...aptics.com, Brian.Starkey@....com,
boris.brezillon@...labora.com, frkoenig@...omium.org,
hans.verkuil@...co.com, hiroh@...omium.org, hverkuil@...all.nl,
kernel@...labora.com, laurent.pinchart@...asonboard.com,
linux-kernel@...r.kernel.org, mchehab@...nel.org,
narmstrong@...libre.com, sakari.ailus@....fi,
stanimir.varbanov@...aro.org,
Helen Koike <helen.koike@...labora.com>
Subject: Re: [PATCH v7 2/9] media: vivid: Convert to v4l2_ext_pix_format
Le vendredi 28 juillet 2023 à 16:22 +0900, Tomasz Figa a écrit :
> > For MPLANE, where backward compatibility was built into libv4l2 LD_PRELOAD
> > wrapper,
>
> Could you refresh my memory on what kind of backwards compatibility we
> had in libv4l2? Was that to make it possible to use new MPLANE-only
> drivers with old applications?
https://git.linuxtv.org/v4l-utils.git/tree/lib/libv4l-mplane
It does some "magic" trick due to some of the new fields not guarantied to be
zero, translate the type, the capabilities. Strangely it does not filter the
pixel formats. I suspect it assumes legacy application won't know about the new
one and will just ignore/not use them.
Nicolas
Powered by blists - more mailing lists