From: Daniel Drake <dsd@laptop.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Conexant CX20582 HDA codec support
Date: Tue, 30 Jun 2009 19:48:33 +0100 [thread overview]
Message-ID: <1246387713.5695.20.camel@polyethylene> (raw)
In-Reply-To: <s5hskhjnqzc.wl%tiwai@suse.de>
Hi,
On Mon, 2009-06-29 at 14:50 +0200, Takashi Iwai wrote:
> Ideally, yes.
> If the codec tree looks similar as other Conexant codecs, you can adapt
> patch_conexant.c...
Thanks for the quick explanations to all my issues. Makes sense.
Our contacts at Conexant pointed us to this file:
http://www.linuxant.com/alsa-driver/alsa-driver-linuxant-1.0.19ppch12-1.noarch.rpm.zip
The patch_conexant.c inside includes support for CX20582 ("Pebble") and
a few more. Complete list:
{ .id = 0x14f15061, .name = "CX2058? (Pebble)",
.patch = patch_cxtppch },
{ .id = 0x14f15066, .name = "CX20582 (Pebble)",
.patch = patch_cxtppch },
{ .id = 0x14f15067, .name = "CX20583 (Pebble 56-LQFP)",
.patch = patch_cxtppch },
{ .id = 0x14f15068, .name = "CX20584 (Pebble)",
.patch = patch_cxtppch },
{ .id = 0x14f15069, .name = "CX20585 (Pebble 56-QFN)",
.patch = patch_cxtppch },
{ .id = 0x14f15070, .name = "CX20592 (Pelican)",
.patch = patch_cxtppch },
{ .id = 0x14f15071, .name = "CX20593 (Pelican 56-LQFP)",
.patch = patch_cxtppch },
{ .id = 0x14f15072, .name = "CX20594 (Pelican)",
.patch = patch_cxtppch },
{ .id = 0x14f15073, .name = "CX20595 (Pelican 56-QFN)",
.patch = patch_cxtppch },
{ .id = 0x14f15074, .name = "CX2059? (Pelican)",
.patch = patch_cxtppch },
{ .id = 0x14f150D0, .name = "CX20688 (Cabo)",
.patch = patch_cxtppch },
{ .id = 0x14f150D4, .name = "CX20692 (Huntington)",
.patch = patch_cxtppch },
{ .id = 0x14f150D5, .name = "CX20693 (Huntington)",
.patch = patch_cxtppch },
{ .id = 0x14f150D6, .name = "CX20694 (Huntington)",
.patch = patch_cxtppch },
{ .id = 0x14f150D7, .name = "CX20695 (Huntington)",
.patch = patch_cxtppch },
{ .id = 0x14f12bfa, .mfg = 2, .name = "HSF",
.patch = patch_cxthsfmodem },
{ .id = 0x14f12c06, .mfg = 2, .name = "HSF",
.patch = patch_cxthsfmodem },
{ .id = 0x14f10000, .mask = 0xffff0000, .mfg = 2, .name = "HSF",
.patch = patch_cxthsfmodem },
Perhaps a useful link to keep around in future if other people come
along looking for new codec support...
Over the next few days, I plan to extract the CX20584 support, get it
working on the XO-1.5 and then send you a patch.
Thanks,
Daniel
next prev parent reply other threads:[~2009-06-30 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 12:10 Conexant CX20582 HDA codec support Daniel Drake
2009-06-29 12:26 ` Mark Brown
2009-06-29 12:48 ` Takashi Iwai
2009-07-03 20:05 ` Daniel Drake
2009-07-03 20:45 ` Takashi Iwai
2009-06-29 12:50 ` Takashi Iwai
2009-06-30 18:48 ` Daniel Drake [this message]
2009-06-30 19:23 ` Tony Vroon
2009-06-30 19:27 ` Daniel Drake
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=1246387713.5695.20.camel@polyethylene \
--to=dsd@laptop.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 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.