Difference between revisions of "V4L Test Suite"
|Line 28:||Line 28:|
Revision as of 21:39, 5 March 2008
Code to test other code.
If you need a test, look here.
If you create a new test, add it here.
If you know of a test that is not listed, please add it.
VIVI - Virtual Video Driver
A real v4l2 device driver with no physical hardware. This means anyone can use it. If your application has problems with a specific device driver, try using vivi instead. If you still have a problem, it is much more likely to be a problem with the application than with the driver. Knowing where to look is a big help in fixing problems.
However, vivi is not
- perfect. Not surprising given it doesn't get the amount of real world use that real drivers do.
- feature complete. It does not implement every interface of the v4l2 spec (yet.)
But it is something anyone can run, so it makes reproducing some problems possible that would otherwise be impossible without the specific hardware.
Simple programs that test various functionality of a driver.
There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause false problems when someone else uses them in a different environment. For instance, a test should not be run unless the driver advertises suppport for it. This means all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. (note I said 'should' - This does not mean you shouldn't post your test code it it does not comply - something is better than nothing.)
the utilities in the test/ directory of the zvbi tarball, available on zvbi's project page;