> > ... and would be a problem only if you want to use image sizes > > like 389 * 251. Is this really a problem? > > It probably isn't a problem, but I don't see any reason not to support > it - even if it is only for a few very specific applications. After all > - most of your changes are pretty much non backward compatible anyway, > so why not break the bytesperline thing as well, and keep the API as > universal as possible? i.e. remove it from pix_format and add a bytesperline value for each plane? How handle capture using read(2) then? Don't allow padding at all? Gerd -- Get back there in front of the computer NOW. Christmas can wait. -- Linus "the Grinch" Torvalds, 24 Dec 2000 on linux-kernel
