Re: RFC: howto handle driver changes which require libv4l x.y ?

Hi, On 07/07/2009 04:35 PM, Mauro Carvalho Chehab wrote: Em Tue, 7 Jul 2009 15:55:59 +0200 Erik Andrénerik.and...@gmail.com escreveu: 2009/7/7 Hans de Goedehdego...@redhat.com: Hi All, So recently I've hit 2 issues where kernel side fixes need to go hand in hand with libv4l updates to not

RFC: howto handle driver changes which require libv4l x.y ?

Hi All, So recently I've hit 2 issues where kernel side fixes need to go hand in hand with libv4l updates to not cause regressions. First lets discuss the 2 cases: 1) The pac207 driver currently limits the framerate (and thus the minimum exposure time) because at higher framerate the cam

Re: RFC: howto handle driver changes which require libv4l x.y ?

2009/7/7 Hans de Goede hdego...@redhat.com: Hi All, So recently I've hit 2 issues where kernel side fixes need to go hand in hand with libv4l updates to not cause regressions. First lets discuss the 2 cases: 1) The pac207 driver currently limits the framerate (and thus   the minimum

Re: RFC: howto handle driver changes which require libv4l x.y ?

Em Tue, 7 Jul 2009 15:55:59 +0200 Erik Andrén erik.and...@gmail.com escreveu: 2009/7/7 Hans de Goede hdego...@redhat.com: Hi All, So recently I've hit 2 issues where kernel side fixes need to go hand in hand with libv4l updates to not cause regressions. First lets discuss the 2