linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bhoel@despammed.com (Berthold Höllmann)
To: linux-hotplug@vger.kernel.org
Subject: UDEV rule for uploading firmware
Date: Sun, 24 Dec 2006 23:42:14 +0000	[thread overview]
Message-ID: <m2ejqoc149.fsf@pchoel.psh> (raw)

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"

But this gives only 

madfuload: --device not given, and DEVICE not set

in /var/log/messages when I attach the device.

I tried a lot with the command line, even hardcoding the next
predictable device name, but always get

madfuload: cannot open '/dev/.tmp-0-0': No such device or address

or

madfuload: cannot open /dev/bus/usb/005/028: No such file or directory

even when a manual call with /dev/bus/usb/005/028 is successfull
afterwards.

The original rule file name is 42-madfuload.rules and I tried to
increase the leading number to get the rules applied later in the
chain, but no go.

With SuSE 10.1 I fixed the problem by reactivating the usbfs mount by
fixing the /etc/fstab, but with openSuSE 10.2 I only get

# mount -a
mount: mount point /proc/bus/usb does not exist

# pre SuSE 10.1
#usbfs                /proc/bus/usb        usbfs      noauto
#0 0
# SuSE 10.1
/dev/bus/usb         /proc/bus/usb        usbfs      defaults              0 0

Is there a way to fix this problem in udev, do I have to change my
fstab entry or do I have to switch to a different tool like HAL?

Thanks
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

             reply	other threads:[~2006-12-24 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24 23:42 Berthold Höllmann [this message]
2006-12-25  0:09 ` UDEV rule for uploading firmware Berthold Höllmann
2006-12-26 14:58 ` Kay Sievers
2006-12-26 19:18 ` Berthold Höllmann

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=m2ejqoc149.fsf@pchoel.psh \
    --to=bhoel@despammed.com \
    --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).