Hello, On 2/15/12 4:53 PM, Robert Abel wrote: > Basically, I found that libv4l and its conversion functions usually > choose to ignore v4l2_pix_format.bytesperline, which seems to work out > most of the time. > I patched the issue for bayer => rgbbgr24 and will possibly fix it for > bayer => yuv as well. > > Is there a general understanding that v4l media drivers must not pad > their data, or that libv4l is ignoring padding? > I've worked with some webcams in the past and they all padded their > data, so I'm wondering if assuming bytesperline = width was done on > purpose and by design of out of necessity (speed..?) or if it just > happened to work for most people? As far as I understand the V4L2 spec the bytesperline != width is no optional feature. If post your patches here I'll review them and add them to the development tree. Thanks, Gregor -- 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
