linux-kernel - Re: Moving sound/* to drivers/ ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48354394.9040205@keyaccess.nl>
Date:	Thu, 22 May 2008 11:57:40 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Takashi Iwai <tiwai@...e.de>
CC:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	alsa-devel@...a-project.org, perex@...ex.cz
Subject: Re: Moving sound/* to drivers/ ?

On 22-05-08 10:27, Takashi Iwai wrote:

> At Thu, 22 May 2008 01:53:06 +0200,
> Rene Herman wrote:

>> 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.

Oh okay, misinterpreted that.

>> 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.

Indeed, but then again, block/ is 3 times as small. Don't actually know 
what the rationale was for that one but I'd expect some of the same 
reasons for that split to apply here.

Yes, there's more non driver work under drivers already but this might 
be something to try to minimise. Drivers are really sort of special in 
their nicely defined and limited impact and statistics such as the 
percentage of updates that are in drivers are used in that way.

> 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.

Mm, right. In a sense the snd-pcsp thing might be an argument even. 
There really wants to be one driver for the PC speaker which doesn't 
want to live in (drivers/)sound/ due to it being generic hardware but 
which does want to use sound/ to pretend it is.

In that sense, the sound core is shared infrastructure...

Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/