Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Sassenberg <sassi@sforce.org>
To: alsa-devel@lists.sourceforge.net
Subject: ALC Chips, now Realtek...
Date: Fri, 17 May 2002 16:41:23 +0200	[thread overview]
Message-ID: <20020517164123.7630a0bf.sassi@sforce.org> (raw)
In-Reply-To: <E178Qdh-0008Ow-00@usw-sf-list2.sourceforge.net>

Hi,


on my Epox 8K3A, there is a VT8233 together with an ALC201A Codec,
which does not work, as far I could figure out.
On Realtek HP I found as a Linux driver for that codec a modified
version of alsa-driver-0.5.11.

<-- snip from a97_codec.c -->

//====== added by hou 01/15/02
//      {       0x414c4710,     "ALC200/200P"			},
        {       0x414c4320,     "ALC100/100P"			},
        {       0x414c4710,     "ALC200"              		},
        {       0x414c4711,     "ALC201"       			},
        {       0x414c4712,     "ALC201A"                       },
  	{	0x414c4713,	"ALC201-G"			},
	{	0x414c4720,	"ALC650"			},
        {       0x414c4721,     "ALC650-D"   			},
 	{	0x414c4730,	"ALC101"			},
        {       0x414c4740,     "ALC202A-A"			},
        {       0x414c4741,     "ALC202-B"			},
        {       0x414c4742,     "ALC202A-C"			},
        {       0x414c4750,     "ALC250"          		},


and later on...

//====  added by hou 01/15/02   
	reg = snd_ac97_read(ac97, AC97_SIGMATEL_DAC2INVERT);
//      printk("id 0x%8x, ext 0x%x.\n", ac97->id, reg);
 	
        switch(ac97->id & 0xfffffff0) {
	case 0x414c4320:
 	case 0x414c4730:
	case 0x414c4750:
  	 	ac97->id = ac97->id & 0xfffffff0;
	        break;
   	case 0x414c4710:
		if ((reg & 0x0f) == 0)    
                	ac97->id = 0x414c4710;
        	else if ((reg & 0x0ff) == 0x11)
                        ac97->id = 0x414c4711;
		else if ((reg & 0x0ff) == 0x13)
                        ac97->id = 0x414c4712;
			        else if ((reg & 0x0ff) == 0x16)
 	                ac97->id = 0x414c4713;
	        else
                        ac97->id = 0x414c4710;
                break;  
 	case 0x414c4720:
                if (((reg & 0x0f) > 0) && ((reg & 0x0f) < 4))
                        ac97->id = 0x414c4720;
	        else if (((reg & 0x0f) > 3) && ((reg & 0x0f) < 8))
                        ac97->id = 0x414c4721;


As there are now these "bitmasks" in new ac97_codec.c, these chips can
be identified (as a start)...

Question: Is anybody working on that ALC stuff?


Regards,

	Sassi




_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

       reply	other threads:[~2002-05-17 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E178Qdh-0008Ow-00@usw-sf-list2.sourceforge.net>
2002-05-17 14:41 ` Christoph Sassenberg [this message]
     [not found] <E17BvQU-0000bb-00@usw-sf-list2.sourceforge.net>
2002-05-26 13:37 ` ALC Chips, now Realtek Sundance

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=20020517164123.7630a0bf.sassi@sforce.org \
    --to=sassi@sforce.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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