From: jcdutton <jcdutton@users.sourceforge.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [alsa-cvslog] CVS: alsa-kernel/pci/emu10k1 emu10k1_main.c,1.68,1.69
Date: Mon, 12 Sep 2005 22:42:20 +0100 [thread overview]
Message-ID: <4325F63C.2010104@users.sourceforge.net> (raw)
In-Reply-To: <s5h64t6ioko.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Sat, 10 Sep 2005 18:20:45 +0100,
> jcdutton wrote:
>
>>Takashi Iwai wrote:
>>
>>>At Sat, 10 Sep 2005 02:24:12 -0700,
>>>James Courtier-Dutton wrote:
>>>
>>>
>>>>Update of /cvsroot/alsa/alsa-kernel/pci/emu10k1
>>>>In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31621/alsa-driver/alsa-kernel/pci/emu10k1
>>>>
>>>>Modified Files:
>>>> emu10k1_main.c
>>>>Log Message:
>>>>Summary: snd-emu10k1: ALSA bug#1297: Fix a error recognising the SB Live Platinum.
>>>>
>>>>The card does not have an AC97 chip.
>>>>.subsystem = 0x80611102
>>>
>>>
>>>Hmm, it seems that there is another model with the same subsystem ID,
>>>which has really an ac97 chip.
>>>
>>>
>>>Takashi
>>>
>>>
>>
>>I only know about bug#1297.
>>Is there another person who has this exact same card ID but different
>>ac97 chip presence?
>
>
> Yes. At least, two on SUSE Bugzilla:
>
> https://bugzilla.novell.com/show_bug.cgi?id=113149
>
>
> Takashi
>
>
Hum, well this is starting to become a real problem.
Can you ask the SUSE user to extract their sound card from their PC and
read off the model name. It will be something like "SB0350".
I will do the same with the alsa bug user.
There must be some reliable way to identify the sound card. Just
detecting the presence or absence of the AC97 chip is not enough for
what I have planned for the more pro user which is to implement full
control over the ADC chip via the I2C bus on the Platinum models.
If both the Platinum and the Player have the same model number on the
card, then I will have to look for something else to determine the
difference.
James
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-09-12 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EE1am-0008Ff-8x@sc8-pr-cvs1.sourceforge.net>
2005-09-10 14:34 ` [alsa-cvslog] CVS: alsa-kernel/pci/emu10k1 emu10k1_main.c,1.68,1.69 Takashi Iwai
2005-09-10 17:20 ` jcdutton
2005-09-12 10:10 ` Takashi Iwai
2005-09-12 21:42 ` jcdutton [this message]
2005-09-13 10:39 ` 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=4325F63C.2010104@users.sourceforge.net \
--to=jcdutton@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--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.