From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Dan Nicholson" <dbn.lists@gmail.com>
Date: Tue, 14 Oct 2008 00:18:04 +0000
Subject: Re: Loading firmware
Message-Id: <91705d080810131718kcc8dffdm78e66daf86011dd9@mail.gmail.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <003c01c92d81$89978710$9cc69530$@com>
In-Reply-To: <003c01c92d81$89978710$9cc69530$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

On Mon, Oct 13, 2008 at 3:17 PM, Jasem Mutlaq <mutlaqja@ikarustech.com> wrote:
> Hello,
>
> I need to load firmware to a USB camera via fxload. The problem is that
> fxload requires a path such as /dev/bus/usb/001/002 in order to load the
> firmware. So I wrote a udev rules file to do just that, however, the only
> useful variable I can obtain now is %k, and I get something in the form of
> usbdev1.2_ep00 which I then need to parse in some regexp magic in order to
> extract the bus and dev num in order to construct the full path. I used to
> be able to pull devnum and busnum ($env{BUSNUM}) but not anymore (using
> openSUSE 11). Now I have a loader script that parses %k and constructs the
> path. But this is only a hack and not a real solution, is there a way to get
> the full path so I can pass it to fxload without resorting to these
> desperate measures? Appreciate your help.

Does something like this help:

<some test to determine your device>, ACTION="add", RUN+="/sbin/fxload
 -D /dev/$name"

Where $name points to the device name and will be set earlier by the
default rules.

--
Dan