From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Jan 'RedBully' Seiffert <redbully@cc.fh-luh.de>,
linux-hotplug-devel@lists.sourceforge.net
Cc: alsa-devel@lists.sourceforge.net, Greg KH <gregkh@gentoo.org>
Subject: Re: [Alsa-devel] [UDEV] Persitent ordering of ALSA-devices
Date: Mon, 04 Dec 2006 11:21:39 +0000 [thread overview]
Message-ID: <1165231299.10319.278726991@webmail.messagingengine.com> (raw)
In-Reply-To: <4571C735.6050403@cc.fh-luh.de>
Jan 'RedBully' Seiffert wrote:
> After Gentoo switched to udev-coldplug, my two soundcards get randomly
> reordered on reboot. Now I need to write a udev rule to give them a
> persistent ordering, but failed to do so until now, partly because i
> don't know on what key ALSA orders devices so they become card0 and 1,
> hw0 and hw1, partly because this feature of udev is so new.
ALSA's card ordering mechanism predates udev and isn't compatible with
it.
The ALSA framework has its own internal card list (that is shown in
/proc/asound/cards). Drivers can be instructed to take a specific card
number with the 'index' option, and this is the only official way of
reordering cards.
It is, in theory, possible to rename the device files, but you have to
be aware that
1) all devices files of one card must be renamed consistently, i.e,
the card number in the controlC*/hwdepC*D*/rawmidiC*D*/pcmC*D*p/
pcmC*D*c files (the number after the "C") must be the same for all
device files belonging to each card; and
2) enumerating cards will no longer work correctly (the card number
returned by ALSA will still be the number specified with the index
parameter), i.e., card names/descriptions will be wrong when a
program tries to show them.
Regards,
Clemens
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-12-04 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7nhSg-2Ow-9@gated-at.bofh.it>
[not found] ` <7nk3R-84O-35@gated-at.bofh.it>
[not found] ` <7nnbg-77Q-11@gated-at.bofh.it>
[not found] ` <7no7s-PV-23@gated-at.bofh.it>
[not found] ` <4570C14B.6090107@cc.fh-luh.de>
[not found] ` <20061202080348.GB9422@kroah.com>
2006-12-02 18:34 ` [UDEV] Persitent ordering of ALSA-devices (was: [gentoo-dev] Jan 'RedBully' Seiffert
2006-12-02 18:48 ` Marco d'Itri
2006-12-02 18:54 ` Darren Salt
2006-12-04 11:21 ` Clemens Ladisch [this message]
2006-12-04 16:47 ` [Alsa-devel] [UDEV] Persitent ordering of ALSA-devices Jan 'RedBully' Seiffert
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=1165231299.10319.278726991@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=gregkh@gentoo.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=redbully@cc.fh-luh.de \
/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).