From: Takashi Iwai <tiwai@suse.de>
To: Mark Knecht <markknecht@attbi.com>
Cc: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Paul Davis <paul@linuxaudiosystems.com>,
Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: alsasound init script (Re: possible problems with rc6 aplay )
Date: Fri, 20 Dec 2002 16:10:50 +0100 [thread overview]
Message-ID: <s5hadj0vi85.wl@alsa2.suse.de> (raw)
In-Reply-To: <1040217097.1370.7.camel@Godzilla>
At 18 Dec 2002 05:11:36 -0800,
Mark Knecht wrote:
>
> On Wed, 2002-12-18 at 03:17, Takashi Iwai wrote:
> > At Wed, 18 Dec 2002 11:46:45 +0100,
> > I wrote:
> > >
> > > > It would be better to make the alsasound script more robust (and
> > > > independent of the startup order) and able to deal with partially loaded
> > > > modules, so instead of just checking for the /proc/asound directory it
> > > > would actually see what modules are already loaded and only load those
> > > > that are not. It does not look too easy, it seems that /proc/asound does
> > > > not provide a list of loaded modules (rather a list of cards that are
> > > > not associated with module names).
> > >
> > > agreed. a scenario i can imagine now is that the script just takes a
> > > look at /proc/asound/cards and checks the numbers at the first column.
> > > this should correspond to the card indices which have been already
> > > loaded. then the script will try to load the modules snd-card-X but
> > > skip the numbers listed in the above...
> > > i'll try to rewrite as this way.
> >
> > after reconsideration: it would be much simpler to create a new proc
> > file which shows the modules already loaded.
> >
> I was wondering what would happen in this process if someone had two r
> three identical USB devices, like the MidiMan 2X2? OR also two identical
> cards like the RME HDSP 9652?
when a module is loaded and two or more identical (or supported)
devices are connected, the module will initialize the all such devices
at once.
for multiple devices, you can specify the options separated by commas,
options snd-hdsp index=1,2,3 id="hdsp1","hdsp2","hdsp3"
if there is no index option given for a device, as mentioned before,
an empty slot is probed from the index 0. thus, if you don't set any
index options for all modules, that's fine, except for that the order
of devices is not guaranteed. (cards_limit option must be enough
large, or you need to apply my patch.)
for keeping the order of devices, giving the index option for each
device would be better.
> It is important that the system recognize the same hardware as the same
> sound device every time the machine booted, and whether the machine is
> warm or cold booted.
in the case of usb, it's not 100% sure, because it's anyway
hotpluggable. but usually the order of probing is identical, so it's
ok.
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by: The Best Geek Holiday Gifts!
Time is running out! Thinkgeek.com has the coolest gifts for
your favorite geek. Let your fingers do the typing. Visit Now.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
next prev parent reply other threads:[~2002-12-20 15:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021216152035.CZFC3512.sccrgwc01.attbi.com@newmx1.fast.net>
2002-12-16 21:18 ` alsasound init script (Re: possible problems with rc6 aplay ) Mark Knecht
2002-12-17 2:51 ` Paul Davis
2002-12-17 3:46 ` Mark Knecht
2002-12-17 11:06 ` Takashi Iwai
2002-12-17 19:36 ` Fernando Pablo Lopez-Lezcano
2002-12-18 10:46 ` Takashi Iwai
2002-12-18 11:17 ` Takashi Iwai
2002-12-18 13:11 ` Mark Knecht
2002-12-20 15:10 ` Takashi Iwai [this message]
2002-12-20 16:10 ` Clemens Ladisch
[not found] <E18PTTN-0004YV-00@sc8-sf-list2.sourceforge.net>
2002-12-20 22:53 ` Pedro Lopez-Cabanillas
2002-12-23 13:44 ` Takashi Iwai
2002-12-23 17:18 ` Patrick Shirkey
2002-12-16 13:57 possible problems with rc6 aplay Takashi Iwai
2002-12-16 14:29 ` Paul Davis
2002-12-16 14:53 ` alsasound init script (Re: possible problems with rc6 aplay ) Takashi Iwai
2002-12-16 15:23 ` Paul Davis
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=s5hadj0vi85.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=markknecht@attbi.com \
--cc=nando@ccrma.Stanford.EDU \
--cc=paul@linuxaudiosystems.com \
/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.