[Ffmpeg-devel] Failing to initialize DV interface

[Jim Mccann]

Hello all,
	I was recently having a similar problem as Maarten described below  
(in 2003...) I poked through the sources and, lo, the fix that  
Charlie provides (see below) still isn't included (at least in the  
svn trunk) and still works (at least for me)!

	So I figured I'd "bump" this and see if anyone feels like patching  
it. (Note: I refrain from doing it myself because, well, I'm lazy.  
And I just did the hack-y thing and copied my kernel header over the  
included header, which almost certainly breaks things for 2.4 systems.)

Good day,

--Jim

> On Thu, 2003-07-24 at 10:01, Maarten De Boer wrote:
> > Hello,
> >
> > I just installed Debian sid, the Linux 2.6.0-test1 kernel, and  
> today's
> > (23-7) ffmpeg CVS snapshot. However, I don't get ffmpeg to work  
> with my
> > consumer DV camera. Everything worked fine with my previous  
> install (Debian
> > woody, kernel 2.4.21). Any suggestions? Let me know if I can  
> provide any
> > additional data that would be helpfull.
>
> The problem is in the ioctls and the header files used by ffmpeg to
> access dv1394.
>
> Translation should be as simple as changing:
>
> DV1394_INIT to DV1394_IOC_INIT
> DV1394_STATUS to DV1394_IOC_STATUS
> etc.
>
> Do a grep for ioctl in libavformat/dv1394.c to locate them.
>
> You will also need to include the dv1394.h which is included with the
> kernel, rather than libavformat/dv1394.h.
>
> I'm not sure what the standard approach to this is, but I've been
> playing with adding:
>
>  -I/lib/modules/`uname -r`/build/drivers
>
> to the c flags (though it's kind of inflexible and should be checked/
> allow overriding in the configure script and also it should add the
> build/include directory so that the linux/ioctl.h header files are
> consistently picked up).
>
> Then you should use:
>
>  #include <ieee1394/dv1394.h>
>
> in the source.
>
> Alternatively, copying ieee1394/dv1394.h and ieee1394/ieee1394- 
> ioctls.h
> into libavformat might do it.
>
> I'm kind of curious how this one will be resolved longer term in  
> ffmpeg,
> since other apps and libs are affected by this.
>
> Cheers,
>
> Charlie