From: Travis Place <wishie@wishie.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problem regarding CA0106
Date: Tue, 17 Jun 2008 03:26:06 +1000 [thread overview]
Message-ID: <1213637166.4031.10.camel@temp-fallen> (raw)
In-Reply-To: <s5hd4mhpdy0.wl%tiwai@suse.de>
On Mon, 2008-06-16 at 18:00 +0200, Takashi Iwai wrote:
> At Tue, 17 Jun 2008 01:52:08 +1000,
> Travis Place wrote:
> >
> > On Mon, 2008-06-16 at 12:38 +0200, Takashi Iwai wrote:
> > > At Sat, 14 Jun 2008 03:18:33 +1000,
> > > Travis Place wrote:
> > > >
> > > > Just been speaking with a guy in #alsa about the problems with his "MSI
> > > > K8N Diamond MB" which has an onboard "SB Live 24bit" or "Audigy".
> > > >
> > > > While looking through ca0106_main.c in GIT, i saw the following section:
> > > >
> > > > /* MSI K8N Diamond Motherboard with onboard SB Live 24bit without AC97
> > > > */
> > > > /* SB0438
> > > > * CTRL:CA0106-DAT
> > > > * ADC: WM8775SEDS
> > > > * DAC: CS4382-KQZ
> > > > */
> > > > { .serial = 0x10091462,
> > > > .name = "MSI K8N Diamond MB [SB0438]",
> > > > .gpio_type = 2,
> > > > .i2c_adc = 1 } ,
> > > >
> > > > For this guys sound to work, we had to change the serial line to:
> > > >
> > > > { .serial = 0x10091102,
> > >
> > > Does it mean that this number 1009:1102 is missing, or a wrong
> > > 1009:1462 entry matches with his hardware?
> > >
> > Well, it appears to me (due to another report filed previously) that
> > the motherboard is a 'newer revision' and has a different ID for the
> > soundcard.
>
> Hm, so you didn't receive alsa-info.sh or "lspci -nv" output?
>
Of course I got alsa-info.sh output :)
(asks himself why he didnt include it though)
http://pastebin.ca/1048644
> > > In the former case, it happens often. We just need to add a new entry
> > > for the newer model. In the latter case, it's odd.
> > >
> >
> > I think that adding the new ID to the driver wont cause any immediate
> > problems. The old value (1009:1462) should remain, until we can confirm
> > it against another K8N Diamond motherboard (although im not sure how
> > common these boards are).
>
> Yeah, I guess so, too. But just to be sure...
>
Well, we'll just have to see what happens, I guess.
For the record, in both older ALSA versions, and 1.0.16, changing only
the serial seems to be sufficient. So adding another serial should be an
easy fix.
Thanks,
Travis
>
> Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2008-06-16 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 17:18 Problem regarding CA0106 Travis Place
2008-06-16 10:38 ` Takashi Iwai
[not found] ` <1213631528.4031.4.camel@temp-fallen>
[not found] ` <s5hd4mhpdy0.wl%tiwai@suse.de>
2008-06-16 17:26 ` Travis Place [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=1213637166.4031.10.camel@temp-fallen \
--to=wishie@wishie.net \
--cc=alsa-devel@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox