On Mon, 19 Mar 2012 17:27:06 +0100 javier Martin <javier.martin@xxxxxxxxxxxxxxxxx> wrote: > I suspect the problem is related to the fact that this sensor has an > array of 656 x 488 pixels but only 640 x 480 are active. The datasheet > available from Omnivision (Version 1.4, August 21, 2006) is not clear > about how to configure the sensor not to show non active pixels but I > could find the following patch which addresses a similar problem for > QVGA: Interesting...nobody ever sent that patch anywhere where I've seen it. Anyway, the ov7670 datasheet is not clear on much of anything, and the things it *is* clear on are likely to be wrong. The comment in the patch makes it clear how this was worked out, anyway: "empirically determined." Unless you can get through to the one person at OmniVision who knows how this sensor actually works, the best that can be done is to mess with the values for the window. That's often done at both the sensor and the controller level - if you look at the Marvell controller, you'll see window tweaking there too. jon -- 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
