From: Trent Piepho <xyzzy@speakeasy.org>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
linux-media@vger.kernel.org, video4linux-list@redhat.com,
Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Confusion in usr/include/linux/videodev.h
Date: Wed, 21 Jan 2009 00:54:07 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0901210048500.13170@shell2.speakeasy.net> (raw)
In-Reply-To: <3f9a31f40901202044n73a100faj96a6f3d3973bcc25@mail.gmail.com>
On Wed, 21 Jan 2009, Jaswinder Singh Rajput wrote:
> On Wed, Jan 21, 2009 at 7:20 AM, Mauro Carvalho Chehab
> <mchehab@infradead.org> wrote:
> > On Wed, 21 Jan 2009 07:10:38 +0530
> > Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> >
> >> usr/include/linux/videodev.h is giving 2 warnings in 'make headers_check':
> >> usr/include/linux/videodev.h:19: leaks CONFIG_VIDEO to userspace where it is not valid
> >> usr/include/linux/videodev.h:314: leaks CONFIG_VIDEO to userspace where it is not valid
> >>
> >> Whole file is covered with #if defined(CONFIG_VIDEO_V4L1_COMPAT) || !defined (__KERNEL__)
> >>
> >> It means this file is only valid for kernel mode if CONFIG_VIDEO_V4L1_COMPAT is defined but in user mode it is always valid.
> >
> > V4L1 is the old deprecated userspace API for video devices. It is still
> > required by some userspace applications. So, on userspace, it should be
> > included. Also, this allows that one userspace app to be compatible with both
> > V4L2 API (the current one) and the legacy V4L1 one.
> >
> > It should be noticed that are still a few drivers using the legacy API yet to
> > be converted.
> >
>
> If you have no objections then I will make a patchset which do followings:
> 1. Remove #if defined(CONFIG_VIDEO_V4L1_COMPAT) || !defined
> (__KERNEL__) from include/linux/videodev.h
> 2. cover all #include <linux/videodev.h> with #ifdef
> CONFIG_VIDEO_V4L1_COMPAT in kernel
>
> By this way, we can satisfy both kernel space and userspace issue and
> also get rid of above warnings.
>
> If you have better suggestion then let me know.
That sounds like it will add a mess of #if's. How about this?
diff -r 29c5787efcda linux/include/linux/videodev.h
--- a/linux/include/linux/videodev.h Thu Jan 15 09:07:03 2009 -0800
+++ b/linux/include/linux/videodev.h Wed Jan 21 00:51:45 2009 -0800
@@ -15,7 +15,8 @@
#include <linux/ioctl.h>
#include <linux/videodev2.h>
-#if defined(CONFIG_VIDEO_V4L1_COMPAT) || !defined (__KERNEL__)
+#if (defined(__KERNEL__) && defined(CONFIG_VIDEO_V4L1_COMPAT)) \
+ || !defined (__KERNEL__)
#define VID_TYPE_CAPTURE 1 /* Can capture */
#define VID_TYPE_TUNER 2 /* Can tune */
Now CONFIG_VIDEO_V4L1_COMPAT will only be used in the kernel.
next prev parent reply other threads:[~2009-01-21 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 1:40 Jaswinder Singh Rajput
2009-01-21 1:50 ` Mauro Carvalho Chehab
2009-01-21 4:44 ` Jaswinder Singh Rajput
2009-01-21 8:54 ` Trent Piepho [this message]
2009-01-21 8:59 ` Jaswinder Singh Rajput
2009-01-21 9:09 ` Arnd Bergmann
2009-01-21 9:51 ` Trent Piepho
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=Pine.LNX.4.58.0901210048500.13170@shell2.speakeasy.net \
--to=xyzzy@speakeasy.org \
--cc=jaswinder@kernel.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=video4linux-list@redhat.com \
/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
all inboxes | Powered by JetHome®