From: Hans Verkuil <hverkuil@xs4all.nl>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: yong.zhi@intel.com
Subject: Re: [v4l-utils PATCH 0/2] META_OUTPUT buffer type support for v4l2-compliance
Date: Tue, 11 Dec 2018 09:22:38 +0100 [thread overview]
Message-ID: <f5c40bc3-39fb-dfb4-5ab8-99385a2c96ba@xs4all.nl> (raw)
In-Reply-To: <20181210212036.16643-1-sakari.ailus@linux.intel.com>
On 12/10/18 10:20 PM, Sakari Ailus wrote:
> Hi all,
>
> Here are the patches needed to support the META_OUTPUT queue type for
> v4l2-compliance. The patch that adds the support is preceded by the kernel
> header update --- the headers have been recently updated and there were
> no other changes.
Looks good for v4l2-compliance, but v4l2-ctl should also be updated.
I have alreaedy prepared v4l2-ctl-meta.cpp (should work automatically with
this patch series applied), but there are two other places where you need
to add META_OUTPUT support. Just add a third patch for v4l2-ctl.
Regards,
Hans
>
> Sakari Ailus (1):
> Update uAPI headers from the kernel
>
> Yong Zhi (1):
> v4l2-compliance: Add support for metadata output
>
> include/linux/videodev2.h | 2 ++
> utils/common/v4l-helpers.h | 14 +++++++++++++-
> utils/common/v4l2-info.cpp | 4 ++++
> utils/v4l2-compliance/v4l2-compliance.cpp | 7 ++++---
> utils/v4l2-compliance/v4l2-compliance.h | 2 +-
> utils/v4l2-compliance/v4l2-test-formats.cpp | 7 +++++++
> 6 files changed, 31 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2018-12-11 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 21:20 [v4l-utils PATCH 0/2] META_OUTPUT buffer type support for v4l2-compliance Sakari Ailus
2018-12-10 21:20 ` [v4l-utils PATCH 1/2] Update uAPI headers from the kernel Sakari Ailus
2018-12-10 21:20 ` [v4l-utils PATCH 2/2] v4l2-compliance: Add support for metadata output Sakari Ailus
2018-12-11 8:22 ` Hans Verkuil [this message]
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=f5c40bc3-39fb-dfb4-5ab8-99385a2c96ba@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yong.zhi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).