On Tuesday 17 July 2007 17:00:40 Nicholas Fearnley wrote:
> On 17 Jul 2007, at 15:08, Tyler Trafford wrote:
> > Nicholas Fearnley wrote:
> >> My hotplug script is custom also.  It is being called for sure,
> >> but not by IVTV.  I have something along the lines of:
> >>
> >> echo >> "I'm being called for $FIRMWARE"
> >>
> >> Which does show a couple of things, but not IVTV.  The IVTV INIT
> >> simply fails to load the firmware for the detected  PVR-150 card. 
> >> It fails on retry also (with the 'firmware' suggestion).
> >>
> >> So hotplug is there, it's callable (it's getting called!), but not
> >> by IVTV.  IVTV is detecting the card fine as a PVR-150, but just
> >> not calling hotplug at all.
> >
> > Is ivtv compiled as a module?
>
> No, compiled in kernel.  Should that cause a problem?  I should
> probably try and compile as a mod and get back to you.
>
> It would be cool to have it in kernel though from a 'firmware' build
> perspective - less to miss, and I can disable module loading from the
> kernel to make it tighter.

I've never actually tested having ivtv compiled in the kernel, I always 
tested it as a module. I'm not sure how firmware loading is supposed to 
work for in-kernel drivers. I suspect that by the time the driver is 
initialized the hotplug daemons may not be active yet.

Regards,

        Hans

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to