From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] emu10k1: fix P16V breakage for non Audigy2 cards
Date: Fri, 18 Mar 2005 14:54:34 -0500 [thread overview]
Message-ID: <1111175674.11341.5.camel@mindpipe> (raw)
In-Reply-To: <423B319A.8080306@superbug.co.uk>
On Fri, 2005-03-18 at 19:52 +0000, James Courtier-Dutton wrote:
> Lee Revell wrote:
> > On Wed, 2005-03-16 at 21:28 +0000, James Courtier-Dutton wrote:
> >
> >>Thank you for fixing the bug.
> >>The "unhandled interrupt" should be commented out. It is used for
> >>reverse engineering certain features.
> >>
> >
> >
> > OK, updated patch attached.
> >
> > Please apply to CVS ASAP, this is a bad bug!
> >
> > Lee
> >
> >
>
> I think that this "bad bug" will also effect Audigy 1 cards.
> Does that new if statement in the irq handler correctly exclude Audigy 1
> cards ?
>
Yes it uses the same logic you used to detect the P16V, if (emu->audigy
&& emu->revision==4) IIRC.
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
next prev parent reply other threads:[~2005-03-18 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 5:21 [PATCH] emu10k1: fix P16V breakage for non Audigy2 cards Lee Revell
2005-03-16 5:27 ` Lee Revell
2005-03-16 21:28 ` James Courtier-Dutton
2005-03-17 15:53 ` Lee Revell
2005-03-17 15:58 ` Takashi Iwai
2005-03-17 16:00 ` Lee Revell
2005-03-17 16:20 ` Lee Revell
2005-03-17 16:41 ` Takashi Iwai
2005-03-17 16:48 ` Lee Revell
2005-03-18 19:52 ` James Courtier-Dutton
2005-03-18 19:54 ` Lee Revell [this message]
2005-03-18 19:56 ` Lee Revell
2005-03-17 14:11 ` [PATCH] emu10k1: fix misc oopses Thierry Vignaud
2005-03-17 15:02 ` Lee Revell
2005-03-17 16:01 ` 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=1111175674.11341.5.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.