[lkml]   [2000]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Re: Move of input drivers, some word needed from you
On Mon, Aug 21, 2000 at 07:48:15AM -0700, Linus Torvalds wrote:
> Are all the SCSI drivers going to be under drivers/scsi/? No. The "normal"
> ones that don't have any better place for them are, but nobody has really
> suggested moving drivers/usb/storage around to another place just because
> it uses the SCSI layer.

> I object to moving files around in ways that makes the tree _less_ clear.
> I want the kernel tree to be a nice hierarchy of drivers, filesystems,
> etc. I don't see the point in lumping everything together in one
> subdirectory just because they happen to be "input" devices, regardless of
> what kind of device they really are.

I have to admit I don't quite understand how drivers/ is organized right now.
There seem to be at least four criteria for subdirectories of drivers/:

drivers/<function> (sound, net)
drivers/<interface> (char, block) (this isn't the same as function IMHO)
drivers/<bus-the-device-is-on> (usb, sbus)
drivers/<architecture> (s390, sgi)

then there are some hybrids (usb seems to be both "devices that are on USB"
and "USB controllers") and strange things like drivers/char/sysrq.c (which
isn't a character device at all, and isn't really a driver either).

I don't see any particular preference, and my impression is that new
directories get added pretty much at random.

I think I'm not the only one to be a bit confused about this.

Philipp Rumpf
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:37    [W:0.140 / U:2.924 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site