From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: What to do with videodev.h
Date: Wed, 26 Jan 2011 09:36:07 -0200 [thread overview]
Message-ID: <4D400727.3000205@redhat.com> (raw)
In-Reply-To: <613f734c5a59a342c587769455e939af.squirrel@webmail.xs4all.nl>
Em 26-01-2011 07:47, Hans Verkuil escreveu:
>> Hi Hans,
>>
>> Em 26-01-2011 06:26, Hans de Goede escreveu:
>>> Hi All,
>>>
>>> With v4l1 support going completely away, the question is
>>> raised what to do with linux/videodev.h .
>>>
>>> Since v4l1 apps can still use the old API through libv4l1,
>>> these apps will still need linux/videodev.h to compile.
>>>
>>> So I see 3 options:
>>> 1) Keep videodev.h in the kernel tree even after we've dropped
>>> the API support at the kernel level (seems like a bad idea to me)
>>
>> That's a bad idea.
>>
>>> 2) Copy videodev.h over to v4l-utils as is (under a different name)
>>> and modify the #include in libv4l1.h to include it under the
>>> new name
>>> 3) Copy the (needed) contents of videodev.h over to libv4l1.h
>>
>> I would do (3). This provides a clearer signal that V4L1-only apps need
>> to use libv4l1, or otherwise will stop working.
>
> I agree with this.
>
>> Of course, the better is to remove V4L1 support from those old apps.
>> There are a number of applications that support both API's. So, it
>> is time to remove V4L1 support from them.
>
> So who is going to do that work? That's the problem...
>
> But ensuring that they no longer compile is a good start :-)
>
> Although most have a private copy of videodev.h as part of their sources.
The ones that don't have videodev.h will compile-break on distros. So distros
will need to do something to keep it working, or they'll just drop those
pre-historic beasts. It is the Evolution Theory working for software:
to adapt or to be extinguished ;)
The ones that are shipped with videodev.h and weren't converted to libv4l
might eventually stay there for a longer time, as people will only notice
when a bug will be reported. If we know what are those apps, then we can
add a blacklist at linuxtv and/or contact interested parties on fixing/removing
them.
We should touch the tools that we care of. Maybe Devin could change tvtime,
we should remove V4L1 driver from xawtv3/xawtv4.
Regards,
Mauro
next prev parent reply other threads:[~2011-01-26 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 8:26 What to do with videodev.h Hans de Goede
2011-01-26 9:07 ` Mauro Carvalho Chehab
2011-01-26 9:47 ` Hans Verkuil
2011-01-26 11:36 ` Mauro Carvalho Chehab [this message]
2011-01-26 14:31 ` Devin Heitmueller
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=4D400727.3000205@redhat.com \
--to=mchehab@redhat.com \
--cc=dheitmueller@kernellabs.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