[142] in linux-scsi channel archive
Re: SCSI defines for pass-thru commands
daemon@ATHENA.MIT.EDU (Linus Torvalds)
Fri Apr 14 04:24:42 1995
Date: Fri, 14 Apr 1995 09:59:49 +0300
From: Linus Torvalds <Linus.Torvalds@cs.Helsinki.FI>
In-Reply-To: Drew Eckhardt's message as of Apr 14, 0:12
To: Drew Eckhardt <drew@boulder.openware.com>, Jim Freeman <jfree@caldera.com>
Cc: linux-scsi@vger.rutgers.edu, linux-kernel@vger.rutgers.edu
Drew Eckhardt: "Re: SCSI defines for pass-thru commands" (Apr 14, 0:12):
>
> >It seems bad form to have a
> > #include "/usr/src/linux/drivers/scsi/scsi.h"
> >line in a user-space application. Nor does it seem right to duplicate
> >these defines for an application. I'd vote to have them defined once,
> >in a <linux/scsi.h>, then have that included in the kernel include file.
> >
> >Comments?
>
> Various pieces of scsi.h, scsi_ioctl.h, etc. should all move to a
> user level include file; the reason they stayed where they are is
> a throw back to Linux 0.12 and 0.95 when the SCSI subsystem was
> essentially a separate distribution and I didn't support SCSI commands
> to/from user space.
I'd actually want all the "high-level" SCSI header files under
<linux/xxx.h> (or we could make it <scsi/xxx.h>, but I doubt it really
needs a separate directory). The reason is kernel drivers: in the
not-too-far future we'll find ourselves with different low-level scsi
drivers for different architectures (m68k, sparc, whatever), and I don't
want to keep them all under linux/drivers/scsi/xxx. In fact, I'd want
something like "linux/drivers/pci/scsi" and "linux/drivers/xxx/scsi" for
different bus systems (with linux/drivers/scsi only containing the
high-level scsi interface).
Under that kind of setup, we'd need to have the scsi header files
somewhere standard anyway.
Linus
