All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: my udev rules are breaking my dmixer setup why?
Date: Tue, 11 Nov 2008 18:30:48 +0100	[thread overview]
Message-ID: <4919C148.3060706@powercraft.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0811111151260.13649@tm8103.perex-int.cz>

Jaroslav Kysela wrote:
> On Tue, 11 Nov 2008, Takashi Iwai wrote:
> 
>>> Almost all devices can be managed with udev rules, that is where the
>>> system is designed for, there are also alsa rules in there, if they
>>> don't work what is wrong then? is it an alsa issue, or udev, what are
>>> the dependencies when alsa uses hardware. How are the /dev/snd/* devices
>>> used and what is the /proc/asound/* for ?
>> The card index mechanism in ALSA was introduced much before udev
>> was born.  It's just a legacy mechanism, but it's hard to kill without
>> breaking the running system, unfortunately.
> 
> Note that you can identify your card via the text identification (check 
> /proc/asound/cards to get it in []). You can set this identification in 
> the module insert time and use for example 'hw:Intel' in your apps without 
> bothering with indexes.
> 
> The missing part is the modification of this text identification using
> sysfs at runtime for udev. Some time ago, I was trying to add this setup 
> to /sys/class/sound, but the sysfs core code was not prepared for this 
> change. I'll try to check the situation again.
> 

As response to:
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-November/012366.html

I am not sure if it is good practice to repose to an RFC if so please
tell me then we will continue the discussion in the RFC thread.

Thank you Jaroslav for creating the patch this is really appreciated, if
all things work I will send you some dutch stroopwafels :-D

I am just curious how you patch can be used with udev? What did you have
in mind?

Would something like this be possible:

SUBSYSTEM=="sound", ACTION="add" KERNELS=="3-1",
NAME="snd/by-id/audiodevice0"
SUBSYSTEM=="sound", ACTION="add" KERNELS=="3-2",
NAME="snd/by-id/audiodevice1"

pcm.!default {
   type plug
   slave.pcm dmixer
}
pcm.dmixer {
   type dmix
   ipc_key 1024
   slave.pcm hw:audiodevice0
}
ctl.dmixer {
   type hw
   card audiodevice0
}
pcm.dsp {
    type plug
    slave.pcm dmixer
}
ctl.mixer {
    type hw
    card audiodevice0
}

Thanks in advance,

Jelle

  parent reply	other threads:[~2008-11-11 17:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 14:59 my udev rules are breaking my dmixer setup why? Jelle de Jong
2008-11-11  8:03 ` Takashi Iwai
2008-11-11  9:43   ` Jelle de Jong
2008-11-11 10:37     ` Takashi Iwai
2008-11-11 10:57       ` Jelle de Jong
2008-11-11 11:04         ` Takashi Iwai
2008-11-11 11:01       ` Jaroslav Kysela
2008-11-11 11:21         ` Jelle de Jong
2008-11-11 11:25           ` Takashi Iwai
2008-11-11 17:30         ` Jelle de Jong [this message]
2008-11-11 17:55           ` Jaroslav Kysela
2008-11-12 10:25             ` Jelle de Jong
2008-12-03 17:56               ` Jelle de Jong
2009-07-29 10:44             ` Jelle de Jong

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=4919C148.3060706@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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 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.