From: Zinx Verituse <zinx@epicsol.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: CMI9739A
Date: Sun, 12 Dec 2004 04:57:07 -0600 [thread overview]
Message-ID: <20041212105707.GA7019@bliss> (raw)
In-Reply-To: <20041212093013.GA338@bliss>
On Sun, Dec 12, 2004 at 03:30:13AM -0600, Zinx Verituse wrote:
>
> Results:
> 72 0001 does nothing.
>
> However, setting one of the registers that actually differs - 64 - does
> fix it. The other registers that changed (6c, 70) seemed to have no effect.
>
> Non-working value for register 0x64: 0x5400
> Working value for register 0x64: 0x1438
>
> Also working value for register 0x64: 0x0010
>
> Bit 4 doesn't appear to be documented in the source, or in the CM9739
> documentation, and it actually defaults to 0x1438 here rather than 0x0000,
> so I've made a patch that just keeps the value (luckily, it seems to default
> to on when the card is initialized).
>
> The patch also includes the id for the 9739A.
> The patch is against 2.6.10-rc3, but it's fairly simple so it shouldn't
> be too hard to apply by hand if it fails.
Apparently this single bit isn't enough for surround; I should have checked
that. Bit 3 is also needed for surround, and I wouldn't doubt bit 5 being
needed for something.
--
Zinx Verituse http://zinx.xmms.org/
-------------------------------------------------------
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-12-12 10:56 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 ` CMI9739A Takashi Iwai
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 ` Zinx Verituse [this message]
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=20041212105707.GA7019@bliss \
--to=zinx@epicsol.org \
--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