[92] in linux-scsi channel archive
Re: New module stuff needs more work
daemon@ATHENA.MIT.EDU (Eric Youngdale)
Wed Mar 8 01:59:33 1995
From: "Eric Youngdale" <eric@aib.com>
Date: Tue, 7 Mar 1995 23:21:14 +0000
To: linux-scsi@vger.rutgers.edu
Cc: linux-kernel@vger.rutgers.edu
FWIW, I spent a few hours over the weekend and I succeeded in
fully modularizing the scsi code. I was able to take a 1.1.95
kernel with no scsi support, and load separate modules for the core
scsi, disk, tape, cdrom, generic, and the software simulator of a
low-level driver. I will hold these patches back until 1.3, since
there is no point in introducing such a thing into 1.2 at this late
date. I have not had time to load the patches onto my real linux
box and try them with a live scsi system - I have only tried this on
my laptop so far. In other words, there could easily still be bugs.
The idea is that once you load the core scsi module, you can
load/unload any/all of the low level and device modules in more or
less any order that you want with the only restriction being that you
cannot unload a module that is in use (i.e. if you have a disk
mounted you will not be able to unload either the disk module or the
low-level driver module). If anyone wants to play, drop me an email.
At some point I still want to define a modular interface for
a cdrom ioctl driver that would allow people to load modules for
various brands of cdrom that use non-SCSI 2 commands, and I still
intend to separately modularize the scsi constants file (currently
part of the core scsi module), but that one is a pretty low priority.
There are a few other scsi things that are probably more important
that I think I just figured out how to cleanly implement.
-Eric
--
"The woods are lovely, dark and deep. But I have promises to keep,
And lines to code before I sleep, And lines to code before I sleep."
