From owner-freebsd-questions Mon Sep 29 14:02:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA09594 for questions-outgoing; Mon, 29 Sep 1997 14:02:27 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA09489; Mon, 29 Sep 1997 14:01:16 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA10183; Mon, 29 Sep 1997 13:57:40 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010173; Mon Sep 29 20:57:30 1997 Message-ID: <34301602.167EB0E7@whistle.com> Date: Mon, 29 Sep 1997 13:56:34 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: MetcalJM@utrc.utc.com CC: gibbs@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Q: Good learning documents for SCSI device drivers References: <95A2D2968BD9D011A38B00A0C95727DB27AB03@express2.res.utc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I wrote most of hte present SCSI system for FreeBSD, however it's been several years since I did that, and I've been working on other things. Thw adapters I wrote drivers fro were all "intelligent" adapters so I never really got into the "NEXUS" stuff. Basically the nexus is a particular pairing of a client and a requestor, for an operation.. I never got much more into it than that.. I can suggest you visit the following ftp site: ftp://ftp.symbios.com/pub/standards/io/ where you will find the SCSI standard and many ther related things. While I can give comments on how the present SCSI system is written, that will soon be a thing of the past. The present SCSI system was good for its day, but time has marched on and Justin (CC'd) is writing a new system based on the SCSI-CAM standard. This should allow us to meke better use of 3rd party CAM modules. Never-teh-less, if you have specific questions about the UPPER layers of the current SCSI system, feel free to ask (I may not know the answer however). There was a massive set of changes that went into it a couple of years ago that obfuscated a lot of what's going on behind MACROs which I was not happy with, and some of the structures changed function with time, and are there-for misleadingly named. I started several times on documents on how it fitted together but never got past the introduction. MetcalJM@utrc.utc.com wrote: > > Hello, > > I am writing to ask if anyone can point me to some good learning > documents for learning the basics of the SCSI subsystem. I have > an open problem with the gnats database > > http://www.freebsd.org/cgi/query-pr.cgi?pr=4498 > > where my Iomega Zip 100 SCSI drive atached to my ProAudioStudio > SCSI adapter is having data corruption problems. I have written > to both the FreeBSD and LINUX authors of the ncr5830 code and > have received no replies. I understand since few people actually > using FreeBSD use such hardware, I am probably on my own for a > fix. All I'm asking is some direction in finding good books > to learn from in order to solve the problem myself. I have > never written any kind of device driver, much less a driver > for a SCSI device. I have fairly good C programming skills > (ie, I can understand the logic flow of the ncr5830.c kernel > code and understand the definitions and usage syntax of the data > structures). But the code is otherwise meaningless to me > since I have no idea about how the code interacts with the > hardware (eg. what's "establising a nexus" mean?). I'm sure > there are plenty of great books out there where a motivated > person like myself can learn what he needs to know. > > I hope some kind soul can give me some focus. Understand > that I would need the basics, yet I would also need enough practical > focus, from whatever sources are suggested, to actually trouble-shoot > and hack into some real code. Ideally, literature that might cover > the ncr5830 would be great!! I understand this to be a well documented > and understood device. > > Thanks in advance for any help!! > > JM > ----------- > > > Jeffrey M. Metcalf > > Assistant Computer Systems Support Engineer > > United Technologies Research Center > > metcaljm@utrc.utc.com > > (860) 610-7576 > > > >