#3 Windows driver .. observation



Just as an observation. I got the impression that the Windows driver was able to deal with only 2 different 'back-ends' which are the Micron MI2020 and OmniVision OV2640 optical chips, so I wonder where all these different versions of this camera come from. Obviously I only have one version of this driver, and there can be many ways the 8052 controller can be programmed .. odd .. I'll dig a little further into this ..



  • Logged In: YES
    Originator: NO

    Hello Olieboer,

    thank you for your interest in the driver.
    It seems that the cam in the C90s behaves differently than all other we observed until now. In the ubuntuforums discussion:


    we have two C90s owners who say that the driver does not work for them in the current versions.
    How did you find out that information about the optical chips? It would be interesting to dig which chip I have (for me the driver works perfectly in the "ms" version) and then compare.
    Thank you again for looking into this!

  • Logged In: NO

    Hi Jack,

    I'd started working on a driver myself, though through a different principle. I tried to make a driver like what ndiswrapper does for wireless network cards. I already had partly figured out some of the function calls in the Windows driver, except I found out that this driver is rather complicated, consisting of multiple parts in multiple files. This gl860 project however will beat my timeline by far. Anyway, you can find out about the optical chips, just having a look at the files involved in the Windows driver. First, you can look in the GL860.inf file, which holds a lot of information, and you'd probably find something starting with OV or MI and then a 4 digit number. Secondly the backends for these optical chips actually reside in separate files called MI2020S.SET and OV2640S.SET. If your Windows driver comes with different names for these .SET files, then we may have found one reason why all these cameras are different.