On 2/22/20 5:58 AM, Hans Verkuil wrote: > virtme: ERRORS: Final Summary: 2943, Succeeded: 2925, Failed: 18, Warnings: 0 > sparse: OK > smatch: OK > > Detailed results are available here: > > http://www.xs4all.nl/~hverkuil/logs/Saturday.log > > Detailed regression test results are available here: > > http://www.xs4all.nl/~hverkuil/logs/Saturday-test-media.log Looking at this it turns out that the new tests I added in v4l2-compliance to check for USERPTR overwrites before the start/after the end of the buffer caused failures in vivid and vim2m. There was also a bug in the compliance code that turned one test in a NOP. I've improved the compliance code, and unfortunately I'm now also getting warnings in vimc and vicodec. I'll dig more into this on Monday. It's an interesting test, and if it finds real bugs, then it would be interesting to see if similar tests can be made for the MMAP streaming mode, since ALL drivers support that. Also, this test is only done with the configured format when v4l2-compliance is called. There is a separate test that tries to stream with all available formats, but that is MMAP-only. It would be interesting to support USERPTR there as well. Regards, Hans > http://www.xs4all.nl/~hverkuil/logs/Saturday-test-media-dmesg.log > > Full logs are available here: > > http://www.xs4all.nl/~hverkuil/logs/Saturday.tar.bz2 > > The Media Infrastructure API from this daily build is here: > > http://www.xs4all.nl/~hverkuil/spec/index.html >
