* Format ioctls (Input 1) test Cropping failed: 4.19, 4.14, 4.9 and 4.4
@ 2019-05-13 13:36 Naresh Kamboju
2019-05-13 13:56 ` Hans Verkuil
0 siblings, 1 reply; 2+ messages in thread
From: Naresh Kamboju @ 2019-05-13 13:36 UTC (permalink / raw)
To: linux-media
Cc: open list, Sami Tolvanen, paul.kocialkowski, ezequiel, treding,
niklas.soderlund+renesas, sakari.ailus, Hans Verkuil, mchehab,
lkft-triage, Hans Verkuil
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
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Format ioctls (Input 1) test Cropping failed: 4.19, 4.14, 4.9 and 4.4
2019-05-13 13:36 Format ioctls (Input 1) test Cropping failed: 4.19, 4.14, 4.9 and 4.4 Naresh Kamboju
@ 2019-05-13 13:56 ` Hans Verkuil
0 siblings, 0 replies; 2+ messages in thread
From: Hans Verkuil @ 2019-05-13 13:56 UTC (permalink / raw)
To: Naresh Kamboju, linux-media
Cc: open list, Sami Tolvanen, paul.kocialkowski, ezequiel, treding,
niklas.soderlund+renesas, sakari.ailus, Hans Verkuil, mchehab,
lkft-triage
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-13 13:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-13 13:36 Format ioctls (Input 1) test Cropping failed: 4.19, 4.14, 4.9 and 4.4 Naresh Kamboju
2019-05-13 13:56 ` Hans Verkuil
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).