mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
	Linux and Kernel Video <video4linux-list@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] Re: [PATCH] V4L: struct video_device corruption
Date: Sun, 23 Jul 2006 06:35:24 -0300	[thread overview]
Message-ID: <1153647324.22089.32.camel@praia> (raw)
In-Reply-To: <Pine.LNX.4.58.0607211536190.26854@shell2.speakeasy.net>

Ok, I had some time to fix the broken dependencies. Please look at the
two commits I did today.

One patch removes HAVE_V4L1 check at drivers. It also include some
checks for V4L1_COMPAT on some core files that should implement both
calls to provide support for V4L1 drivers.

The other fixes the broken dependencies for drivers that still need V4L1
to work properly.

Cheers,
Mauro.

Em Sex, 2006-07-21 às 15:55 -0700, Trent Piepho escreveu:
> On Fri, 21 Jul 2006, Mauro Carvalho Chehab wrote:
> > config VIDEO_BT848
> >         tristate "BT848 Video For Linux"
> >         depends on VIDEO_DEV && PCI && I2C && VIDEO_V4L2
> >
> > Argh! it should be V4L1 instead!
> 
> You can compile and use bt848 without V4L1 turned on.  It still has some
> V4L1 functions defined.
> 
> > > All these files include v4l2-dev.h and have HAVE_V4L1 defined when V4L1 is
> > > not turned on in Kconfig.  There files are all buildable when V4L1 is off;
> > > they don't depend on it in Kconfig.
> > Some of the above drivers are V4L2, like tda9887, tuner-core,
> > tuner-simple, msp3400, cs53l32a, tveeprom, wm87xx. Maybe they are just
> > including the wrong headers. We should try to change to videodev2.h and
> > see what happens with all those drivers. The ones that break should me
> > marked with the proper requirement on Kconfig.
> >
> > Some of they need some #ifdef inside. For example, compat_ioctl32 should
> > handle both APIs, since it is a generic code to fix 32 bit calls to 64
> > bit kernel.
> 
> I think this is pretty much what I've been saying.  Drivers should:
> A. Not include videodev.h, but use videodev2.h
> B. Include videodev.h, but be marked V4L1 in Kconfig
> C. #ifdef around videodev.h (and code that needs videodev.h), so it
>    is not included or needed when V4L1 is turned off.
Cheers, 
Mauro.


  reply	other threads:[~2006-07-23  9:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  4:43 oops in bttv Chuck Ebbert
2006-07-13  5:05 ` Greg KH
2006-07-13  5:24   ` Randy.Dunlap
2006-07-13  5:44     ` Andrew Morton
2006-07-15 23:08       ` [PATCH] V4L: struct video_device corruption Robert Fitzsimons
2006-07-16  1:31         ` Mauro Carvalho Chehab
2006-07-18  0:25           ` [v4l-dvb-maintainer] " Trent Piepho
2006-07-19 11:54             ` Mauro Carvalho Chehab
2006-07-19 15:36               ` Michael Krufky
2006-07-20 21:57               ` Trent Piepho
2006-07-21 12:26                 ` Mauro Carvalho Chehab
2006-07-21 20:06                   ` Trent Piepho
2006-07-21 20:30                     ` Mauro Carvalho Chehab
2006-07-21 22:55                       ` Trent Piepho
2006-07-23  9:35                         ` Mauro Carvalho Chehab [this message]
2006-07-24  2:16                           ` Trent Piepho
2006-07-24 12:34                             ` Mauro Carvalho Chehab
2006-07-24 22:06                               ` Trent Piepho
2006-07-25 17:59                                 ` Mauro Carvalho Chehab
2006-07-25  3:08           ` Andrew Morton
2006-07-25  7:57             ` [v4l-dvb-maintainer] " Manu Abraham
2006-07-25  8:42             ` Trent Piepho
2006-07-25  9:06               ` Andrew Morton
2006-07-25 12:28                 ` Mauro Carvalho Chehab

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=1153647324.22089.32.camel@praia \
    --to=mchehab@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    --cc=video4linux-list@redhat.com \
    --cc=xyzzy@speakeasy.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

all inboxes | Powered by JetHome®