From: Anders Magnusson <ragge@ludd.luth.se>
Message-Id: <199909020805.KAA11504@father.ludd.luth.se>
Subject: Re: KDA50 woes
To: quasijarus@minnie.cs.adfa.edu.au
Date: Thu, 2 Sep 1999 10:05:23 +0200 (MET DST)
Cc: pups@minnie.cs.adfa.edu.au, quasijarus@minnie.cs.adfa.edu.au
In-Reply-To: <9909020115.AA00610@meson.jpsystems.com> from Michael Sokolov at "Sep 1, 99 08:15:23 pm"
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups@minnie.cs.adfa.edu.au
Precedence: bulk

> Hi,
> 
> I wonder, does anyone here know anything about the KDA50? I've solved my RA72
>
Well, something I think... :-)

[...]
> 
> 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.
> 
The IPL autodetect code has seemed to me as unneccessary. You know that
the KDA50 will always interrupt at spl5, so you can hard-code it in
the interrupt driver and nuke the autodetect code. The same with the 
other drivers that can be on Qbus:

	if (uh->uh_type == QBA)
		spl5();

-- Ragge