From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: alsa on non-linux Date: Tue, 14 Jan 2014 15:04:58 +0100 Message-ID: <52D5440A.6080508@ladisch.de> References: <20140110153700.GC1173@quark.internal.precedence.co.uk> <20140114101709.GB160@quark.internal.precedence.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by alsa0.perex.cz (Postfix) with ESMTP id 3BE8F261717 for ; Tue, 14 Jan 2014 15:05:07 +0100 (CET) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9F51E20F45 for ; Tue, 14 Jan 2014 09:05:01 -0500 (EST) In-Reply-To: <20140114101709.GB160@quark.internal.precedence.co.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Patrick Welche , Takashi Iwai Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Patrick Welche wrote: > I started out, writing the attached patch in November, but then it looked > as though the boundaries of application library interface and linux sound > chip driver had become so blurred that I thought that a decision had been > taken to bin all OSes bar linux, hence the question. Can you give me a > hint on how you think it is supposed to work? Only the "hw" plugins access the Linux kernel drivers. Anything else should be portable (with the exception of plugins like "dmix" that require a "hw" plugin as their slave). For most device types (hwdep/seq/rawmidi/timer), the hw plugin is the only implementation, so a portable alsa-lib has only control and pcm devices at the moment. Regards, Clemens