On Friday 22 July 2011 23:31:46 Devin Heitmueller wrote: > On Fri, Jul 22, 2011 at 5:22 PM, Ondrej Zary <linux@xxxxxxxxxxxxxxxxxxxx> wrote: > > Seems that this bug is widespread - the same problem appears also in guvcview > > and adobe flash. I think that the driver is broken too - it should return > > corrected resolution in TRY_FMT. > > Well, if the driver does not return the resolution it is actually > capturing in, then that indeed is a driver bug. That's a different > issue though than what your patch proposed. > > You should make the TRY_FMT call specifying an invalid resolution and > see if it returns the real resolution the device will capture at. If > it doesn't, then fix *that* bug. It does not, there's no code that would do that. I actually fixed that only to find out that the scaling is unusable at least with the MicroCam because of black horizontal lines that appear in the image (amount of the lines depend on the scaling factor). So I just disabled the scaling completely for MicroCam. I also don't know if the multiple-of-64 width limit is valid for all usbvision devices - that's why I haven't posted patch to fix this. > The application needs to know the capturing resolution, so it's > possible that it does properly handle the driver passing back the real > resolution and the driver is at fault, in which case no change is > needed to the app at all. > > Devin > -- Ondrej Zary -- 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
