This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Wed Mar 20 05:00:12 CET 2019
media-tree git hash:6fe59b7eec391ad2e340f7727781cede099ab4c9
media_build git
Sean Young writes:
> Adam wrote:
>> Rather than document all this, isn't better to clean it up in the
>> source? I can probably come up with a patch for this issue in fairly
>> short order, if that's welcome.
>
> You're right, this is broken. For this to work it would have to get all
> the detail
On Tue, 19 Mar 2019 17:37:59 +
Brian Starkey wrote:
> Hi Boris,
>
> On Tue, Mar 19, 2019 at 03:52:42PM +0100, Boris Brezillon wrote:
> > This is part of the multiplanar and singleplanar unification process.
> > v4l2_ext_pix_format is supposed to work for both cases.
> >
> > We also add the
On Tue, 19 Mar 2019 14:07:32 -0400
Nicolas Dufresne wrote:
> Le mardi 19 mars 2019 à 15:52 +0100, Boris Brezillon a écrit :
> > +/**
> > + * struct v4l2_plane_ext_pix_format - additional, per-plane format
> > definition
> > + * @modifier: modifier applied to the format (used for tiled
Hi Gregor,
Samuel reported in priv that the issues he had with user after free were
solved by the patchsets merged at 1.12 and 1.16 stable branches.
Could you please generate a new staging release for them?
Thanks!
Mauro
Em Sun, 17 Mar 2019 06:52:42 -0300
Mauro Carvalho Chehab escreveu:
> Em
Le mardi 19 mars 2019 à 15:52 +0100, Boris Brezillon a écrit :
> +/**
> + * struct v4l2_plane_ext_pix_format - additional, per-plane format definition
> + * @modifier: modifier applied to the format (used for tiled formats
> + * and other kind of HW-specific formats, li
Hi Boris,
On Tue, Mar 19, 2019 at 03:52:42PM +0100, Boris Brezillon wrote:
> This is part of the multiplanar and singleplanar unification process.
> v4l2_ext_pix_format is supposed to work for both cases.
>
> We also add the concept of modifiers already employed in DRM to expose
> HW-specific for
From: Hans Verkuil
Those extended buffer ops have several purpose:
1/ Fix y2038 issues by converting the timestamp into an u64 counting
the number of ns elapsed since 1970
2/ Unify single/multiplanar handling
3/ Add a new start offset field to each v4l2 plane buffer info struct
to support t
This is part of the multiplanar and singleplanar unification process.
v4l2_ext_pix_format is supposed to work for both cases.
We also add the concept of modifiers already employed in DRM to expose
HW-specific formats (like tiled or compressed formats) and allow
exchanging this information with the
Hello,
This RFC follows the discussion started by Hans [1] a few months back.
It does not try to address all the problem reported in this thread but
instead focuses on the FMT and BUF(S) ioctls.
Note that my primary goal is to unify handling for multiplanar and
singleplanar formats and extend thi
Support for multiplanar and singleplanar formats is mutually exclusive,
at least in practice. In our attempt to unify support for support for
mplane and !mplane in v4l, let's get rid of the
->vidioc_enum_fmt_{vid,out}_cap_mplane() hooks and call
->vidioc_enum_fmt_{vid,out}_cap() instead.
Signed-of
2019年3月19日(火) 18:14 :
>
>
>
> On 13.03.2019 23:05, Sakari Ailus wrote:
>
> > On Tue, Mar 12, 2019 at 06:16:08PM +0100, Lubomir Rintel wrote:
> >> On Tue, 2019-03-12 at 00:36 +0900, Akinobu Mita wrote:
> >>> This patchset fixes the problems introduced by recent change to ov7670.
> >>>
> >>> Akinobu
V4L2 async framework can use both device's fwnode and endpoints's fwnode
for matching the async sub-device with the sub-device. In order to proceed
moving towards endpoint matching assign the endpoint to the async
sub-device.
As most async sub-device drivers (and the related hardware) only support
v4l2_async_notifier_add_fwnode_remote_subdev is a convenience function for
parsing information on V4L2 fwnode subdevs.
Signed-off-by: Sakari Ailus
---
since RFC v1:
- Fix documentation for v4l2_async_notifier_add_fwnode_remote_subdev.
drivers/media/v4l2-core/v4l2-async.c | 23 +
On Mon, Mar 18, 2019 at 08:19:42PM -0400, Adam Di Carlo wrote:
>
> There seems to be known issue with ir-keytable such that while
>
> ./ir-keytable -p rc5
>
> works, this one won't:
>
> ./ir-keytable -d /dev/input/event24 -p rc5
>
> Reading the source, it looks like the internal 'rc_dev' s
Hi Mauro,
Here's a set of sensor and IPU3 driver patches as well as fwnode fixes in
the frameworks as well as in the DaVinci VPE driver. Also put the lens
drivers in Kconfig into their own section (they were in the decoder
section).
Please pull.
The following changes since commit 9e98c678c2d6ae
On 13.03.2019 23:05, Sakari Ailus wrote:
> On Tue, Mar 12, 2019 at 06:16:08PM +0100, Lubomir Rintel wrote:
>> On Tue, 2019-03-12 at 00:36 +0900, Akinobu Mita wrote:
>>> This patchset fixes the problems introduced by recent change to ov7670.
>>>
>>> Akinobu Mita (2):
>>>media: ov7670: restore
This is not how ACPI tables are written. Add a deprecation note and refer
to the proper documentation.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-fwnode.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/v4l2-fwnode.c
b/drivers/me
18 matches
Mail list logo
