All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	John Frankish <john.frankish@outlook.com>
Subject: Re: Intel alsa sound request for Laptops
Date: Tue, 31 Jan 2017 11:48:00 +0100	[thread overview]
Message-ID: <s5hbmunld3z.wl-tiwai@suse.de> (raw)
In-Reply-To: <56c8aca6-f21b-954a-3257-7c8bf62648ab@metafoo.de>

On Tue, 31 Jan 2017 11:37:22 +0100,
Lars-Peter Clausen wrote:
> 
> On 01/31/2017 10:13 AM, Takashi Iwai wrote:
> [...]
> >>>> $ alsamixer
> >>>> cannot open mixer: No such file or directory
> [...]
> >> However, if the default sound device has been disabled by not loading i915, then alsa should be smart enough to use the next available sound device without the need to resort to obscure commands (snd_hda_intel.index=1,0) or additional software (pulseaudio).
> > 
> > Sorry, ALSA layer isn't designed to be smart.  It's rather dumb, gives
> > simply what the kernel provides.  You can implement many things on top
> > of it in a form of plugins, but the basic policy is not to modify the
> > given stuff, and pass it as is.
> 
> Given that alsamixer is capable of handling multiple cards and able to
> switch between them at runtime we should still look into this. The
> application should not refuse to launch if the default card is not available.

Well, currently the "default" just points to the default card, that is
card#0.  It's the current definition.

We may change it, but it means the inconsistent behavior against the
older version, thus we must do it VERY carefully.  (e.g. an
application opening the device twice may get a different result
depending on the status when it's applied to a hotplug device.)


Takashi

  reply	other threads:[~2017-01-31 10:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 12:46 Intel alsa sound request for Laptops John Frankish
2017-01-28 15:56 ` Takashi Iwai
2017-01-28 16:54   ` John Frankish
2017-01-28 20:20     ` Takashi Iwai
2017-01-29  5:27       ` John Frankish
2017-01-29  7:49         ` Takashi Iwai
2017-01-29  8:15           ` John Frankish
2017-01-29  8:35             ` Takashi Iwai
2017-01-29  9:59               ` John Frankish
2017-01-29 12:25                 ` Takashi Iwai
2017-01-29 13:06                   ` John Frankish
2017-01-29 13:47                     ` Takashi Iwai
2017-01-29 14:23                       ` John Frankish
2017-01-29 22:24                         ` John Rigg
2017-01-30 20:21                         ` Takashi Iwai
2017-01-31  6:40                           ` John Frankish
2017-01-31  7:19                             ` Takashi Iwai
2017-01-31  7:47                               ` John Frankish
2017-01-31  8:16                                 ` Takashi Iwai
2017-01-31  8:37                                   ` John Frankish
2017-01-31  9:13                                     ` Takashi Iwai
2017-01-31 10:37                                       ` Lars-Peter Clausen
2017-01-31 10:48                                         ` Takashi Iwai [this message]
2017-01-29 13:23             ` Lars-Peter Clausen

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=s5hbmunld3z.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=john.frankish@outlook.com \
    --cc=lars@metafoo.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.