> > The defined method involves providing a script in /etc/hotplug/usb/...
> > invoking "fxload" with the right firmware for the particular device IDs.
> > http://linux-hotplug.sourceforge.net/?selected=usb describes it
> > (at the end of the page).
> >
> I did that. Added to usb.handmap the lines:
> bpide6 0x0003 0x0ac9 0x1003 0x0000 0x0000
> 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00000000
> bpckusb 0x0003 0x0ac9 0x0000 0x0000 0x0000
> 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00000000
> ...
Two comments ...
First, it looks like you've added three lines for each type of firmware.
That won't work correctly, the "modules.usbmap" format is one line
per "usb_device_id". I could believe that the failures you're seeing
are because you're using more than one line per entry ... it's sure
acting as if it thought "0x0" was a module name!
Second, it'd probably be simpler to have one script "backpack"
that switches on vendor/product. Here's what one script I use
does, you could modify it:
#!/bin/sh
case $PRODUCT in
# EZ-USB FX2 development kit ... pre-renumeration
4b4/8613/*)
FIRMWARE=/root/fx2/bulksrc.hex
if [ -x /usr/bin/logger ]; then
/usr/bin/logger -t $0 "load $FIRMWARE for $PRODUCT to $DEVICE"
fi
/sbin/fxload -2 -I $FIRMWARE
;;
# same script is invoked post-renumeration, does nothing.
esac
Of course it'd be as easy to have the "case" just set FIRMWARE,
and do the rest afterwards if it got set.
> In the dir /etc/hotplug/usb I created the files:
> bpatapi5 bpatapi6 bpckusb bpide5 bpide6
>
> And a dir, "bpckusbfw", where I put the appropriate hex files
Sounds right, though I'll suggest just one script "backpack"
and one directory "backpack-fw". (I like simpler naming... :)
Or maybe named to match the driver you use, which is what I did
above
> Am I missing something?
I think likely your problem was point 1 above.
> I kludged this to allow loading, so I've had it work here, but this still
> dosen't resolve Olivers issue with firmware reloading with power
> management.
Is that actually an issue for this device though? Did you verify?
What are your symptoms?
> In addition, there is no central package of firmware, so do I
> make our own firmware RPM/deb? No good answer on the linux-hotplug list.
I don't remember seeing the question. For GPL'd firmware, I can
imagine a package associated with the hotplug scripts. If it's not
GPL'd, it'd seem that some other RPM/deb distribution would be
appropriate.
> (IMHO scripts for loading firmware should have a separate mechanism from
> notifying/launching applications to use a device)
Separate discussion, which should be on the hotplug list if you
want to pursue it. I'd call that a policy versus mechanism issue.
The same mechanism _ought_ to support many policies, and
IMO "load firmware" is as much a policy as "modprobe" or "start
application Z".
The tricky part is policies that involve interacting with a user or
administrator -- "what desktop?" Hotplug is set up to be a system
mechanism that doesn't interact. It needs some standard hook
to send notificatiosn to tools on some desktop (local, remote, etc).
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
