Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!wx.gtegsc.com!wlbr!sms From: sms@WLV.IIPO.GTEGSC.COM (Steven M. Schultz) Subject: Re: KFQSA Driver for BSD 4.3 Unix Message-ID: <1993Jun9.171307.26570@wlbr.iipo.gtegsc.com> Sender: news@wlbr.iipo.gtegsc.com (news) Nntp-Posting-Host: wlv.iipo.gtegsc.com Organization: GTE Government Systems References: <1993Jun8.180313.14890@mintaka.lcs.mit.edu> <1993Jun8.185311.6191@spcvxb.spc.edu> Date: Wed, 9 Jun 93 17:13:07 GMT Lines: 28 In article <1993Jun8.185311.6191@spcvxb.spc.edu> terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes: > It should work, though you may need to make some minor driver changes. >The KFQSA looks like multiple UDA50/KDA50/etc. Be sure that the drives are I double checked last night, both a 4.3Reno system (gave me an excuse to fire up the uVax) and a 4.3 system. No changes would be needed to the driver itself. Just add a bunch of "uda? ..." lines to the kernel config file. > The changes you'd need would be to handle the controller model that you >receive when the driver goes "what are you" to the KFQSA. Each MSCP control- Na, the uda driver pays that part of the 'id' absolutely no mind at all. Where you would run into possible problems is in the drive type identification - all the driver looks at (in straight 4.3) is the '81', '80', '82' part of the media id - it can't tell the difference between an RA72 and an RF72 (for example). The other problem(s) that would be encountered are: 1) the 4.3 driver has built in tables that only go as far as the RA81, you'll have to have the system up and running and add in additional tables for RFxx drives. 2) there are a few "oop"es in the 4.3Reno compatibility table (it wouldn't recognize a genuine RD53 as an RD53). Steven Schultz sms@wlv.iipo.gtegsc.com