From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Schmidt Date: Fri, 06 Jan 2006 11:34:40 +0000 Subject: Re: [OT] ALSA userspace API complexity Message-Id: <20060106123440.7359e430@mango.fruits.de> List-Id: References: <20050726150837.GT3160@stusta.de> <20060103193736.GG3831@stusta.de> <20060104030034.6b780485.zaitcev@redhat.com> <20060106041421.31579e69.froese@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Hannu Savolainen Cc: Edgar Toernig , Takashi Iwai , linux-sound@vger.kernel.org, LKML On Fri, 6 Jan 2006 05:33:43 +0200 (EET) Hannu Savolainen 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