[alsa-devel] Suggestion for getting alsa to use Conexant

[Tobin Davis]

Just out of curiosity, has anyone with these codecs tried the linuxant
software?  I looked at it briefly, and they are modifying my
patch_conexant.c driver.  Some of the changes I may include in the main
alsa driver (hey, I wrote the bulk, so why not), some of it would never
pass kernel coding style.

I am kind of peeved that they don't bother to communicate with the alsa
team, instead they take all of the hda code and hack it up, adding their
copyright info to the code header (see header patch attached).  Takashi,
what's your take on this?

Tobin

On Fri, 2007-05-25 at 12:14 +0200, Takashi Iwai wrote:

> At Thu, 24 May 2007 19:32:55 -0700,
> Tobin Davis wrote:
> > 
> > I don't think this is limited to the Conexant CX20549 (5045) or the
> > CX20551 (5047).  I have a laptop with a Conexant vendor ID of 2bfa.  The
> > hda-intel driver picks it up, but uses the hda-generic configuration.
> > 
> > On the CX20549 & CX20551, I think I need to toggle a bit to enable the
> > MFG portion.  I have a test board here, but the drivers are not
> > detecting it, even without my patch_conexant code.  I'll look at the
> > intel-80xm module, but it is written for the AC'97 bus specification,
> > which is very different from the HDA bus specification.
> 
> The bus design isn't a so big issue, but the problem would be rather
> the difference of the codec/controller communication.  For example,
> smartlink modem codecs (si3054) and compatibles are already supported
> in patch_si3054.c.  As you can see, the code is really small.
> 
> AFAIK, the conexant modem codec requires extra communication, a kind
> of ACK, and thus incompatible with smartlink codecs.  Similarly, the
> intel8x0m driver also doesn't support conexant chips because the
> conexant codecs need different controls.
> 
> Ideally, the whole encoding stuff should go to the user-space like
> slmodemd.  I once tried to convince Conexant guys to do that, but they
> disagreed because of lack of man power.  To me, it's hard to imagine
> because keeping the kernel driver needs more effort...
> 
> 
> Takashi
> 
> > 
> > Tobin
> > 
> > On Wed, 2007-05-02 at 21:13 -0500, Victor Schneider wrote:
> > 
> > > How about being able to parameterize Alsa modules so that the intel 80xm 
> > > module finds any hda modem that also acts as an Intel hda chip? I am 
> > > referring to the Conexant combination modem and hda chip that gets 
> > > identified as "Conexant Waikiki" by alsamixer, but that 80xm can't find as a 
> > > modem. Giving the 80xm module the device:identifier value to override its 
> > > detection of the Intel version of the Conexant hda modem might let slmodemd 
> > > work.
> > > 
> > > _______________________________________________
> > > Alsa-devel mailing list
> > > Alsa-devel at alsa-project.org
> > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > 
> > -- 
> > Tobin Davis <tdavis at dsl-only.net>
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel at alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > 

-- 
Tobin Davis <tdavis at dsl-only.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cxtheader.patch
Type: text/x-patch
Size: 754 bytes
Desc: not available
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20070525/cc81345f/attachment.patch