From: Lee Revell <rlrevell@joe-job.com>
To: Shayne O'Connor <forums@machinehasnoagenda.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: emu10k1 driver broken in CVS
Date: Wed, 16 Mar 2005 00:09:05 -0500 [thread overview]
Message-ID: <1110949745.19984.2.camel@mindpipe> (raw)
In-Reply-To: <1110949192.19837.3.camel@mindpipe>
On Tue, 2005-03-15 at 23:59 -0500, Lee Revell wrote:
> It's not this one. The problem must be the P16V patch. But that should
> have no effect on emu10k1...
OK, found the bug. The interrupt handler checks the IPR2 register even
on non-Audigy2 cards resulting in an infinite loop.
Patch forthcoming. We really need an -rc2 ASAP, this is a nasty bug.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-16 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 4:34 emu10k1 driver broken in CVS Lee Revell
2005-03-16 4:48 ` Shayne O'Connor
2005-03-16 4:46 ` Lee Revell
2005-03-16 4:59 ` Lee Revell
2005-03-16 5:09 ` Lee Revell [this message]
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=1110949745.19984.2.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=forums@machinehasnoagenda.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