On Tue, 29 Jul 2008 21:49:27 +0200 Hans de Goede j.w.r.degoede@hhs.nl wrote:
Gregor Jasny wrote:
On Tue, Jul 29, 2008 at 12:00:34PM +0200, Hans de Goede wrote:
Indeed, so iow I'm happy to conclude that thie is not a libv4l bug :)
Will you add a work around like the above in libv4l?
I don't like it much, but since Mauro thinks this is for the best I've added to my tree.
Thanks. You should notice that, even if we eventually change this at the drivers for example, on kernel 2.6.27, libv4l will work only with a driver that is newer than a kernel greater than 2.6.27 or upper. So, at libv4l, for sure you need to change it.
Cheers, Mauro