On Tuesday 03 February 2009 14:53:05 Korvin wrote: > On Tuesday 03 February 2009 18:20:15 Vasily Khoruzhick wrote: > > MI1310 == MT9M111 (supported by our driver) > > MI1320 == MT9M112 (AFAIK not supported) > > So.. at least I understand why it initializing successfully. Seems that > these sensors have the same (or at least compatible) I2C interface and > register set. Therefore it does not complain about incorrect writes. > > I think that we need to pass some more init data or something... and then > hopefully, it will be possible to use the device %) > > I try to sniff the USB traffic and report here. > > > Btw, did you try to run mplayer when you forced driver to use > > MT9M112-specific code for your sensor? > > > > Note: you should run mplayer with libv4l in LD_PRELOAD (look at driver's > > README) > > Yes, i tried to run as shown in readme, but it displays a lot of errors > like: ... > Current input: 1 > Current format: unknown (0x30323953) > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > v4l2: ioctl set format failed: Invalid argument > tv.c: norm_from_string(pal): Unknown parameter norm > v4l2: ioctl enum norm failed: Invalid argument > ... > v4l2: Cannot get fps > v4l2: ioctl set mute failed: Invalid argument > v4l2: ioctl query control failed: Invalid argument > v4l2: ioctl query control failed: Invalid argument > ...
These errors indicate that you're using not latest libv4l, please download and install libv4l-0.5.8
signature.asc
Description: This is a digitally signed message part.
