[ivtv-users] Delay loading v4l-cx25840.fw
Michael Cree
mcree at orcon.net.nz
Fri May 1 02:30:00 CEST 2009
On 29/04/2009, at 11:06 PM, Andy Walls wrote:
> On Wed, 2009-04-29 at 21:50 +1200, Michael Cree wrote:
>> On 29/04/2009, at 6:19 PM, Hans Verkuil wrote:
>>> On Wednesday 29 April 2009 04:56:53 Andy Walls wrote:
>>>> The ivtv and cx25840 module should be deferring the cx2584x
>>>> firmware
>>>> load until the chip is actually needed. Then the actual loading is
>>>> spun
>>>> off to some transient kernel thread to get the job done in parallel
>>>> with
>>>> other processes.
>>>
>>> What does surprise me here is that the fw is loaded right after the
>>> driver
>>> was loaded, which does suggest that some process is opening one of
>>> the
>>> device nodes since the fw load is only done on the first open.
>>
>> Loading lirc drivers maybe?
>
> It has to be something from userspace on the /dev/video* or /dev/
> radio*
> nodes. I'm not sure lirc would cause this.
Okay. I mentioned it because I know that on my system the firmware
gets loaded about the time the lircd script is run. But on closer
examination of the startup messages I see that Hal gets loaded then
the ivtv firmware load messages come, then lircd is loaded so your
suggestion that:
> I've always
> assumed it was either udev or hal or some some other automatic process
> that mucks with device nodes.
looks likely.
Unfortunately the evidence I mention above of Hal loading then ivtv
firmware is not recorded in my system logs - I just saw it pass by on
the console screen. I think there is a flag I can change in the
startup procedure that will cause a lot more information to be
recorded. I'll explore trying to get a useful start up log over the
weekend.
Cheers
Michael.
More information about the ivtv-users
mailing list