I altered firmware.agent as follows:
------------------------------------------------------------------------
[EMAIL PROTECTED]:~# cat /etc/hotplug/firmware.agent
#!/bin/sh
#
# Firmware-specific hotplug policy agent.
#
# Kernel firmware hotplug params include:
#
# ACTION=%s [add or remove]
# DEVPATH=%s [in 2.5 kernels, /sys/$DEVPATH]
# FIRMWARE=%s
#
# HISTORY:
#
# 24-Jul-2003 Initial version of "new" hotplug agent.
#
# $Id: firmware.agent,v 1.4 2004/09/20 21:23:51 kroah Exp $
#
cd /etc/hotplug
. ./hotplug.functions
# DEBUG=yes export DEBUG
# directory of the firmware files
FIRMWARE_DIR=/lib/firmware
echo "SYSFS: " $SYSFS >> /tmp/logfile
echo "DEVPATH: " $DEVPATH >> /tmp/logfile
# mountpoint of sysfs
SYSFS=$(sed -n 's/^.* \([^ ]*\) sysfs .*$/\1/p' /proc/mounts)
echo "SYSFS: " $SYSFS >> /tmp/logfile
echo "DEVPATH: " $DEVPATH >> /tmp/logfile
# use /proc for 2.4 kernels
if [ "$SYSFS" = "" ]; then
SYSFS=/proc
fi
echo "SYSFS: " $SYSFS >> /tmp/logfile
echo "DEVPATH: " $DEVPATH >> /tmp/logfile
#
# What to do with this firmware hotplug event?
#
case "$ACTION" in
add)
if [ ! -e $SYSFS/$DEVPATH/loading ]; then
sleep 1
fi
echo "SYSFS: " $SYSFS >> /tmp/logfile
echo "DEVPATH: " $DEVPATH >> /tmp/logfile
if [ -f "$FIRMWARE_DIR/$FIRMWARE" ]; then
echo 1 > $SYSFS/$DEVPATH/loading
echo "SYSFS: " $SYSFS >> /tmp/logfile
echo "DEVPATH: " $DEVPATH >> /tmp/logfile
cp "$FIRMWARE_DIR/$FIRMWARE" $SYSFS/$DEVPATH/data
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
else
echo -1 > $SYSFS/$DEVPATH/loading
echo "SYSFS: " $SYSFS >> /tmp/logfile
echo "DEVPATH: " $DEVPATH >> /tmp/logfile
fi
;;
remove)
;;
*)
mesg "Firmware '$ACTION' event not supported"
exit 1
;;
esac
------------------------------------------------------------------------
I got this output:
[EMAIL PROTECTED]:~# cat /tmp/logfile
SYSFS:
DEVPATH: /class/firmware/i2c-0
SYSFS:
DEVPATH: /class/firmware/i2c-0
SYSFS: /proc
DEVPATH: /class/firmware/i2c-0
SYSFS: /proc
DEVPATH: /class/firmware/i2c-0
SYSFS: /proc
DEVPATH: /class/firmware/i2c-0
SYSFS: /proc
DEVPATH: /class/firmware/i2c-0
FIRMWARE_DIR: /lib/firmware
FIRMWARE: v4l-cx25840.fw
SYSFS:
DEVPATH: /class/firmware/i2c-0
SYSFS:
DEVPATH: /class/firmware/i2c-0
SYSFS: /proc
DEVPATH: /class/firmware/i2c-0
SYSFS:
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS:
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS: /proc
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS: /proc
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS: /proc
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS: /proc
DEVPATH: /class/firmware/0000:00:0f.0
FIRMWARE_DIR: /lib/firmware
FIRMWARE: v4l-cx2341x-enc.fw
SYSFS:
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS:
DEVPATH: /class/firmware/0000:00:0f.0
SYSFS: /proc
DEVPATH: /class/firmware/0000:00:0f.0
------------------------------------------------------------------------
Can you see anything strange?
Best regards,
Daniel
----- Original Message -----
From: "Csaba Paradi" <[EMAIL PROTECTED]>
To: "User discussion about IVTV" <[email protected]>
Sent: Wednesday, January 18, 2006 1:08 PM
Subject: Re: [ivtv-users] Firmware load error, ivtv 0.4.2, PVR-150
> Trace the firmware.agent line-by-line !
> ( example with 'echo $SYSFS >> /tmp/logfile' )
>
> My problem was with the line:
> "SYSFS=$(sed -n 's/^.* \([^ ]*\) sysfs .*$/\1/p' /proc/mounts)"
> The sed gave to matched lines, and after it the SYSFS variable was bad,
> and the whole script is failed. This why the kernel thinks that there is
> firmware load timeout.
>
> I hope this helps!
>
> --
> Csaba Paradi
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
