All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Conrad <dr.stefan.conrad@t-online.de>
To: linux-hotplug@vger.kernel.org
Subject: DEVNAME not set when executing udev rule
Date: Thu, 03 Sep 2009 22:33:50 +0000	[thread overview]
Message-ID: <4AA0444E.3010908@t-online.de> (raw)

Hi,

I am trying to initialise a MidiSport USB interface with a udev rule
that triggers fxload to upload the firmware:

ACTION="add", SUBSYSTEM="usb", DEVPATH="/*.0",
ENV{PRODUCT}="763/1001/*", RUN+="/sbin/fxload -v -s
/usr/local/share/usb/maudio/MidiSportLoader.ihx -I
/usr/local/share/usb/maudio/MidiSport2x2.ihx -D $env{DEVNAME}"

The problem:
DEVNAME is not set in the environment.
Only DEVICE is set with the 'wrong' device file name under /proc/bus/usb
 which is deprecated and thus not useful.

System: Suse 11.1 Linux 2.6.27.29-0.1-default #1 SMP 2009-08-15 17:53:59
+0200 i686 athlon i386 GNU/Linux
udev Version: 128

What can I do to pass a valid device file name to fxload to upload the
firmware?

Thanks,

Stefan

             reply	other threads:[~2009-09-03 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 22:33 Stefan Conrad [this message]
2009-09-03 22:57 ` DEVNAME not set when executing udev rule Kay Sievers

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=4AA0444E.3010908@t-online.de \
    --to=dr.stefan.conrad@t-online.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.