> 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.
>
> On my systems (Fedora 9 & 10) IIRC it happens early too. I've always
> assumed it was either udev or hal or some some other automatic process
> that mucks with device nodes.
It would be nice if you could track down who is messing around with those
device nodes. If you modprobe ivtv with file and ioctl debugging on, does
that give an indication of what is done with the device nodes?
I'm running a non-standard linuxfromscratch system which doesn't use hal.
On that system the fw is really loaded only when it is opened for use for
the first time.
Depending on what process is doing what with the device nodes I may be
able to optimize the driver for that. It's really annoying to have this fw
loaded at boot time, esp. if you have one or more PVR-500 cards.
Regards,
Hans
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
