From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Sound card module loading sequence (was: Re: [PATCH] fix udevtrigger first/default/last ordering
Date: Wed, 19 Apr 2006 07:01:06 +0000 [thread overview]
Message-ID: <200604191301.07114.patrakov@ums.usu.ru> (raw)
In-Reply-To: <1145144929.444186616087e@cs1.alpha12.l-secure.net>
Greg KH wrote:
> Name the sound devices based on the pci id. Or the path. Or something
> else you think might be unique (vendor/product id?, etc.)
Please see also http://lkml.org/lkml/2006/1/5/214
The question here is whether it is an acceptable idea to have persistent
soundcard naming with this crazy "plughw:CARDID,0" or "index" hack instead of
symlinks created by udev. BTW I think this hack won't work reliably for two
identical cards (i.e., it would break if one upgrades BIOS).
I have not enough power to push this to ALSA maintainers, though.
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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
prev parent reply other threads:[~2006-04-19 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 23:48 Sound card module loading sequence (was: Re: [PATCH] fix udevtrigger first/default/last ordering) juuso.alasuutari
2006-04-18 19:12 ` Sound card module loading sequence (was: Re: [PATCH] fix udevtrigger first/default/last ordering Greg KH
2006-04-18 19:25 ` Darren Salt
2006-04-19 7:01 ` Alexander E. Patrakov [this message]
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=200604191301.07114.patrakov@ums.usu.ru \
--to=patrakov@gmail.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).