Hi,
I wonder, does anyone here know anything about the KDA50? I've solved my RA72
problem (as it turns out, if there is no control panel connected, the drive
assumes normal operation, i.e., spin up, go on-line, enable port A, no write
protect, and the unit number between 0 and 7 is set by the switches on the
right side of the drive), but now I have a different problem: I can't get UNIX
(4.3BSD-Quasijarus of course) to recognize the KDA50, although it worked fine
on my Webster ESDI controller back in Ohio, and others have also reported
successfully booting it on different controllers. By inserting a few debugging
printouts in the uda driver, I have determined that it fails the udaprobe(). I
know very little about UDA50/KDA50 registers, so I may be wrong, but it looks
to me that the code is trying to do the following. It diddles the controller
registers to make it start the initialization. Then apparently it expects the
controller to interrupt and set some status bits in some register. However,
because of Q-bus's odd interrupt protocol and the need to determine the IPL of
the controller, the procedure is done non-trivially. First it does an spl6(),
disabling all interrupts except BR7 (which these controllers apparently don't
use). Then it does the register diddling and testing with these interrupts
disabled. It allows the CPU to field the interrupt only when the register bits
indicate that the operation has been performed and the interrupt has been
posted. Apparently the assumption is that the controller will post the
interrupt and then set the right bits in the right registers without waiting
for the CPU to field the interrupt. Also apparently the KDA50 is different and
doesn't set those bits until the interrupt is fielded, breaking this code.
So my questions to the folks are: First, is my understanding of the situation
correct? Second, what can be done about it? I guess as a temporary solution I
can remove this problematic IPL autodetection code and hard-code the IPL of my
KDA50, but what is it? Is the IPL set with switches on the KDA50 or how? And
what do the KDA50 switches do in the first place? Does anyone know? TIA.
--
Michael Sokolov
Special Agent
International Free Computing Task Force
ARPA Internet SMTP mail: msokolov(a)meson.jpsystems.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA00399
for pups-liszt; Thu, 2 Sep 1999 15:09:20 +1000 (EST)
From Kirk McKusick
<mckusick(a)flamingo.McKusick.COM> Thu Sep 2 09:44:29 1999
Received: from
knecht.sendmail.org (
knecht.sendmail.org [209.31.233.160])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id PAA00395
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 2 Sep 1999 15:09:13 +1000 (EST)
Received: from
flamingo.McKusick.COM (root(a)flamingo.mckusick.com [209.31.233.178])
by
knecht.sendmail.org (8.9.3/8.9.3) with ESMTP id RAA20755;
Wed, 1 Sep 1999 17:54:11 -0700 (PDT)
Received: from
flamingo.McKusick.COM (mckusick(a)localhost.concentric.net [127.0.0.1])
by
flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id QAA29309;
Wed, 1 Sep 1999 16:44:35 -0700 (PDT)
Message-Id: <199909012344.QAA29309(a)flamingo.McKusick.COM>
To: wkt(a)cs.adfa.edu.au
Subject: Re: V7M
cc: pups(a)minnie.cs.adfa.edu.au
In-reply-to: Your message of "Mon, 09 Aug 1999 09:41:23 +1000."
<199908082341.JAA83043(a)henry.cs.adfa.edu.au>
Date: Wed, 01 Sep 1999 16:44:29 -0700
From: Kirk McKusick <mckusick(a)flamingo.McKusick.COM>
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
My recollection is that V7M stood for V7-mini. It was a
striped down version of V7 that was designed to run on
the very low-end PDP-11's (like the 11/20).
Kirk McKusick
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA00533
for pups-liszt; Thu, 2 Sep 1999 15:27:01 +1000 (EST)
From "Steven M. Schultz"
<sms(a)moe.2bsd.com> Thu Sep 2 15:25:35 1999
Received: from
moe.2bsd.com
(0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id PAA00528
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 2 Sep 1999 15:26:54 +1000 (EST)
Received: (from sms@localhost)
by
moe.2bsd.com (8.9.0/8.9.0) id WAA04996
for pups(a)minnie.cs.adfa.edu.au; Wed, 1 Sep 1999 22:25:35 -0700 (PDT)
Date: Wed, 1 Sep 1999 22:25:35 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199909020525.WAA04996(a)moe.2bsd.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: V7M
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
From: Kirk McKusick
<mckusick(a)flamingo.McKusick.COM>
My recollection is that V7M stood for V7-mini. It was a
striped down version of V7 that was designed to run on
the very low-end PDP-11's (like the 11/20).
Hmmm, interesting. My memories dredge up the 'M' as meaning
"Modified". Don't recall it ever being touted as 11/20 capable
56kb, no MMU would be a wee bit too mini I'd think - was there ever
a V7 that could run without an MMU? If there was I've completely
forgotten about it.
Steven Schultz
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA00770
for pups-liszt; Thu, 2 Sep 1999 15:59:45 +1000 (EST)