Em 08-10-2010 18:18, Daniel Drake escreveu: > On 8 October 2010 22:13, Jonathan Corbet <[email protected]> wrote: >> A problem like that will be at the controller level, not the sensor >> level. Given that this is an XO-1 report, I'd assume something >> requires tweaking in the cafe_ccic driver. I wasn't aware of this; I >> know it worked once upon a time. > > I reported it 3 months ago > http://dev.laptop.org/ticket/10231 > > Are you interested in working on this? > I'd have no idea where to start.
It maybe at one or at the other. What happens is that, in general, both the controller and the sensor discards the initial/final parts of a line. The visible area of the image is (generally) configurable on both. If the visible area doesn't match, you'll see a vertical or a horizontal line. This is configured by hstart and hstop, in the case of ov sensors. If you wanna try to fix, all you need to do is do move the start/stop window, for example, subtracting 2 on both hstart/hstop. If this doesn't fix, try 3, 4, ... Yet, as Jon mentioned, if this works on XO-1, the better fix would be to adjust the screen visible area at XO-2 visible area setup (sometimes called "crop area" at datasheets). > > I'm not so convinced that it's a controller problem rather than a > sensor one, given that it says the sensor register values were > determined empirically rather than from docs. > > Thanks, > Daniel > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
