[alsa-devel] Splitting up the HDA-INTEL modules

Takashi Iwai tiwai at suse.de
Wed Jan 16 15:54:57 CET 2008

At Wed, 16 Jan 2008 10:51:45 -0200,
Claudio Matsuoka wrote:
> On Jan 16, 2008 9:54 AM, Takashi Iwai <tiwai at suse.de> wrote:
> > It's a good question whether the setup should be the codec (driver)
> > dependent or generic.  I tend to believe that we'll need some
> > codec-specific workarounds, at least, to keep the same level of the
> > driver support as now.
> >
> > In my earler development, I implemented some byte-code implementer in
> > the driver so that it can be handled in a generic way.  The current
> > codec specific implementation is interpreted to a byte-code in the
> > user-space tool, and it runs on the driver.  Of course, this method
> > adds an interpreter to the driver, and I'm also not sure whether this
> > method is optimal.
> I'll have a look at the current hda-tools and see how it works before
> emmiting any opinion, I am aware that the codec configuration is more
> complicated than it looks.

I put the versoin 0.0.10b now.  It includes the patches to the latest
ALSA tree but no other changes.

(it might take some time to be exported to the outside.)


More information about the Alsa-devel mailing list