lkml.org 
[lkml]   [2006]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [OT] ALSA userspace API complexity
On Fri, 6 Jan 2006 05:33:43 +0200 (EET)
Hannu Savolainen <hannu@opensound.com> wrote:

> Then this is in no way an API issue. Many OSS drivers (including envy24)
> create separete device files for each input/output channel (or device pair).
> Applications can chose to open the first device file in for all the
> channels or any combination of the devices in mono/stereo/n-channel mode.
>
> All this depends only on the driver implementation. There is nothing API
> related. Any app can open the devices as usual without paying any
> attention on the channel allocation (which is done automatically by the
> driver). xmms (or whatever else consumer app) can open the device and ask
> for stereo access. Equally well a DAB application can open the device and
> ask for full 10 output channels (or anything between 1 and 10). No special
> API features are needed for this.

Hi,

i would find it helpful if you always made it crystal clear about what
version of OSS you are talking about:

- your proprietary version

- or the free one in the kernel

Mixing these isn't helping the discussion.

Flo

--
Palimm Palimm!
http://tapas.affenbande.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-01-06 12:37    [W:0.270 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site