All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Dominique Larchey-Wendling <Dominique.Larchey-Wendling@loria.fr>
Cc: Alsa-devel@alsa-project.org
Subject: Re: Strange bug in .asoundrc ??
Date: Mon, 19 Nov 2007 16:43:48 +0100	[thread overview]
Message-ID: <1195487028.2251.1222141113@webmail.messagingengine.com> (raw)
In-Reply-To: <4741A665.1030600@loria.fr>

Dominique Larchey-Wendling wrote:
>  > It appears this behaviour is by design.
> 
> Ok so this is not a bug but a feature ;-)
> However, it is not specified in the doc that alsa-lib makes a semantic 
> distinction between the types of objects

If a somewhat complete documentation existed, it would certainly mention
this.

> in the alisp language.

The configuration language is not alisp.

> What is strange is that the same function is called in alsa-lib to
> expand hw:0 whether it is prefixed with "ctl" or "pcm" :
> 
> snd_config_search_definition(root, "ctl", name, &ctl_conf);
> 
> and
> 
> snd_config_search_definition(root, "pcm", name, &pcm_conf);

This function is called with a string like "tata" and returns the string
"hw:0" (it would return the compound node {type hw card 0} when it would
be called with "hw:0").

In the PCM code, it is the following recursive call of
snd_pcm_open_noupdate() that causes the extra lookup to happen.

> but my question was more why is it designed this way ?

Well, "designed" may be too strong a word; it implies that somebody
actually thought about it.  :-)

I'd guess that this functionality was never needed for any device type
except PCM because there aren't any plugins that could be used in place
of "hw".


Regards,
Clemens

      reply	other threads:[~2007-11-19 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 11:06 Strange bug in .asoundrc ?? Dominique Larchey-Wendling
2007-11-19 14:20 ` Clemens Ladisch
2007-11-19 15:06   ` Dominique Larchey-Wendling
2007-11-19 15:43     ` Clemens Ladisch [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=1195487028.2251.1222141113@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=Alsa-devel@alsa-project.org \
    --cc=Dominique.Larchey-Wendling@loria.fr \
    /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.