From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Naresh Kamboju <naresh.kamboju@linaro.org>, linux-media@vger.kernel.org
Cc: open list <linux-kernel@vger.kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
paul.kocialkowski@bootlin.com, ezequiel@collabora.com,
treding@nvidia.com, niklas.soderlund+renesas@ragnatech.se,
sakari.ailus@linux.intel.com,
Hans Verkuil <hans.verkuil@cisco.com>,
mchehab@kernel.org, lkft-triage@lists.linaro.org
Subject: Re: Format ioctls (Input 1) test Cropping failed: 4.19, 4.14, 4.9 and 4.4
Date: Mon, 13 May 2019 15:56:34 +0200 [thread overview]
Message-ID: <cc4b91e4-13f8-c489-e2ce-445770ddf876@xs4all.nl> (raw)
In-Reply-To: <CA+G9fYv+M_8p99c6i=akmuhHSCW6MdF-29CPKrwDsd2EW_LsbQ@mail.gmail.com>
On 5/13/19 3:36 PM, Naresh Kamboju wrote:
> Format ioctls (Input 1) test Cropping failed on all devices running
> 4.19, 4.14, 4.9 and 4.4 kernel branches.
>
> Format ioctls (Input 1):
>
> ...
> test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported)
> fail: ../../../v4l-utils-1.16.0/utils/v4l2-compliance/v4l2-test-formats.cpp(1425):
> doioctl(node, VIDIOC_CROPCAP, &cap)
> fail: ../../../v4l-utils-1.16.0/utils/v4l2-compliance/v4l2-test-formats.cpp(1447):
> testLegacyCrop(node)
> test Cropping: FAIL
There is no easy patch you can backport to fix this and I wouldn't bother with this.
>
> Test passes on mainline, -next and 5.0
> Test failed on 4.19, 4.14, 4.9 and 4.4 for all devices
>
> steps to reproduce:
>
> # boot 4.19/4.14/4.9 kernel on x86_64 / Juno / hikey / device
> # install v4l-utils package
> # modprobe vivid.ko no_error_inj=1
> # v4l2-compliance -v -d /dev/video0
>
> Test results comparison on all branches,
> https://qa-reports.linaro.org/_/comparetest/?project=22&project=6&project=58&project=135&project=40&project=23&project=159&suite=v4l2-compliance&test=Cropping
>
> Test output log,
> https://lkft.validation.linaro.org/scheduler/job/708755#L2236
>
> Best regards
> Naresh Kamboju
>
Be aware that v4l2-compliance is meant to be compiled directly from the
v4l-utils master repo, and run against the latest media-tree master
repository. It's not meant to be backwards compatible with older kernels.
If you want to do regression testing with v4l2-compliance against older
kernels, then it would actually be better to pick a v4l2-compliance version
from around the time that kernel version was first released.
Regards,
Hans
prev parent reply other threads:[~2019-05-13 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 13:36 Naresh Kamboju
2019-05-13 13:56 ` 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=cc4b91e4-13f8-c489-e2ce-445770ddf876@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mchehab@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=paul.kocialkowski@bootlin.com \
--cc=sakari.ailus@linux.intel.com \
--cc=samitolvanen@google.com \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®