From: Takashi Iwai <tiwai@suse.de>
To: Zinx Verituse <zinx@epicsol.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: CMI9739A
Date: Thu, 25 Nov 2004 17:18:57 +0100 [thread overview]
Message-ID: <s5hact5oqa6.wl@alsa2.suse.de> (raw)
In-Reply-To: <20041125004649.GA21551@bliss>
At Wed, 24 Nov 2004 18:46:49 -0600,
Zinx Verituse wrote:
>
> I recently purchased a motherboard with an on-board CMI9739A (or so it claims)
>
> the id is: 0x434d4983
>
> Unfortunately, simply adding the line:
>
> { 0x434d4983, 0xffffffff, "CMI9739A", patch_cm9739, NULL },
>
> causes the card to be muted, reguardless of the mixer, because of the init
> code in patch_cm9739 -- the init code apparently isn't compatible.
>
> Removing the initialization code, but leaving the ops, gives a few more
> functional mixer options (like "Line-In as Surround" and "Mic as Center/LFE")
According to the datasheet, CM9739A is indeed compatible with 9739
except for pins.
Could you get the ac97 register dump of the good- and bad-running
states (from /proc/asound/card0/codec97#0/* files) ?
I guess the GPIO initialization (for using HP) is wrong there. Doing
the following helps?
# echo 72 0001 > /proc/asound/card0/codec97#0/ac97#0-0+regs
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-25 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 0:46 CMI9739A Zinx Verituse
2004-11-25 16:18 ` Takashi Iwai [this message]
2004-11-30 2:05 ` CMI9739A Zinx Verituse
2004-11-30 10:09 ` CMI9739A Takashi Iwai
2004-12-12 9:30 ` CMI9739A Zinx Verituse
2004-12-12 10:57 ` CMI9739A Zinx Verituse
2004-12-20 14:04 ` CMI9739A 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=s5hact5oqa6.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=zinx@epicsol.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.