On Fri July 20 2012 11:25:05 javier Martin wrote: > On 19 July 2012 14:14, Hans Verkuil <hverkuil@xxxxxxxxx> wrote: > > Hi Javier, > > > > Can you run v4l2-compliance? I have updated it today so that it is able to > > handle m2m devices. > > > > It will find at least one problem since you didn't set bus_info in querycap :-) > > That's true but in the specification says that "If no such information > is available the field may simply count the devices controlled by the > driver, or contain the empty string (bus_info[0] = 0)" [1]. > What should I put in there anyway? My device is memory mapped through > the AHB bus. Should I just write "ahb"? v4l2-compliance is often more strict than the spec, and this is one such case. It should be possible to use bus_info as a unique identifier of the device, and an empty string doesn't do that. In platform drivers like this you can just fill in the same value as was placed in the card field. I've put this on the list of API items to discuss during the upcoming V4L2 workshop. Regards, Hans > > [1] http://v4l2spec.bytesex.org/spec/r13105.htm > > > You will also see that it complains about VIDIOC_G_PARM. That's fixed by applying > > this patch: > > > > http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg49271.html > > > > That patch is part of a patch series that fixes mem2mem_testdev so that > > v4l2-compliance runs without errors. > > -- 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
