From: Ezequiel Garcia <ezequiel@collabora.com>
To: Milosz Wasilewski <milosz.wasilewski@linaro.org>, kernelci@groups.io
Cc: Gustavo Padovan <gustavo.padovan@collabora.com>,
Chase Qi <chase.qi@linaro.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>,
Mark Brown <broonie@kernel.org>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
Ana Guerrero Lopez <ana.guerrero@collabora.co.uk>
Subject: Re: [kernelci] media subsystem test pilot
Date: Wed, 12 Sep 2018 12:55:04 -0300 [thread overview]
Message-ID: <08bfc4b338de935228efd1fec342caef57d45f3f.camel@collabora.com> (raw)
In-Reply-To: <CAJrz+7KR0x51xK=4bHH2i_OzGgrK6BdyiJE5vhs0gOdNx1YcAw@mail.gmail.com>
On Wed, 2018-09-12 at 09:51 +0100, Milosz Wasilewski wrote:
> On 12 September 2018 at 09:13, Guillaume Tucker
> <guillaume.tucker@gmail.com> wrote:
> >
> > * add config fragment (similar to the kselftest one) with virtual
> > video drivers enabled to test v4l2 framework on QEMU and get
> > reference test results
>
> Last week I asked Chase (CCed) to try to create a 'test definition'
> for v4l for LAVA. I can see the v4l template in the repo now [1] but
> it looks like bound to LAVA environment. Do you possibly have some
> different implementation that allows for local execution?
>
>
(+Nicolas)
v4l2-compliance is a decent test for simple capture devices
(simple means, those that function thru the V4L API).
However, I am not so sure it's the right tool for codecs,
which go thru the stateful or stateless codec API.
Nicolas and I have been talking about using gstreamer for that,
via gst-validate, which allows very interesting tests.
Regards,
Ezequiel
next prev parent reply other threads:[~2018-09-12 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 8:13 media subsystem test pilot Guillaume Tucker
2018-09-12 8:51 ` [kernelci] " Milosz Wasilewski
2018-09-12 15:55 ` Ezequiel Garcia [this message]
2018-09-12 10:34 ` Mark Brown
2018-09-12 20:15 ` Kevin Hilman
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=08bfc4b338de935228efd1fec342caef57d45f3f.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=ana.guerrero@collabora.co.uk \
--cc=broonie@kernel.org \
--cc=chase.qi@linaro.org \
--cc=guillaume.tucker@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci@groups.io \
--cc=milosz.wasilewski@linaro.org \
--cc=nicolas.dufresne@collabora.co.uk \
/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