Hi Shuah, > TRY_FMT and S_FMT both don't handle invalid pixelformats. Looks like > there is reason behind this based on the comments: > > /* format->fmt.pix.width only support 720 and height 480 */ > if (width != 720) > width = 720; > if (height != 480) > height = 480; This actually isn't a bug, and in fact I believe the v4l2-compliance tool prints out a URL to a thread you should read. It has to do with the HVR-950q hardware delivering UYVY video and the behavior being unspecified for how non-supported pixel formats should be handled until relatively recently. As a result, it behaves that way so apps like tvtime don't break due to expecting legacy behavior. It has nothing to do with the resolution - in fact the driver is doing exactly what it is supposed to (if you provide an unsupported resolution, the driver is supposed to pass back a resolution that is good and still return success). It's the application's responsibility to look at the resolution in the struct after the ioctl call and make sure it hasn't changed (and if it has, the app should adjust its expectations accordingly). Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
