On Fri, 12 Sep 2003, Takashi Iwai wrote:
> At Fri, 12 Sep 2003 12:31:32 +0200 (CEST),
> Jaroslav wrote:
> >
> > On Fri, 12 Sep 2003, Takashi Iwai wrote:
> >
> > > > I have plans to extend the mixer interface to pass (and handle) the dB
> > > > resolution. But it will be done completely in the user space. The alsa-lib
> > > > will analyze information from the driver (hardware components) and then it
> > > > will use a predefined expressions for these transformations. I think that
> > > > we should not polute the kernel space with these "additional" things.
> > >
> > > agreed. it's a user-space thing.
> > >
> > > but some additional information like min/max dB would be needed, too?
> >
> > I think that we can have this database (including expressions which
> > converts hardware range to the dB range) in alsa-lib, too. It was one of
> > reasons why I am working on the lisp integration to alsa-lib, because we
> > can easy describe mathematic expressions with this language.
>
> oh, yes, it's good. it would be easier to add new information, too.
>
> well, we'll still need to provide a good method to tell the used codec
> (or any other info) for user apps. the same driver can have different
> codecs, which behave quite differently. as you know, even ac97 codecs
> may have different dB range for the same element...
Yes, the best way to determine the ac97 codec confiration is reading of
ac97 registers. The proc interface might help us and we can move this
functionality to sysfs later.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
