Jonathan Corbet wrote: > On Sun, 15 Mar 2009 17:10:01 +0000 > Jonathan Cameron <jic23@xxxxxxxxx> wrote: > >> The primary control on this chip related to shutter rate is actualy >> the frame rate. There are rather complex (and largerly undocumented) >> interactions between this setting and the auto brightness controls >> etc. Anyone have any suggestions on a better way of specifying this? > > Welcome to the world of the ov7670! My conclusion, after working with > this sensor, is that is consists of something like 150 analog tweakers > disguised as digital registers. Everything interacts with everything > else, many of the settings are completely undocumented, and that's not > to mention the weird multiplexor at 0x79. It's hard to make this thing > work if you don't have a blessed set of settings from OmniVision. Hmm... And the grape vine / rumour says that they get most of their 'magic' values from customers who tweak the chips enough to get something working. Thanks for all the good work you put in. Only other useful info was the tinyos driver and that was a port of yours in the first place ;) I'm particularly fond of the apparently obvious registers that won't take a write unless something else is in a particular state. > >> Clearly this driver shares considerable portions of code with >> Jonathan Corbet's driver (in tree). It would be complex to combine >> the two drivers, but perhaps people feel this would be worthwhile? > > I think it's necessary, really. Having two drivers for the same device > seems like a bad idea. As Hans noted, he's already put quite a bit of > work into generalizing the ov7670 driver; I think it would be best to > work with him to get a driver that works for everybody. That sounds like a good plan. Now all we need is some time ;) Jonathan -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
