From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935304AbYEVI2N (ORCPT ); Thu, 22 May 2008 04:28:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755566AbYEVI16 (ORCPT ); Thu, 22 May 2008 04:27:58 -0400 Received: from mail.suse.de ([195.135.220.2]:36695 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762161AbYEVI14 (ORCPT ); Thu, 22 May 2008 04:27:56 -0400 Date: Thu, 22 May 2008 10:27:55 +0200 Message-ID: From: Takashi Iwai To: Rene Herman Cc: Jeff Garzik , linux-kernel@vger.kernel.org, Linus Torvalds , alsa-devel@alsa-project.org, perex@perex.cz Subject: Re: Moving sound/* to drivers/ ? In-Reply-To: <4834B5E2.3040301@keyaccess.nl> References: <4834B252.1080700@garzik.org> <4834B5E2.3040301@keyaccess.nl> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta28) (fuki) (+CVS-20070806) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Thu, 22 May 2008 01:53:06 +0200, Rene Herman wrote: > > On 22-05-08 01:37, Jeff Garzik wrote: > > > Speaking as a former OSS driver maintainer, I always preferred > > drivers/sound. > > > > Though Rene's suggestion (use both sound/ and drivers/sound/) might make > > sense if the subsystem code is huge -- I supported the drivers/block/ -> > > block/ code movement for example. > > Well, not _huge_ but ALSA is very much structured like that; large > middle layer with "miniport" drivers (I do by the way expect this was > also Takashi plan originally due to him using sound/* and not just > "sound/"; that is, I took the * to be shorthand for isa, pci, usb and so on) Well, no, I originally thought moving all $LINUX/sound to $LINUX/drivers/sound. The sound core stuff is already in sound/core, so it can be peacefully in drivers/sound/core, just like other drivers like USB, V4L, etc. > From a structural view, the PCM core is just as much not a driver as > the IP protocol isn't one and moving all of sound/ to drivers/ would > trade the current "why are the drivers not under drivers/?" issue for a > "why is all this non-driver code under drivers/?". > > This "net model" of sound/ and drivers/sound/ would be cleanest I feel. I think it's a question of the balance. The net stuff is huge, 10 times more codes than the sound core. An argument for keeping the sound core in /sound is that this is used not only by sound drivers but also by some video drivers. Takashi