From owner-freebsd-hackers  Thu Feb 16 23:26:59 1995
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA18121 for hackers-outgoing; Thu, 16 Feb 1995 23:26:59 -0800
Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id XAA18115 for <freebsd-hackers@freefall.cdrom.com>; Thu, 16 Feb 1995 23:26:58 -0800
Received: by tfs.com (smail3.1.28.1) 
Message-Id: <m0rfN58-0003wTC@TFS.COM>
From: julian@tfs.com (Julian Elischer)
Subject: Re: NEW_SCSICONF
To: dufault@hda.com (Peter Dufault)
Date: Thu, 16 Feb 1995 23:26:26 -0800 (PST)
Cc: freebsd-hackers@freefall.cdrom.com
In-Reply-To: <199502162219.RAA18699@hda.com> from "Peter Dufault" at Feb 16, 95 05:19:19 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1958      
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> 
> Can someone explain the history of "NEW_SCSICONF", and whether it should
> be left in there?  I'd like to remove it.
The NEW_SCSICONF stuff is an attempt to make some of the features
of teh tape driver (e.g. rogue entries) more general to the
SCSI system as a whole, and to rationalise some of the scsi
systems's configuration actions and interfaces. It was implimented
by the PCI driver crew, and has some good features. Don't just delete
it.

Having said that, The whole SCSI system is badly in need of a revamp.
It's been just over a year since I last did this, and it's screaming
for a cleanup..

> 
> Also, is anyone using the "predef" stuff in scsiconf.c?  I'd like to
> remove it and replace it with a traditional config approach.
yes I have used it but only on the OSF version of the code...

Some of the things that need doing..
1/ examination of charles's changes in NetBSD, and the adoption of some
quite astute simplifications and reallignments he's done.. (also bug-fixes)
The difficult part in this is that he''s reformatted everything again,
and the NetBSD config stuff is considerably different, leading to quite
different softc structures and configuration routines.
2/ examination of the NEW_SCSICONF code and extraction of pertinant ideas
and changes.
3/ both sd and wd drivers should share more "how a disk behaves" code..
4/ the tape driver needs a good shake-out
5/ the cd driver needs code for audio-read (I have that for toshiba drives
at least). possibly dependent on drive manufacturer.
6/ all-round documentation of interfaces... comments checked for correctness.

> 
> Peter
> 
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 300 lakeside Dr. oakland CA. \___   ___ | country !
+- X_.---._/  USA+(510) 645-3137(wk)           \_/   \\            
          v