Hi Sonny,
> that it reports itself as LML33 [0] as it does in
> /proc/video/dev/video0. I believe that it is an issue with the dmsdk.
Getting "LML33\0x5b0\0x5d via v4l [0]" is unusual but not necessarily
wrong. Ascii for "\0x5b0\0x5d" would be "[0]" as you mentioned was
reported by /proc/video/dev/video0. As you can see, the v4l dmmodule
gets that string from:
ioctl(vfd, VIDIOCGCAP, &vcap)
sprintf(device.name, "%s via v4l", vcap.name);
so if vcap.name contains that string, the fix would need to be in
the v4l driver as opposed to the v4l dmmodule.
> that particular device, it fails. I believe it fails because of the
Could you ellaborate on what you mean when you say it fails? Do you
mean that your call to dmuFindDeviceByName failed when you asked
for the device name as "LML33 [0] via v4l"?
We'd be happy to accept a patch if the bug lies in the dmmodule.
Regards,
jaya
>
> First I want to tell the developers what an amazing job they have done.
> Second, I had a question. I installed the dmsdk and I am using the v4l
> drivers for an lml33 (www.linuxmedialabs.com). For normal v4l devices
> it works well. With the dmsdk, it does report itself with dmquery, but
> as "LML33\0x5b0\0x5d via v4l [0]". Unfortunately when I try to query
> that particular device, it fails. I believe it fails because of the
> "\0x5b0\0x5d" in the name. I went through the driver and can only find
> that it reports itself as LML33 [0] as it does in
> /proc/video/dev/video0. I believe that it is an issue with the dmsdk.
> If someone could point me in the right direction to fixing this, I would
> be very grateful. In addition, maybe it would be possible to give
> devices numbers. I know that realserver does this. I appreciate any
> help that anyone can give. I do want to note that I can query the other
> devices on the list without a problem.
>
> Thanks
> Sonny
>
|