Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030270AbWADSTS (ORCPT ); Wed, 4 Jan 2006 13:19:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030269AbWADSTR (ORCPT ); Wed, 4 Jan 2006 13:19:17 -0500 Received: from affenbande.org ([81.169.150.36]:38529 "EHLO tarzan.affenbande.org") by vger.kernel.org with ESMTP id S1030267AbWADSTQ (ORCPT ); Wed, 4 Jan 2006 13:19:16 -0500 Date: Wed, 4 Jan 2006 19:17:50 +0100 From: Florian Schmidt To: Takashi Iwai Cc: Adrian Bunk , Jesper Juhl , Olivier Galibert , Alistair John Strachan , Jan Engelhardt , 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: <20060104191750.798af1da@mango.fruits.de> In-Reply-To: References: <20060103203732.GF5262@irc.pl> <9a8748490601031256x916bddav794fecdcf263fb55@mail.gmail.com> <20060103215654.GH3831@stusta.de> <20060103221314.GB23175@irc.pl> <20060103231009.GI3831@stusta.de> <20060104000344.GJ3831@stusta.de> <20060104010123.GK3831@stusta.de> <20060104113726.3bd7a649@mango.fruits.de> Organization: affenbande X-Mailer: Sylpheed-Claws 1.0.5 (GTK+ 1.2.10; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1440 Lines: 32 On Wed, 04 Jan 2006 18:54:48 +0100 Takashi Iwai wrote: > Note that as of OSS emulation, this is no longer true. The OSS > devices are opened as "non-blocking" per default. ALSA native devices > are opened as "blocking" just to keep the compatible behavior, > though. Hi Takashi, do you know of _any_ app relying on this behaviour? If not, make blocking open and blocking read/write different things (as they really are different things). Maybe create a /proc control, so users can revert to the olde behaviour if there really is any need. I simply cannot imagine that any ALSA app relies on this weird behaviour. I only ever hear how it confuses people [Hang out a bit on #alsa on irc.freenode.org: "my alsa driver is broken as this and that app hangs!!!" - "no it's expected behaviour" - "WTF!!!?" ;) <- smiley]. It is also still quite a common case i suppose as when an OSS app has a device open, the ALSA apps trying to open it in blocking mode will again hang. Or so i'd think. My soundcard is hw mixing capable (thank god ;)), so i don't really know, and it's been a while since i hang out regularly on that channel. If i talk out of my ass, let me know. Regards, Flo - 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/