Return to BSD News archive
Xref: sserve comp.unix.bsd:5996 comp.os.linux:11614
Newsgroups: comp.unix.bsd,comp.os.linux
Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!usc!wupost!spool.mu.edu!agate!tfs.com!tfs.com!julian
From: julian@tfs.com (Julian Elischer)
Subject: Re: 386BSD and Linux SCSI device drivers.
Message-ID: <1992Oct3.050456.15329@tfs.com>
Organization: TRW Financial Systems
References: <Sep.26.02.07.48.1992.16929@athos.rutgers.edu> <1992Oct1.032932.6773@unislc.uucp> <id.JHRT.WP6@ferranti.com>
Date: Sat, 3 Oct 1992 05:04:56 GMT
Lines: 41
In article <id.JHRT.WP6@ferranti.com> peter@ferranti.com (peter da silva) writes:
>Do 386BSD or Linux support SCSI devices with multiple units? I am looking at
>a cheap drive array consisting of 4 ESDI disk drives (Miniscribe 9380E or
>equivalent) on a single SCSI-bus ESDI controller. The drives are, so far
>as I can tell, unit 0 through unit 4. I would like to use these from a SCSI
>controller.
>--
The new scsi system I just released the beta3 set for does allow multiple lu
disks
e.g an aha4000 with 2 scsi disks.
I have not tested this on disks of course because I don't HAVE one
but it should work. I have tested it on a few devices
we have here that DO have multiple lu's and it works fine.
(it does assume that the first lu (lu0) has a device on it
otherwise it will just skip on to the next target without checking the
other LUs. (I just added that bit to speed things up in probe.. it USED to
check all LUs on ALL targets.)
e.g.
sd0 could be aha0: target 1: lu 0
sd1 could be aha0: target 1: lu 1
sd2 could be aha1: target 2: lu 0
sd3 could be bt0: target 3: lu 0
sd5 could be ahb0: target 1: lu 0
aha = aha1542x
bt = bustek 742a (or 747 I think)
ahb = aha1742
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@tfs.com +------>x USA \ in a very strange
| ( OZ ) 2118 Milvia st. Berkeley CA. \___ ___ | country !
+- X_.---._/ USA+(510) 704-3137(wk) \_/ \\
v