Re: alsa-lib plugin devel

[Marcel Holtmann <marcel@holtmann.org>]

Hi Takashi,

> > > We can create a new API to list up the available PCMs.
> > > It will help applications, I guess.
> > > 
> > > The problem is that plugins which aren't bound to drivers like btsco
> > > are hard to detect whether they really work in advance.
> > > Do we need a probe callback for such a plugin?
> > 
> > I suppose there are problems listing things because the plugins behave 
> > differently. I don't fully understand the problem.
> > 
> > But... it would be a big inconvenience for the user to be told to know 
> > the device name or go look it up in .asoundrc and/or /etc/asound.conf. 
> > The {linphone,xine,gnomemeeting} gui should be able to discover and list 
> > the plugin devices.
> 
> I think putting marks in the PCM defintions is the easiest way.
> 
> Another question about listing devices: shall we list up the entries
> like "front", "rear", etc?
> 
> IMO, the function should list up only the basic PCMs.  I.e. the
> default analog output and the SPDIF (or whatever additional outputs).

from the Bluetooth standpoint we need only to list the input and
outputs, because there is nothing more defined. Neither for SCO or for
the A2DP devices.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl