Hans de Goede wrote:
> Hi,
>
> On 03/22/2010 09:11 AM, Hans Verkuil wrote:
>> On Sunday 21 March 2010 00:14:25 Hans de Goede wrote:
>>> Hi,
>>>
>>> On 03/20/2010 10:21 AM, Hans Verkuil wrote:
Hi all!
The second phase that needs to be done to remove the v4l1 support
from the
>>>
Hans Verkuil wrote:
> On Sunday 21 March 2010 00:14:25 Hans de Goede wrote:
>> Yes it can, this for example already happens when using v4l1 apps with
>> uvcvideo (which is not possible without libv4l1).
>
> In what way does libv4l1 still depend on the kernel's v4l1 compat layer? And
> what is nee
Hi,
On 03/22/2010 09:11 AM, Hans Verkuil wrote:
On Sunday 21 March 2010 00:14:25 Hans de Goede wrote:
Hi,
On 03/20/2010 10:21 AM, Hans Verkuil wrote:
Hi all!
The second phase that needs to be done to remove the v4l1 support from the
kernel is that libv4l1 should replace the v4l1-compat code
On Sunday 21 March 2010 00:14:25 Hans de Goede wrote:
> Hi,
>
> On 03/20/2010 10:21 AM, Hans Verkuil wrote:
> > Hi all!
> >
> > The second phase that needs to be done to remove the v4l1 support from the
> > kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
> >
> > I do no
Hi,
On 03/20/2010 10:21 AM, Hans Verkuil wrote:
Hi all!
The second phase that needs to be done to remove the v4l1 support from the
kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
I do not know how complete the libv4l1 code is right now. I would like to
know in parti
On Saturday 20 March 2010 17:14:12 Devin Heitmueller wrote:
> On Sat, Mar 20, 2010 at 10:14 AM, Hans Verkuil wrote:
> > Of course, the best solution is to convert the V4L1 apps to using V4L2.
>
> On that topic, if I wanted to ensure that an application was not using
> any V4L1 functionality, is t
On Sat, Mar 20, 2010 at 10:14 AM, Hans Verkuil wrote:
> Of course, the best solution is to convert the V4L1 apps to using V4L2.
On that topic, if I wanted to ensure that an application was not using
any V4L1 functionality, is there any easy way to do that? For
example, can I just remove the #inc
On Saturday 20 March 2010 14:51:44 Chicken Shack wrote:
> Am Samstag, den 20.03.2010, 13:37 +0100 schrieb Hans Verkuil:
> > On Saturday 20 March 2010 13:17:15 Chicken Shack wrote:
> > > Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> > > > Hi all!
> > > >
> > > > The second phase t
Am Samstag, den 20.03.2010, 13:37 +0100 schrieb Hans Verkuil:
> On Saturday 20 March 2010 13:17:15 Chicken Shack wrote:
> > Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> > > Hi all!
> > >
> > > The second phase that needs to be done to remove the v4l1 support from the
> > > kerne
On Saturday 20 March 2010 13:17:15 Chicken Shack wrote:
> Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> > Hi all!
> >
> > The second phase that needs to be done to remove the v4l1 support from the
> > kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
> >
Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> Hi all!
>
> The second phase that needs to be done to remove the v4l1 support from the
> kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
>
> I do not know how complete the libv4l1 code is right now. I woul
Hi all!
The second phase that needs to be done to remove the v4l1 support from the
kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
I do not know how complete the libv4l1 code is right now. I would like to
know in particular whether the VIDIOCGMBUF/mmap behavior can be
12 matches
Mail list logo
