*BSD News Article 10645


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA419 ; Sun, 31 Jan 93 14:07:20 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD Installation
Message-ID: <1993Feb1.181334.6496@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University  (Ogden, UT)
References: <1993Jan31.090002.2601@organpipe.uug.arizona.edu> <1993Jan31.224750.19475@fcom.cc.utah.edu> <1993Feb1.045800.20194@serval.net.wsu.edu>
Date: Mon, 1 Feb 93 18:13:34 GMT
Lines: 49

In article <1993Feb1.045800.20194@serval.net.wsu.edu> hlu@luke.eecs.wsu.edu (H.J. Lu) writes:
>In article <1993Jan31.224750.19475@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>[...]
>
>>The WD7000 is not supported.  The fact that it comes up in the inventory
>>is precisely what has kept me from releasing a driver for the thing under
>>Julian's SCSI system.  Basically, the thing *shouldn't* be recognized by
>>the wd driver's probe -- I can fix it, but it means IDE drives aren't
>>recognized either.
>>
>>This is probably why AT&T provides SVR4.0 SCSI and ESDI bootables on two
>>sets of disks rather than just a single set of disks: they couldn't fix
>>it either.
>>
>
>I might be wrong. Linux bootable has both WD7000 and IDE supportorts. I
>just built it aonly tried it with my IDE.

The problem is in the wd probe routine recognizing the drive and there
being no documented way to distibguish between a WD7000, a WD1007, or
some other "wd compatable" controller in the probe.

Does Linux even use probe routines?

In a similar vein, I have successfully distinguished between RLL/MFM/ESDI
and IDE/SCSI controllers.  I would like to be able to distinguish between
RLL/MFM/IDE/ESDI and SCSI controllers.  If this could be done easily and
*before* March, then I could release a WD7000 driver under Julian's SCSI
system.  My driver is WD7000-FASST2 specific; I know there is currently
work underway by other for the WD7000-ASC *and* the WD7000-FASST2.  This
is of more general utility, but they will face the same problems.

As an aside, a method of distinguishing IDE from all other drives in the
probe routine would allow us to ignore all of the drive translation BS
we currently have to worry about.  Anyone out there work for OnTrack?  8-).


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------