From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org, ian_minett@creativelabs.com
Subject: Re: [PATCH 0/2] Two fixes for ca0132
Date: Mon, 20 Aug 2012 11:24:10 +0200 [thread overview]
Message-ID: <s5hfw7hrk5h.wl%tiwai@suse.de> (raw)
In-Reply-To: <s5hharxrk7u.wl%tiwai@suse.de>
At Mon, 20 Aug 2012 11:22:45 +0200,
Takashi Iwai wrote:
>
> At Mon, 20 Aug 2012 11:16:58 +0200,
> David Henningsson wrote:
> >
> > I came across the following codec:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1038651/+attachment/3267820/+files/Card0.Codecs.codec.0.txt
> >
> > ...and the codec wouldn't load due to mixer errors. I don't know more about the codec than the codec proc shows,
> > and looking at that file it seems a bit broken, but maybe Ian would be able to make it work, with the help of
> > some secret verbs? At least now the codec would load correctly, so that the output side could be used.
>
> Both fixes already have existed in my local queue for weeks and
> provided to some people who reported CA0132 problems (including Ian).
> Basically they are for fixing the missing SPDIF controls. But they
> were pending because of the upcoming DSP loading stuff, which seem to
> be pretty delayed.
>
> So I'm going to apply the fixes for 3.6 kernel.
FWIW, the patches are in topic/ca0132-fix branch of sound git tree
(which should appear shortly later).
Takashi
next prev parent reply other threads:[~2012-08-20 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 9:16 [PATCH 0/2] Two fixes for ca0132 David Henningsson
2012-08-20 9:16 ` [PATCH 1/2] ALSA: hda - Fix "Line" and "Mic" names for CA0132 David Henningsson
2012-08-20 9:17 ` [PATCH 2/2] ALSA: hda - don't create dysfunctional mixer controls for ca0132 David Henningsson
2012-08-20 9:22 ` [PATCH 0/2] Two fixes " Takashi Iwai
2012-08-20 9:24 ` Takashi Iwai [this message]
2012-08-20 9:27 ` David Henningsson
2012-08-20 9:34 ` Takashi Iwai
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=s5hfw7hrk5h.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=ian_minett@creativelabs.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;
as well as URLs for NNTP newsgroup(s).