From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Andrew Benton <b3nt@ukonline.co.uk>, Takashi Iwai <tiwai@suse.de>,
alsa-devel <alsa-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] ALSA problems with 2.6.18-rc3
Date: Wed, 09 Aug 2006 17:51:09 +0100 [thread overview]
Message-ID: <1155142269.18821.45.camel@localhost.localdomain> (raw)
In-Reply-To: <1155141333.26338.186.camel@mindpipe>
On Wed, 2006-08-09 at 12:35 -0400, Lee Revell wrote:
> On Wed, 2006-08-09 at 17:30 +0100, Andrew Benton wrote:
> > Lee Revell wrote:
> > > Please try to identify the change that introduced the regression. What
> > > was the last kernel/ALSA version that worked correctly?
> >
> > The change happened between 2.6.17 and 2.6.18-rc1. Specifically,
> > 2.6.17-git4 works and 2.6.17-git5 doesn't.
>
> Takashi-san,
>
> Does this help at all? Many users are reporting that sound broke with
> 2.6.18-rc*.
Fwiw, 2.6.18-rc1 works on arm (pxa2xx). Maybe this is related to another
subsystem not found on arm.
Liam
next prev parent reply other threads:[~2006-08-09 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D8F3E5.5020508@ukonline.co.uk>
[not found] ` <1155073853.26338.112.camel@mindpipe>
[not found] ` <44DA0D93.2080307@ukonline.co.uk>
2006-08-09 16:35 ` ALSA problems with 2.6.18-rc3 Lee Revell
2006-08-09 16:51 ` Liam Girdwood [this message]
2006-08-09 18:17 ` Gene Heskett
2006-08-09 20:41 ` Lee Revell
2006-08-09 20:51 ` Gene Heskett
2006-08-09 20:57 ` Lee Revell
2006-08-09 21:22 ` Alistair John Strachan
2006-08-09 21:34 ` Lee Revell
2006-08-09 22:07 ` Alistair John Strachan
2006-08-09 22:11 ` Lee Revell
2006-08-09 22:28 ` Alistair John Strachan
2006-08-09 22:49 ` Lee Revell
2006-08-10 8:47 ` Takashi Iwai
2006-08-10 1:47 ` Gene Heskett
2006-08-10 13:13 ` 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=1155142269.18821.45.camel@localhost.localdomain \
--to=liam.girdwood@wolfsonmicro.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=b3nt@ukonline.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox