Enrik Berkhan wrote:
Nonsense, its bNumConfigurations, of course.
Now I have the following working ruleset:
SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{product}=="MSP-FET430UIF JTAG Tool"
\
SYSFS{bNumConfigurations}=="1" \
RUN+="/sbin/modprobe ti_usb_3410_5052 vendor_3410=0x%s{idVendor}
product_3410=0x%s{idProduct}"
SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{product}=="MSP-FET430UIF JTAG Tool"
\
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"
Thus looks about right from what I have found so far. However, on Fedora
Core 5 it still doesn't work. I get a failure to download the firmware.
I probed inside the driver with some printk's. On the FC5 machine it is
trying to download to a different endpoint. I haven't had time to work
out why. Is this some permissions thing? I know you need to allow for
SELinux on an FC5 machine, but I thought that was just at the time of
generating the /dev/xxx entries.
Steve
