From: Dave Jones <davej@redhat.com>
To: Peter Zubaj <pzad@pobox.sk>
Cc: alsa-devel@alsa-project.org, James@superbug.co.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
perex@suse.cz
Subject: Re: Re: [ALSA] snd-emu10k1: ALSA bug#1297: Fix a error recognising the SB Live Platinum.
Date: Mon, 3 Oct 2005 20:54:01 -0400 [thread overview]
Message-ID: <20051004005401.GC10697@redhat.com> (raw)
In-Reply-To: <7a5967f2d895440aa1ca2fa1d201c380@pobox.sk>
On Mon, Oct 03, 2005 at 08:23:28AM +0200, Peter Zubaj wrote:
> AFAIK this was fixed in CVS. Two cards have same model id (one has AC97, one not).
>
> Fix:
>
> http://sourceforge.net/mailarchive/forum.php?thread_id=8360485&forum_id=33141
>
>From the look of that patch, this will just print
"emu10k1: AC97 is optional on this board Proceeding without ac97 mixers..."
and do nothing about actually making things work for people again,
or even to suggest what they can do to work around this situation
when their volume control breaks. At the least this sounds like it
needs to mention a module parameter to force ac97 support.
What actually happens if we set ac97_chip=1 on the boards that
don't have it ? Is it purely a cosmetic thing, showing some
sliders that do nothing?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
next parent reply other threads:[~2005-10-04 0:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7a5967f2d895440aa1ca2fa1d201c380@pobox.sk>
2005-10-04 0:54 ` Dave Jones [this message]
[not found] <dc7e3d7c111741a991e11a1a39ca9262@pobox.sk>
2005-10-04 10:50 ` Re: [ALSA] snd-emu10k1: ALSA bug#1297: Fix a error recognising the SB Live Platinum Takashi Iwai
2005-10-04 11:08 ` James Courtier-Dutton
2005-10-04 11:14 ` Takashi Iwai
2005-10-04 11:05 ` James Courtier-Dutton
2005-10-04 20:40 ` Dave Jones
2005-10-05 11:58 ` Takashi Iwai
2005-10-03 6:23 Peter Zubaj
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=20051004005401.GC10697@redhat.com \
--to=davej@redhat.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=pzad@pobox.sk \
/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