From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
alsa-devel@alsa-project.org, perex@perex.cz
Subject: Re: Moving sound/* to drivers/ ?
Date: Thu, 22 May 2008 11:57:40 +0200 [thread overview]
Message-ID: <48354394.9040205@keyaccess.nl> (raw)
In-Reply-To: <s5hy7623fqs.wl%tiwai@suse.de>
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.
next prev parent reply other threads:[~2008-05-22 9:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 21:20 Moving sound/* to drivers/ ? Takashi Iwai
2008-05-21 21:44 ` Linus Torvalds
2008-05-21 21:54 ` Sam Ravnborg
2008-05-21 21:58 ` [alsa-devel] " Rene Herman
2008-05-21 22:08 ` Rene Herman
2008-05-21 23:21 ` Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?] Paul Mackerras
2008-05-21 23:51 ` Linus Torvalds
2008-05-22 0:56 ` Al Viro
2008-05-22 1:20 ` Linus Torvalds
2008-05-22 1:23 ` Moving include/asm-* David Miller
2008-05-22 8:09 ` Andreas Schwab
2008-05-22 16:12 ` David Miller
2008-05-22 16:32 ` Andreas Schwab
2008-05-22 17:43 ` David Miller
2008-05-22 1:23 ` Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?] Harvey Harrison
2008-05-22 1:25 ` Moving include/asm-* David Miller
2008-05-22 1:29 ` Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?] Linus Torvalds
2008-05-22 1:36 ` Al Viro
2008-05-22 4:20 ` Jeff Dike
2008-05-22 5:26 ` Al Viro
2008-05-22 16:27 ` Jeff Dike
2008-05-22 17:18 ` Sam Ravnborg
2008-05-22 1:30 ` Al Viro
2008-05-22 22:52 ` Arnd Bergmann
2008-05-21 22:05 ` [alsa-devel] Moving sound/* to drivers/ ? Timur Tabi
2008-05-21 22:23 ` Adrian Bunk
2008-05-22 8:22 ` Takashi Iwai
2008-05-21 23:37 ` Jeff Garzik
2008-05-21 23:53 ` Rene Herman
2008-05-22 6:26 ` Jaroslav Kysela
2008-05-22 7:12 ` Sam Ravnborg
2008-05-22 7:20 ` Jaroslav Kysela
2008-05-22 8:11 ` Rene Herman
2008-05-22 8:27 ` Takashi Iwai
2008-05-22 8:55 ` Jan Engelhardt
2008-05-22 15:04 ` Linus Torvalds
2008-05-22 15:50 ` Jan Engelhardt
2008-05-22 16:40 ` Rene Herman
2008-05-22 9:57 ` Rene Herman [this message]
2008-05-22 14:22 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48354394.9040205@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox