From: Bill Davidsen <davidsen@tmr.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Ivan N. Zlatev" <contact@i-nz.net>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Thomas Meyer <thomas@m3y3r.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2/4] 2.6.23-rc4: known regressions
Date: Wed, 29 Aug 2007 18:34:04 -0400 [thread overview]
Message-ID: <46D5F45C.7020800@tmr.com> (raw)
In-Reply-To: <s5hodgqibf8.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Wed, 29 Aug 2007 18:42:56 +0300,
> Ivan N. Zlatev wrote:
>> On 8/29/07, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>>> ALSA
>>>
>>> Subject : Master volume control broken
>>> References : http://lkml.org/lkml/2007/8/18/46
>>> Last known good : ?
>>> Submitter : Thomas Meyer <thomas@m3y3r.de>
>>> Caused-By : Ivan N. Zlatev <contact@i-nz.net>
>>> commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1
>>> Handled-By : Ivan N. Zlatev <contact@i-nz.net>
>>> Status : problem is being debugged
>>>
>>>
>> Hello,
>>
>> I am not the one to handle the issue. I have just supplied the
>> pinconfigs for the intel mac cards and assisted with logs/debug
>> information, so I happen to be more of an end user. I am not familiar
>> with the code base of the Intel HDA Codec. Takashi Iwai is the one
>> with the knowledge to fix the problem.
>
> ... but without the hardware :-<
>
> IMO, this is actually no real regression. In the earlier verison, you
> didn't have controls for multiple outputs, thus the mixer control was
> named as Master. Now you do have multiple individual controls, and
> thus there is no master any more, instead. That's the trade-off.
>
Would you buy or use a stand-alone mixer where the only way to control
total output would be to change the setting for one output, then
rebalance all the others against it, and then iterate until the result
is correct?
Is this an intermediate step to the full functionality of a $29 Radio
Shack mixer, or a limitation of just one audio driver, or maybe the user
interface for ALSA is broken right now?
Is it planned to leave Linux audio in this state?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-08-29 22:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46D58CC6.4020605@googlemail.com>
2007-08-29 15:27 ` [2/4] 2.6.23-rc4: known regressions Michal Piotrowski
2007-08-29 15:42 ` Ivan N. Zlatev
2007-08-29 15:54 ` Takashi Iwai
2007-08-29 22:34 ` Bill Davidsen [this message]
2007-09-02 12:19 ` Jesper Juhl
2007-09-04 8:30 ` Takashi Iwai
2007-09-03 20:23 ` Thomas Meyer
2007-09-04 8:36 ` Takashi Iwai
2007-08-30 8:21 ` Danny ter Haar
2007-08-31 22:01 ` Len Brown
2007-10-12 11:10 ` Danny ter Haar
2007-08-29 15:27 ` [3/4] " Michal Piotrowski
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 21:54 ` [NFS] " J. Bruce Fields
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 15:27 ` [4/4] " Michal Piotrowski
2007-08-29 15:27 ` Michal Piotrowski
2007-08-30 10:42 ` Soeren Sonnenburg
2007-08-30 10:42 ` Soeren Sonnenburg
2007-09-02 22:33 ` Michal Piotrowski
2007-09-02 22:33 ` Michal Piotrowski
2007-09-03 6:12 ` Arkadiusz Miskiewicz
2007-09-03 6:12 ` Arkadiusz Miskiewicz
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=46D5F45C.7020800@tmr.com \
--to=davidsen@tmr.com \
--cc=contact@i-nz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=thomas@m3y3r.de \
--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.