From: Takashi Iwai <tiwai@suse.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: Pedro Lopez-Cabanillas <plcl@telefonica.net>,
Karsten Wiese <annabellesgarden@yahoo.de>,
usb-midi-fw-devel@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net
Subject: Re: Re: [usb-midi-fw-devel] proposal concerning cooperation of snd-usb-usx2x.o and rbtload
Date: Mon, 01 Sep 2003 15:25:30 +0200 [thread overview]
Message-ID: <s5hr830od2t.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030831093237.GB921@tuba.home>
At Sun, 31 Aug 2003 11:32:37 +0200,
Martin Langer wrote:
>
> On Sun, Aug 31, 2003 at 12:27:42AM +0200, Pedro Lopez-Cabanillas wrote:
> >
> > Yes, but it is easier to use the vendor and product id instead of usb dev full
> > path. Something like this:
> > pre-install snd-usb-us122 /usr/sbin/rbtload -P0x8007 -V0x1604 -p71 -Ius122.rbt
> > See the attached patch (untested).
> >
> > Yes again, and it is the same with post-install of course.
> > For USB devices on Linux, there is only a way to handle every event when you
> > plug and unplug a device: hotplug.
> >
>
> But it fails in case of one device if you do a re-plugin! The first plugin
> loads the firmware fine. Then you unplug your device and the module still
> remains in a status of sleep. If you plug in your device again it woke up,
> but it won't get a download of firmware and I don't saw a hotplug event in the
> logfile. I believe here is a solution in the ALSA USB corner neccessary. The
> download can not start by a hotplug event in this case! (My LEDs are still
> dark here!)
perhaps pre-install is not called because the module was not unloaded.
i thought hotplug can call the script in a usermap in prior to loading
the usb module ? (at least, the hotplug stuff on suse distro does it,
initializing the ALSA stuff before loading snd-usb-audio to keep the
consistency.) if so, the script should be triggered from hotplug.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-01 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308282352.54486.annabellesgarden@yahoo.de>
[not found] ` <200308291734.20533.plcl@telefonica.net>
2003-08-29 18:12 ` [usb-midi-fw-devel] proposal concerning cooperation of snd-usb-usx2x.o and rbtload Karsten Wiese
2003-08-29 19:59 ` Pedro Lopez-Cabanillas
2003-08-29 23:55 ` Martin Langer
[not found] ` <200308310027.42281.plcl@telefonica.net>
2003-08-31 9:32 ` Martin Langer
2003-09-01 13:25 ` Takashi Iwai [this message]
2003-09-02 21:18 ` Pedro Lopez-Cabanillas
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=s5hr830od2t.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=annabellesgarden@yahoo.de \
--cc=martin-langer@gmx.de \
--cc=plcl@telefonica.net \
--cc=usb-midi-fw-devel@lists.sourceforge.net \
/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.