linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jasem Mutlaq" <mutlaqja@ikarustech.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: Loading firmware
Date: Tue, 14 Oct 2008 17:24:42 +0000	[thread overview]
Message-ID: <007f01c92e21$c1949b30$44bdd190$@com> (raw)
In-Reply-To: <003c01c92d81$89978710$9cc69530$@com>

> That's not a USB _device_, it's a (not interesting) USB endpoint.
> 
> > 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).
> 
> That still works.

I tried it on OpenSUSE 11 and it doesn't, $env{BUSNUM} and $env{DEVNUM} are empty strings, $env{DEVNAME} returns the USB endpoint which I can't pass to fxload.

> Why not just use $DEVNAME?
>   RUN+="/sbin/fxload <firmware file option> -D $env{DEVNAME}"

This is what I get:

run_program: '/sbin/fxload' (stderr) '/dev/usbdev1.24_ep82: No such device or address'
run_program: '/sbin/fxload' returned with status 255

Thus far, fxload only works if it is passed something in the form of /dev/bus/usb/XXX/YYY

Cheers,
Jasem




  parent reply	other threads:[~2008-10-14 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 22:17 Loading firmware Jasem Mutlaq
2008-10-14  0:18 ` Dan Nicholson
2008-10-14 13:16 ` Jasem Mutlaq
2008-10-14 14:33 ` Kay Sievers
2008-10-14 17:24 ` Jasem Mutlaq [this message]
2008-10-14 17:46 ` Kay Sievers
2008-10-14 18:08 ` Dan Nicholson
2008-10-15 12:05 ` Jasem Mutlaq
2008-10-15 12:32 ` Kay Sievers
2008-10-15 12:44 ` Jasem Mutlaq
2008-10-15 13:22 ` Kay Sievers
2008-10-15 13:59 ` Jasem Mutlaq

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='007f01c92e21$c1949b30$44bdd190$@com' \
    --to=mutlaqja@ikarustech.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).