From: "Ivica Bukvic" <ico@fuse.net>
To: 'Jaroslav Kysela' <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net
Subject: RE: [Alsa-user] [lack of] dynamic detection/loading of modules
Date: Thu, 27 Feb 2003 08:05:49 -0500 [thread overview]
Message-ID: <000b01c2de60$f31dd340$aa1f830a@ICO> (raw)
In-Reply-To: <Pine.LNX.4.44.0302271037550.1109-100000@pnote.perex-int.cz>
I presume I need to blacklist the snd-usb-audio/midi in the
/etc/hotplug/blacklist for this to work?
Also, do I need to make any other changes or as long as I put this
script into the /etc/hotplug/ dir I am set?
Thanks for the great script!
(is this going to become a standard part of the alsa driver? I sure hope
so :-)
Ico
> Note that the problem is already solveable with a nice way. The SuSE
uses
> this hotplug script:
>
> -------------------------
> #!/bin/bash
> #
> # /etc/hotplug/usb/alsasound
> #
> # Sets up newly plugged in USB audio/MIDI devices.
> #
>
> if [ "$INTERFACE" != "" ]; then
> IFS=/
> set $INTERFACE ''
> usb_bInterfaceClass=$1
> usb_bInterfaceSubClass=$2
> usb_bInterfaceProtocol=$3
> IFS="$DEFAULT_IFS"
> fi
>
> function add_alsa () {
> # check alsa is already running
> if [ ! -d /proc/asound ]; then
> # start alsasound script, so that static devices are properly
loaded
> echo "Starting ALSA..."
> /etc/init.d/alsasound start >/dev/null 2>&1
> fi
> /sbin/modprobe snd-usb-audio
> if [ "$usb_bInterfaceSubClass" != "0x01" ]; then
> /sbin/modprobe snd-usb-midi
> fi
> }
>
> function remove_alsa () {
> /sbin/modprobe -r snd-usb-midi
> /sbin/modprobe -r snd-usb-audio
> }
>
> case "$ACTION" in
> add)
> add_alsa
> ;;
> remove)
> remove_alsa
> ;;
> esac
> -----------------------
>
> So, if no static ALSA drivers are loaded, load them before usb module
is
> inserted. Nice way to solve all your problems.
>
> Jaroslav
>
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-27 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 3:22 [lack of] dynamic detection/loading of modules Ivica Bukvic
2003-02-27 3:33 ` Paul Davis
2003-02-27 20:35 ` Fernando Pablo Lopez-Lezcano
2003-02-28 14:51 ` Takashi Iwai
2003-03-05 3:01 ` Fernando Pablo Lopez-Lezcano
2003-03-05 10:03 ` Takashi Iwai
2003-03-05 18:03 ` [Alsa-user] " Fernando Pablo Lopez-Lezcano
2003-03-05 20:20 ` Fernando Pablo Lopez-Lezcano
2003-03-05 3:05 ` Fernando Pablo Lopez-Lezcano
2003-02-27 9:40 ` [Alsa-user] " Jaroslav Kysela
2003-02-27 13:05 ` Ivica Bukvic [this message]
2003-02-27 13:08 ` Takashi Iwai
2003-02-27 20:31 ` Fernando Pablo Lopez-Lezcano
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='000b01c2de60$f31dd340$aa1f830a@ICO' \
--to=ico@fuse.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=perex@suse.cz \
/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