I found the cause of my problem, I was using devfs instead of udev + sysfs :-) Now the firmware loads fine, I just have som problems with the lirc-device but I think I can work that out.
Thanks for helping me! /Daniel Csaba Paradi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > > >> echo "SYSFS: " $SYSFS >> /tmp/logfile >> echo "DEVPATH: " $DEVPATH >> /tmp/logfile >> > It is a good idea to mark somehow the log lines, example > this way: > echo "before_loading_1_SYSFS: " $SYSFS >> /tmp/logfile > > It is more easier to trace the result of the hotplug script this way. > >> if [ -f "$FIRMWARE_DIR/$FIRMWARE" ]; then >> echo 1 > $SYSFS/$DEVPATH/loading >> >> echo "SYSFS: " $SYSFS >> /tmp/logfile >> > echo "after_loading_1_SYSFS: " $SYSFS >> /tmp/logfile > >> echo "DEVPATH: " $DEVPATH >> /tmp/logfile >> >> cp "$FIRMWARE_DIR/$FIRMWARE" $SYSFS/$DEVPATH/data >> > echo "after_data_SYSFS: " $SYSFS >> /tmp/logfile > If you put 'sleep 3' here, you can check the sysfs manually during > firmware loading with something like this 'cat > /proc/class/firmware/0000:00:0f.0/loading' > Maybe not a bad idea to log the executing status of the 'cp' command, as > I know the kernel is not logging the execution errors of the hotplug > script. > >> echo 0 > $SYSFS/$DEVPATH/loading >> >> echo "SYSFS: " $SYSFS >> /tmp/logfile >> echo "DEVPATH: " $DEVPATH >> /tmp/logfile >> echo "FIRMWARE_DIR: " $FIRMWARE_DIR >> /tmp/logfile >> echo "FIRMWARE: " $FIRMWARE >> /tmp/logfile >> >> > > If everything is OK in the hotplug script, than the only possible way is > to trace the kernel/drivers/base/firmware_class.c . Log firmware size in > the hotplug script and also in the kernel. > > - -- > Csaba Paradi > [EMAIL PROTECTED] > Ruby Co. > +36 30 9494542 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFDzk02e4buY9quE2URAtgTAJ97jbNZt6BzRZPuSfTsR9hPdqiuyACaA4YW > lnPHBrLeWdKYhjwUTYjhaoM= > =QzvQ > -----END PGP SIGNATURE----- > > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
