From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, v4l-dvb <linux-media@vger.kernel.org>
Subject: Re: RFC: Drop V4L1 support in V4L2 drivers
Date: Fri, 19 Mar 2010 16:27:19 -0300 [thread overview]
Message-ID: <4BA3D017.80504@redhat.com> (raw)
In-Reply-To: <4BA3CC3B.1050705@redhat.com>
Hans de Goede wrote:
>> 3) The removal of V4L1 means that the existing applications should not
>> try to include
>> videodev.h with newer kernels or their compilations will break (easy
>> to fix, but better
>> to remind application developers that may be reading this thread).
>> Also, the removal of
>> V4L1 compat means that all V4L1 only applications will stop working.
>> What's the current
>> status of webcam/TV/stream/radio/videotext/vbi applications? Just
>> yesterday, somebody
>> reported me a problem with radio crashing at the V4L1 compat layer. It
>> seemed that maybe
>> not all radio apps got converted. So, before dropping compat layer
>> support, we should
>> double check what apps will break.
>>
>
> I think the best way forward here is making libv4l1 completely independ
> of the kernel
> v4l1 compat layer. This isn't to hard to do, I could even copy over the
> necessary bits
> to compile v4l1 apps from linux/videodev.h to libv4l1.h, then the kernel
> can completely
> drop v4l1 compat for v4l2 drivers, but this will need some time...
You should notice that it is not just video stream here: you need to consider
also radio, vbi/teletext and tuning. The easiest way seems to start migrating
the v4l1 compat to userspace.
On the other hand, what applications are we talking about? Maybe it is just easier
to write a document pointing to an alternative application for each case.
--
Cheers,
Mauro
prev parent reply other threads:[~2010-03-19 19:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 7:59 RFC: Drop V4L1 support in V4L2 drivers Hans Verkuil
2010-03-19 8:04 ` Laurent Pinchart
2010-03-19 8:46 ` Hans Verkuil
2010-03-19 8:50 ` Laurent Pinchart
2010-03-19 9:03 ` Markus Rechberger
2010-03-19 13:47 ` Mauro Carvalho Chehab
2010-03-19 15:49 ` David Ellingsworth
2010-03-19 17:43 ` Mauro Carvalho Chehab
2010-03-19 18:00 ` David Ellingsworth
2010-03-19 18:12 ` Devin Heitmueller
2010-03-19 19:04 ` VDR User
2010-03-20 1:01 ` hermann pitton
2010-03-19 19:57 ` Mauro Carvalho Chehab
2010-03-19 19:06 ` Hans de Goede
2010-03-19 15:17 ` Andy Walls
2010-03-19 19:02 ` Hans de Goede
2010-03-19 13:01 ` Mauro Carvalho Chehab
2010-03-19 19:10 ` Hans de Goede
2010-03-19 19:27 ` Mauro Carvalho Chehab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA3D017.80504@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox