On Tuesday 03 February 2009 17:48:30 Vasily Khoruzhick wrote: > It will be nice if you have datasheet for your sensor. Unfortunatly, MI1320 is a mysterious device :D I searched the whole web for datasheet, but found nothing. Only some strings like "SN9C102x + MI1320" saying that some devices have such config.
Will try to ask guys from GPSCA team about datasheet, because it seemed that 102x bridge supports MI somehow. > If not, you should capture usb traffic that windows driver produce (I think this article: > http://groups.google.com/group/microdia/web/usb-sniffing-on-windows should > help you) Ok, I'll try this. Also, default setting from the cfg file may be valuable (i found them in windows driver's cfg) P.S. There is another funny thing: When I played with existing microdia drivers I tried to bring device up using different configurations of sensor & I2C address. Of course it wasn't working and complaining about I2C errors while trying to write at particular addresses (dmesg showed that). But one config was started without any I2C errors at all. Like all init completed successfully. That was the following string: > {SN9C20X_USB_DEVICE(0x0458, 0x704c, MT9M111_SENSOR, 0x5d)}, I found for MT9M111 sensor's datasheet on the net and realized that actual specs are very close to the OEM specification of my webcam. Maybe we're dealing with clones of one arch under two different names? Or with some minor differences which disallow the driver to startup and work correctly. Of course, most likely it's just a bit of luck... and envolved addresses are writeable/readable on both of the chips -- BR, Dmitry Kashitcyn aka Korvin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
