We are just building against current v4l, not a particular kernel. In
that struct, 'dev' is 2.6 only, for instance. I think removing that
priv isn't the right thing now that I think about it, we probably need a
call to pci_set_drvdata() there... I'll have to look into it.
John Harvey wrote:
Not sure but if we are building against our own or the particular kernel's
(in the long run) why would there be any ifdef's like this in the 0.5 code
for v4l2 stuff?
Shouldn't we just remove the #ifdef & #endif lines?
John
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Tyler Trafford
Sent: 18 October 2005 23:16
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] 2832 and v4l CVS not in sync
It also looks like (from right below the 'priv' code) in this:
#ifdef LINUX26
s->v4l2dev->dev = &itv->dev->dev;
s->v4l2dev->release = video_device_release;
#endif /* LINUX26 */
The 'release' part shouldn't be inside that ifdef anymore, right?
-Tyler
--
Tyler Trafford
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
