From: Mark Canter <marcus@vfxcomputing.com>
To: Andrew Morton <akpm@osdl.org>
Cc: rlrevell@joe-job.com, nish.aravamudan@gmail.com,
drzeus-list@drzeus.cx, linux-kernel@vger.kernel.org,
alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: intel 8x0 went silent in 2.6.11
Date: Thu, 3 Mar 2005 21:50:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.62.0503032146580.21844@krusty.vfxcomputing.com> (raw)
In-Reply-To: <20050303154929.1abd0a62.akpm@osdl.org>
Yes, flipping back to the 2.6.10 kernel resolves the sound issue through
the docking station so that everything runs without incident. Though I'd
like to see/assist in resolving the issue for future releases :).
On Thu, 3 Mar 2005, Andrew Morton wrote:
> Mark Canter <marcus@vfxcomputing.com> wrote:
>>
>>
>> To close this issue out of the LKML and alsa-devel, a bug report has been
>> written.
>>
>> It appears to be an issue with the 'headphone jack sense' (as kde labels
>> it). The issue is in the way the 8x0 addresses the docking station/port
>> replicator's audio output jack. The mentioned quick fix does not work for
>> using the ds/pr audio output, but does resolve it for a user that is only
>> using headphones/internal speakers.
>
> But there was a behavioural change: applications which worked in 2.6.10
> don't work in 2.6.11, is that correct?
>
> If so, the best course of action is to change the kernel so those
> applications work again. Can that be done?
>
next prev parent reply other threads:[~2005-03-04 2:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 12:51 Pierre Ossman
2005-03-03 17:45 ` Nish Aravamudan
2005-03-03 18:46 ` Mark Canter
2005-03-03 18:52 ` [Alsa-devel] " Lee Revell
2005-03-03 19:06 ` Mark Canter
2005-03-03 19:09 ` Lee Revell
[not found] ` <Pine.LNX.4.62.0503031410450.19015@krusty.vfxcomputing.com>
2005-03-03 19:22 ` Lee Revell
[not found] ` <29495f1d050303114379ab96b5@mail.gmail.com>
2005-03-03 19:47 ` Lee Revell
2005-03-03 20:33 ` Mark Canter
2005-03-03 23:49 ` Andrew Morton
2005-03-04 0:37 ` Pierre Ossman
2005-03-04 21:16 ` Pierre Ossman
2005-03-05 19:00 ` Lee Revell
2005-03-07 20:13 ` Pierre Ossman
2005-03-07 20:26 ` Takashi Iwai
2005-03-07 13:50 ` Takashi Iwai
2005-03-07 20:16 ` Pierre Ossman
2005-03-07 20:21 ` Takashi Iwai
2005-03-08 1:10 ` Pierre Ossman
2005-03-08 11:53 ` Takashi Iwai
2005-03-08 12:46 ` Pierre Ossman
2005-03-09 1:53 ` Mark Canter
2005-03-09 3:02 ` Lee Revell
2005-03-04 2:50 ` Mark Canter [this message]
2005-03-04 5:13 ` Jeff Garzik
2005-03-04 18:02 ` Lee Revell
2005-03-03 19:42 ` Nish Aravamudan
2005-03-04 20:40 ` Bill Davidsen
2005-03-04 20:44 ` Lee Revell
2005-03-04 20:44 ` Mark Canter
2005-03-04 0:36 ` Pierre Ossman
2005-03-04 20:36 ` Bill Davidsen
2005-03-04 21:06 ` Lee Revell
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=Pine.LNX.4.62.0503032146580.21844@krusty.vfxcomputing.com \
--to=marcus@vfxcomputing.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--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
Powered by JetHome