All of lore.kernel.org
 help / color / mirror / Atom feed
From: Travis Place <wishie@wishie.net>
To: alsa-devel@alsa-project.org
Subject: [Fwd: Re:  Problem regarding CA0106]
Date: Tue, 17 Jun 2008 01:56:11 +1000	[thread overview]
Message-ID: <1213631771.4031.6.camel@temp-fallen> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Forwarded message - Re: [alsa-devel] Problem regarding CA0106 --]
[-- Type: message/rfc822, Size: 2155 bytes --]

From: Travis Place <wishie@wishie.net>
To: Takashi Iwai <tiwai@suse.de>
Subject: Re: [alsa-devel] Problem regarding CA0106
Date: Tue, 17 Jun 2008 01:52:29 +1000
Message-ID: <1213631528.4031.4.camel@temp-fallen>

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.

> 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).

> 
> thanks,
> 
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Thanks,
Travis Place

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

                 reply	other threads:[~2008-06-16 15:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1213631771.4031.6.camel@temp-fallen \
    --to=wishie@wishie.net \
    --cc=alsa-devel@alsa-project.org \
    /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.