From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>, Andrew Morton <akpm@osdl.org>,
alsa-devel@alsa-project.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18: hda_intel: azx_get_response timeout, switching to single_cmd mode...
Date: Mon, 25 Sep 2006 18:15:21 -0700 [thread overview]
Message-ID: <45187F29.2050905@goop.org> (raw)
In-Reply-To: <20060925202644.GB6278@ucw.cz>
Pavel Machek wrote:
> sometimes see this message, too, and sound more or less works for me.
> (Using alsa interface, mplayer works ok. mpg123 does not work).
>
That's how it used to be for me, but not any more.
J
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.18: hda_intel: azx_get_response timeout, switching to single_cmd mode...
Date: Mon, 25 Sep 2006 18:15:21 -0700 [thread overview]
Message-ID: <45187F29.2050905@goop.org> (raw)
In-Reply-To: <20060925202644.GB6278@ucw.cz>
Pavel Machek wrote:
> sometimes see this message, too, and sound more or less works for me.
> (Using alsa interface, mplayer works ok. mpg123 does not work).
>
That's how it used to be for me, but not any more.
J
next prev parent reply other threads:[~2006-09-26 1:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 19:58 2.6.18: hda_intel: azx_get_response timeout, switching to single_cmd mode Jeremy Fitzhardinge
2006-09-25 20:26 ` Pavel Machek
2006-09-26 1:12 ` Michael Clark
2006-09-26 1:12 ` Michael Clark
2006-09-26 1:15 ` Jeremy Fitzhardinge [this message]
2006-09-26 1:15 ` Jeremy Fitzhardinge
2006-09-26 10:16 ` Takashi Iwai
2006-09-26 10:16 ` Takashi Iwai
2006-09-26 15:37 ` Randy Dunlap
2006-09-26 15:37 ` Randy Dunlap
2006-09-26 15:48 ` Takashi Iwai
2006-09-26 15:48 ` Takashi Iwai
2006-09-26 15:56 ` Randy Dunlap
2006-09-26 15:56 ` Randy Dunlap
2006-09-26 16:09 ` Takashi Iwai
2006-09-26 16:09 ` Takashi Iwai
2006-09-26 16:31 ` Andrew Morton
2006-09-26 16:42 ` Takashi Iwai
2006-09-26 16:42 ` Takashi Iwai
2006-09-26 16:31 ` Andrew Morton
2006-10-01 6:03 ` Jeremy Fitzhardinge
2006-10-01 6:03 ` Jeremy Fitzhardinge
2006-10-04 9:21 ` Takashi Iwai
2006-10-04 9:21 ` Takashi Iwai
2006-10-04 15:16 ` Jeremy Fitzhardinge
2006-10-04 15:16 ` Jeremy Fitzhardinge
2006-10-04 15:38 ` Takashi Iwai
2006-10-04 15:38 ` Takashi Iwai
2006-10-04 19:04 ` Takashi Iwai
2006-10-04 19:04 ` Takashi Iwai
2006-10-04 20:07 ` Jeremy Fitzhardinge
2006-10-04 20:07 ` Jeremy Fitzhardinge
2006-10-05 9:58 ` Takashi Iwai
2006-10-05 9:58 ` Takashi Iwai
2006-10-28 5:07 ` 2.6.18: hda_intel:azx_get_response " Shai Peretz
2006-10-04 13:57 ` 2.6.18: hda_intel: azx_get_response " Tomasz Torcz
2006-10-04 15:16 ` Jeremy Fitzhardinge
2006-10-04 15:16 ` Jeremy Fitzhardinge
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=45187F29.2050905@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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.