From: Takashi Iwai <tiwai@suse.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, fengguang.wu@intel.com
Subject: Re: ugly sound output (intel-hda) [was: mmotm 2009-11-24-16-47 uploaded]
Date: Fri, 27 Nov 2009 12:18:18 +0100 [thread overview]
Message-ID: <s5hskc0cj2d.wl%tiwai@suse.de> (raw)
In-Reply-To: <4B0FB2E2.3040801@gmail.com>
At Fri, 27 Nov 2009 12:07:14 +0100,
Jiri Slaby wrote:
>
> On 11/27/2009 11:45 AM, Takashi Iwai wrote:
> > Could you give rather alsa-info.sh output (run with --no-upload option)?
>
> Yup, attached.
Thanks.
Just to be sure -- which h/w vendor/machine is it?
> >> It's a regression against, I think, 2009-11-13-19-59.
> >
> > There aren't so many fundamental changes since Nov. 13.
> > The major ones are for Intel HDMI, but it should be irrelevant in your
> > case.
> >
> > The changes in patch_sigmatel.c since then are:
> >
> > d56757abc11a21996d9839c0d4e3b2c3666cd318
> > ALSA: hda - Replace the rest of jack-detections with snd_hda_jack_detect()
>
> commit 99dee933c33b63da4339bccc092b69b053fe055a
> Author: Jiri Slaby <jslaby@novell.com>
> Date: Fri Nov 27 11:51:13 2009 +0100
>
> Revert "ALSA: hda - Replace the rest of jack-detections with
> snd_hda_jack_detect()"
>
> This reverts commit d56757abc11a21996d9839c0d4e3b2c3666cd318.
>
>
> Makes the difference :).
Oh, it's good that you found it quickly.
It means that STAC/IDT codecs give a wrong pin capability.
I'll revert the changes for patch_sigmatel.c now.
thanks,
Takashi
next prev parent reply other threads:[~2009-11-27 11:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 0:47 mmotm 2009-11-24-16-47 uploaded akpm
2009-11-25 15:12 ` BUG at scsi_lib.c:1108 [Was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-25 15:19 ` James Bottomley
2009-11-25 20:22 ` Jiri Slaby
2009-11-25 21:13 ` Neil Brown
2009-11-26 10:17 ` Boaz Harrosh
2009-11-27 4:17 ` Neil Brown
2009-11-27 10:20 ` Jiri Slaby
2009-11-26 1:46 ` mmotm 2009-11-24-16-47 uploaded (gpio_max7301) Randy Dunlap
2009-11-28 16:21 ` Wolfram Sang
2009-12-15 22:43 ` Andrew Morton
2009-12-15 22:46 ` Randy Dunlap
2009-12-15 23:10 ` Andrew Morton
2009-12-16 11:30 ` Wolfram Sang
2009-11-27 10:33 ` ugly sound output (intel-hda) [was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-27 10:45 ` Takashi Iwai
2009-11-27 11:07 ` Jiri Slaby
2009-11-27 11:18 ` Takashi Iwai [this message]
2009-11-27 12:22 ` Jiri Slaby
2009-11-27 12:26 ` Takashi Iwai
2009-11-27 15:03 ` WARNING: kernel/smp.c:292 smp_call_function_single [Was: " Jiri Slaby
2009-11-27 15:17 ` Peter Zijlstra
2009-11-27 16:37 ` Thomas Gleixner
2009-11-27 16:44 ` Thomas Gleixner
2009-11-28 12:12 ` Avi Kivity
2009-11-30 8:58 ` Tejun Heo
2009-11-30 9:41 ` Avi Kivity
2009-11-30 10:02 ` Thomas Gleixner
2009-11-30 10:45 ` Tejun Heo
2009-11-30 11:02 ` [PATCH tip/sched/urgent] sched: revert 498657a478c60be092208422fefa9c7b248729c2 Tejun Heo
2009-11-30 11:13 ` Avi Kivity
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=s5hskc0cj2d.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=perex@perex.cz \
/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
all inboxes | Powered by JetHome®