From owner-freebsd-scsi Tue Mar 26 17:59:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA00989 for freebsd-scsi-outgoing; Tue, 26 Mar 1996 17:59:54 -0800 (PST) Received: from hda.com ([199.232.245.79]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA00975 for ; Tue, 26 Mar 1996 17:59:50 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id UAA04383; Tue, 26 Mar 1996 20:50:02 -0500 From: Peter Dufault Message-Id: <199603270150.UAA04383@hda.com> Subject: Re: HP 4020i CD-R wishes To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 26 Mar 1996 20:50:01 -0500 (EST) Cc: freebsd-scsi@FreeBSD.org Reply-To: hdalog@zipnet.net In-Reply-To: <199603261806.TAA15110@uriah.heep.sax.de> from "J Wunsch" at Mar 26, 96 07:06:52 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > As Peter Dufault wrote: > > > We have some layering now, where you go through per-device ioctl > > code first and then hit the general code if it wasn't handled. It > > would probably benefit from one more layer: > > Hmm, but that doesn't cover stacking for read or write op's. However, > perhaps we don't need this at all? > Is it stacking you want or better packaging? I think of stacking as more like the ccd driver where you stack on top of an existing driver without changing it much. Do you want to be able to say "the worm uses this style write" and use the same code in use in the tape writer? Then I think we tidy up and formalize the libraries already started so that if you use the same type of write for a tape and a recorder you don't have the replicated code. -- Temporarily via "hdalog@zipnet.net"... Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267