On Fri, 2011-01-21 at 23:37 +0100, Hans Verkuil wrote: > Hi all, > > As you may have seen I have been adding a lot of tests to the v4l2-compliance > utility in v4l-utils lately. It is now getting to the state that is becomes > quite useful even though there is no full coverage yet. > > Currently the following ioctls are being tested: Hans, This is a great thing to have. Thanks! > Also tested is whether you can open device nodes multiple times. > > These tests are pretty exhaustive and more strict than the spec itself. OK, so multiple open is not strictly required by the spec, IIRC. If you check the ivtv /dev/radio node, it does not allow multiple open, IIRC, so it should not get OK for that test. I also think during the subdev conversion, some of the less popular ivtv cards with GPIO controlled radio audio may have been broken (and still not fixed yet :( ), but working for the PVR-150, PVR-500, etc.. The DEBUG ioctl()s can be compiled out too. So for someone making decisions based on the output of this tool: 1. if something comes back as "Not supported", that still means the driver is API specification compliant, right? 2. could it be the case that this compliance tool will be sensitive to the driver/hardware combination and not the driver alone? Regards, Andy -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
