From: berthold@xn--hllmanns-n4a.de (Berthold Höllmann)
To: linux-hotplug@vger.kernel.org
Subject: Re: UDEV rule for uploading firmware
Date: Tue, 26 Dec 2006 19:18:10 +0000 [thread overview]
Message-ID: <m2psa68o0d.fsf@pchoel.psh> (raw)
In-Reply-To: <m2ejqoc149.fsf@pchoel.psh>
"Kay Sievers" <kay.sievers@vrfy.org> writes:
> On 12/25/06, Berthold Höllmann <berthold@xn--hllmanns-n4a.de> wrote:
>> I try to fix a UDEV rule for uploading firmware for an USB audio
>> device. The tool madfuload has to get the device name in either the
>> DEVICE environment variable or via a command line switch. The original
>> rule as delivered with the program is:
>>
>> ACTION="add", SUBSYSTEM="usb", DEVPATH="/*.0", ENV{PRODUCT}="763/2806/*", RUN+="/usr/local/sbin/madfuload -l -3 -f /usr/local/share/usb/maudio/ma006100.bin"
>
> Try hooking into the "usb_device" event, not "usb". The device node
> may not be around at the time you receive the "usb" event. You need to
> match on sysfs vendor/product values to indentify your device then.
> The device-node path is available in the event environment of the
> "usb_device" event so you can pass it to the called tool.
Thanks for your help. For the records, the working solution (at least
for me) is:
ACTION="add", SUBSYSTEM="usb_device", SYSFS{idVendor}="0763", SYSFS{idProduct}="2806", RUN+="/usr/local/sbin/madfuload -l -3 -f /usr/local/share/usb/maudio/ma006100.bin -D $env{DEVNAME}"
Kind regards
Berthold
--
berthold@xn--hllmanns-n4a.de / <http://höllmanns.de/>
bhoel@web.de / <http://starship.python.net/crew/bhoel/>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-12-26 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 23:42 UDEV rule for uploading firmware Berthold Höllmann
2006-12-25 0:09 ` Berthold Höllmann
2006-12-26 14:58 ` Kay Sievers
2006-12-26 19:18 ` Berthold Höllmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2psa68o0d.fsf@pchoel.psh \
--to=berthold@xn--hllmanns-n4a.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).