Folks: Thanks for helping me on this. I do have another question. This may sound too basic, but I am still a little unclear. If I am creating a patch for a new codec, how do I decide what controls don't get created by the stac92xx_build_controls and stac92xx_auto_config? Do I start off with having no mixer structure at all and then see what's missing based on the Codec widget diagram?
That's what I would do. Then you can add controls as needed. Otherwise you end up with duplicate controls.
The other thing you could do is if this is for a new codec currently not supported, and you are writing a new stac####_patch function, don't call the stac92xx_auto_config routine and do it manually. Look at the STAC9872 Hack section for reference.
Thanks Mark Allyn -----Original Message----- From: Eduardo Pereira Habkost [mailto:ehabkost@xxxxxxxxxxx] Sent: Thursday, March 08, 2007 4:54 AM To: Tobin Davis Cc: Allyn, Mark A; alsa-devel@xxxxxxxxxxxxxxxxxxxxx Subject: Re: Question on hda mixer structures Hi, On Wed, Mar 07, 2007 at 04:15:17PM -0800, Tobin Davis wrote: > The stac925x_mixer structure is only for controls that don't get created > by stac92xx_build_controls{}. The volume controls for inputs and > outputs are auto-generated by this function. Do you mean stac92xx_parse_auto_config()? The controls in stac925x_mixer seem to be exactly the ones that do get created by stac92xx_build_controls().
|
-- Tobin Davis <tdavis@xxxxxxxxxxxx> |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
