On Tue, Oct 14, 2008 at 10:46 AM, Kay Sievers <kay.sievers@xxxxxxxx> wrote:
> On Tue, Oct 14, 2008 at 7:24 PM, Jasem Mutlaq <mutlaqja@xxxxxxxxxxxxxx> wrote:
>
>> Thus far, fxload only works if it is passed something in the form of /dev/bus/usb/XXX/YYY
>
> It should work with any usb device device node, forget the endpoints,
> match on a usb device. You look at the wrong events, you get a bunch
> of them on plugin, only one of them will be the one that works with
> fxload, and definitely not the one with the *_ep*. The right one
> should have: DEVTYPE=usb_device set.
For reference, look at the rule that actually creates the /dev/bus/usb links:
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
To get some information about what's going on:
path=`udevadm info --query=path --name=/dev/bus/usb/$your/$node`
udevadm test $path
udevadm info --attribute-walk --path=$path
I suspect you'll end up with something like this (make sure it runs
somewhere after the above rule that sets the name):
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
ATTR{idVendor}=="xxxx", ATTR{idProduct}=="yyyy", RUN+="/sbin/fxload -I
/lib/firmware/foo.hex -D $env{DEVNAME}"
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
