From: Hans de Goede <hdegoede@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: What to do with videodev.h
Date: Wed, 26 Jan 2011 09:26:20 +0100 [thread overview]
Message-ID: <4D3FDAAC.2020303@redhat.com> (raw)
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)
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'm not sure where I stand wrt 2 versus 3. Comments anyone?
Regards,
Hans
next reply other threads:[~2011-01-26 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 8:26 Hans de Goede [this message]
2011-01-26 9:07 ` What to do with videodev.h Mauro Carvalho Chehab
2011-01-26 9:47 ` Hans Verkuil
2011-01-26 11:36 ` Mauro Carvalho Chehab
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=4D3FDAAC.2020303@redhat.com \
--to=hdegoede@redhat.com \
--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