public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Mac mini sound woes
Date: Tue, 29 Mar 2005 21:31:09 +0200	[thread overview]
Message-ID: <s5hu0mugsg2.wl@alsa2.suse.de> (raw)
In-Reply-To: <1112123109.4922.3.camel@mindpipe>

At Tue, 29 Mar 2005 14:05:08 -0500,
Lee Revell wrote:
> 
> On Tue, 2005-03-29 at 21:04 +1000, Benjamin Herrenschmidt wrote:
> > Can the driver advertize in some way what it can do ? depending on the
> > machine we are running on, it will or will not be able to do HW volume
> > control... You probably don't want to use softvol in the former case...
> > 
> > dmix by default would be nice though :)
> 
> No, there's still no way to ask the driver whether hardware mixing is
> supported yet.  It's come up on alsa-devel before.  Patches are welcome.

Well I don't remember the discussion thread on alsa-devel about this,
but it's a good idea that alsa-lib checks the capability of hw-mixing
and apples dmix only if necessary.  (In the case of softvol, it can
check the existence of hw control by itself, though.)

Currently, dmix is enabled per driver-type base.  That is, dmix is set
to default in each driver's configuration which is known to have no hw
mixing functionality.

> dmix by default would not be nice as users who have sound cards that can
> do hardware mixing would be annoyed.  However, in the upcoming 1.0.9
> release softvol will be used by default for all the mobo chipsets.

On 1.0.9, dmix will be default, too, for most of mobo drivers.


Takashi

  reply	other threads:[~2005-03-29 19:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 23:42 Mac mini sound woes Benjamin Herrenschmidt
2005-03-28  1:42 ` Andrea Arcangeli
2005-03-28  2:34   ` Benjamin Herrenschmidt
2005-03-29  3:36 ` Lee Revell
2005-03-29  3:41   ` Benjamin Herrenschmidt
2005-03-29  7:47   ` Marcin Dalecki
2005-03-29  8:18     ` Benjamin Herrenschmidt
2005-03-29  9:22       ` Marcin Dalecki
2005-03-29 10:22         ` Takashi Iwai
2005-03-30  1:45           ` Marcin Dalecki
2005-03-30  2:08             ` Lee Revell
2005-03-30  4:14             ` Lee Revell
2005-03-30  5:15             ` Steven Rostedt
2005-03-29 22:13         ` Lee Revell
2005-03-29 23:25           ` Chris Friesen
2005-03-29 23:39             ` Benjamin Herrenschmidt
2005-03-30  1:48               ` Marcin Dalecki
2005-03-30  5:42                 ` Lee Revell
2005-03-30  1:45           ` Marcin Dalecki
2005-03-29 10:02   ` Takashi Iwai
2005-03-29 11:04     ` Benjamin Herrenschmidt
2005-03-29 12:12       ` Takashi Iwai
2005-03-29 19:05       ` Lee Revell
2005-03-29 19:31         ` Takashi Iwai [this message]
2005-03-29 20:11           ` Lee Revell
2005-03-29 22:03           ` Benjamin Herrenschmidt

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=s5hu0mugsg2.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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