JoJo jojo schrieb:
Hi VarisHave you followed instructions from here? https://groups.google.com/group/microdia/web/testing-microdia-driver-draft You will need libv4l for the webcam applications to work correctly, post screenshots. whats the command you used on mplayer?, try this one $ LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so mplayer tv:// -tv driver=v4l2:width=640:height=480:fps=25:device=/dev/video0 -vo x11 -JoJo On Thu, Dec 11, 2008 at 3:48 AM, varis <[EMAIL PROTECTED]> wrote:Hi all Trying to load the module I find this trouble in I2C slave. microdia: Microdia USB 2.0 webcam driver loaded microdia: Microdia USB 2.0 Webcam - 0C45:6270 plugged-in. microdia: Detected SN9C20X Bridge microdia: I2C slave 0x5d returned error during write to address 0xff microdia: Detected MT9V111 Sensor microdia: Microdia USB 2.0 Webcam is now controlling video device /dev/ video0 usbcore: registered new interface driver usb_microdia_driver microdia: v2008.11 : Microdia USB 2.0 Webcam Driver And trying to start mplayer inputs: 0 = Webcam;v4l2: ioctl get input failed: Invalid argument I am webmaster of a company which sells a Webcam with this driver in Spain. I have left a link to the group in. http://www.opcion.es/linux.php?info=4--~--~---------~--~----~------------~-------~--~----~ Lets make microdia webcams plug'n play, (currently plug'n pray) To post to this group, send email to [email protected] Visit us online https://groups.google.com/group/microdia -~----------~----~----~----~------~----~------~--~---
The I2C error in dmesg is part of determining which sensor we are facing in a 0c45:6270 or 62b0 device. Therefore it doesn't do any harm but unfortunatly we can't disable it if we don't want to suppress all error output.
The line from mplayer only tells us that mplayer is unhappy with our driver but not what exactly goes wrong. Maybe we should just implement a few more ioctl and see if one of them removes the error.
GWater
signature.asc
Description: OpenPGP digital signature
