On Wed, 2009-04-29 at 13:33 +0200, Hans Verkuil wrote: > > On Wed, 2009-04-29 at 21:50 +1200, Michael Cree wrote: > >> On 29/04/2009, at 6:19 PM, Hans Verkuil wrote:
> >> > 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. > >> > > 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. I'll work on it. It looks like something that is aware of v4l device nodes (see below) - I'm wagering hald. > If you modprobe ivtv with file and ioctl debugging on, does > that give an indication of what is done with the device nodes? For the cx18 driver on a Fedora 10 system something runs through the /dev/video* nodes and /dev/radio* doing VIDIOC_QUERYCAP. I suspect the behavior will be the same for ivtv. I'll test on my other system when I get a chance. I have attached the startup from dmesg and /var/log/messages. I had the mythbackend disabled at boot. With the mythbackend enabled at startup, the results are the same except at 135 seconds after boot, the mythbackend opens up a TS stream looking for EIT/EPG data. > 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. More info to come... Regards, Andy
cx18-dig-fw-on-boot.tar.bz2
Description: application/bzip-compressed-tar
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
