Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932393AbWAFKet (ORCPT ); Fri, 6 Jan 2006 05:34:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932201AbWAFKet (ORCPT ); Fri, 6 Jan 2006 05:34:49 -0500 Received: from boogie.lpds.sztaki.hu ([193.225.12.226]:64461 "EHLO boogie.lpds.sztaki.hu") by vger.kernel.org with ESMTP id S932199AbWAFKes (ORCPT ); Fri, 6 Jan 2006 05:34:48 -0500 Date: Fri, 6 Jan 2006 11:34:37 +0100 From: Gabor Gombas To: Hannu Savolainen Cc: Marcin Dalecki , Jesper Juhl , Lee Revell , Jan Engelhardt , Takashi Iwai , Adrian Bunk , Tomasz Torcz , Olivier Galibert , Alistair John Strachan , Andi Kleen , perex@suse.cz, alsa-devel@alsa-project.org, James@superbug.demon.co.uk, sailer@ife.ee.ethz.ch, linux-sound@vger.kernel.org, zab@zabbo.net, kyle@parisc-linux.org, parisc-linux@lists.parisc-linux.org, jgarzik@pobox.com, Thorsten Knabe , zwane@commfireservices.com, zaitcev@yahoo.com, linux-kernel@vger.kernel.org Subject: Re: [2.6 patch] schedule obsolete OSS drivers for removal Message-ID: <20060106103436.GB24929@boogie.lpds.sztaki.hu> References: <0D76E9E1-7FB0-41FD-8FAC-E4B3C6E9C902@dalecki.de> <1136486021.31583.26.camel@mindpipe> <1136491503.847.0.camel@mindpipe> <7B34B941-46CC-478F-A870-43FE0D3143AB@dalecki.de> <1136493172.847.26.camel@mindpipe> <8D670C39-7B52-407C-8BDD-3478DB172641@dalecki.de> <9a8748490601051535s5e28fd81of6814088db7ccac@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Copyright: Forwarding or publishing without permission is prohibited. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1297 Lines: 27 On Fri, Jan 06, 2006 at 03:36:47AM +0200, Hannu Savolainen wrote: > There are two very opposite approaches to do a sound subsystem. The ALSA > way is to expose every single detail of the hardware to the applications > and to allow (or force) application developers to deal with them. The OSS > approach is to provide maximum device abstraction in the API level (by > isolating the apps from the hardware as much as practically possible). Well, then it is quite clear to me: you can build an OSS-like interface on top of ALSA, but you cannot build an ALSA-like interface on top of OSS. This implies that an ALSA-like interface should be in the kernel, and an OSS-like interface should be implemented on top of it in userspace for those who do not need all the features. This way both camps are satisfied. Gabor -- --------------------------------------------------------- MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences --------------------------------------------------------- - 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/