From: James Courtier-Dutton <James@superbug.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
Takashi Iwai <tiwai@suse.de>,
Arnaud Patard <arnaud.patard@rtp-net.org>,
Mikael Magnusson <mikaelmagnusson@glocalnet.net>,
Peter Zubaj <pzad@pobox.sk>
Subject: Re: Fix emu10k1 breakages in kernel 2.6.12
Date: Sat, 02 Jul 2005 11:34:05 +0100 [thread overview]
Message-ID: <42C66D9D.9020203@superbug.co.uk> (raw)
In-Reply-To: <1120273701.12256.30.camel@mindpipe>
Lee Revell wrote:
> This set of critical fixes did not make it into the 2.6.12 kernel.
>
> To better handle the large variety of devices it supports, the emu10k1
> driver was recently cleaned up by moving all hardware details into a
> table keyed by PCI ID; unfortunately some IDs were missing from the
> table.
>
> The typical effect is loss of mixer settings, mic not working, or no
> sound at all when upgrading to 2.6.12.
>
Hold on. It is supposed to be done in a backwards compatible way
already. Before all card varients we handled as being the same card,
except for a few special cases. The first version of the patch took the
general case and named it "Audigy Unknown" and gave it the correct
parameters as were used before in the general case of all card varients
being the same. Then, I looked through the code, and extracted all the
special cases, and created specific recognition of those cards and set
the correct feature variables, so they were also handled.
The result of this should have been that there were no performance
change between either versions. Then, as more card types were
identified, I added special cases for them, but in their case, they used
all the default parameters for the general case, the only difference was
that the correct Model name was recorded and displayed in
/proc/asound/cards. This is mainly just to help users identify their
particular card, without having to remove the case of their PC. So this
helps them report bugs better.
If there are loss of features during the upgrade, I would be very
suprised. I suspect that the same problems one sees now with some cards,
has been there all along. If that is not the case, please report them in
the bug tracker in the normal way.
James
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-02 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 3:08 Fix emu10k1 breakages in kernel 2.6.12 Lee Revell
2005-07-02 4:56 ` [stable] " Greg KH
2005-07-02 5:45 ` Lee Revell
2005-07-02 5:52 ` Greg KH
2005-07-02 21:15 ` Lee Revell
2005-07-02 10:34 ` James Courtier-Dutton [this message]
2005-07-02 18:14 ` Lee Revell
2005-07-02 22:30 ` James Courtier-Dutton
2005-07-02 23:20 ` Lee Revell
2005-07-02 23:41 ` Lee Revell
2005-07-02 22:46 ` James Courtier-Dutton
2005-07-02 23:12 ` Lee Revell
2005-07-05 15:33 ` Lee Revell
2005-07-05 15:40 ` Takashi Iwai
2005-07-05 15:41 ` Lee Revell
2005-07-05 15:45 ` Takashi Iwai
2005-07-05 16:16 ` James Courtier-Dutton
2005-07-05 16:22 ` Lee Revell
2005-07-05 16:31 ` 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=42C66D9D.9020203@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=arnaud.patard@rtp-net.org \
--cc=mikaelmagnusson@glocalnet.net \
--cc=pzad@pobox.sk \
--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 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.