On Thu, 16 Dec 2004, Kirk Russell wrote:

> On Thu, 16 Dec 2004, George Harvey wrote:
>
>> With the CMD card installed, I get exactly the same output. If I then
>> remove the TK70 controller, I still get the same output! From this I
>> guess that my CMD card is configured with the same address as the TK70
>> controller. I've had a hunt on the 'net but haven't found any info on
>> jumper settings for the CQD-223 so I'm looking for help to re-jumper it
>> to a non-overlapping address.
>
> http://www.bitsavers.org/pdf/cmd/CQD-220_CQD-223_Nov90.pdf
>
> I used address 772150.

That is the correct address for the first MSCP controller.
The first TMSCP controller should be at 774500.
The second MSCP controller as well as the second TMSCP controller is in 
floating space.

For a machine with one ethernet, two MSCP and two TMSCP, the values are:
DEUNA   174510  (Fixed CSR)
UDA50   172150  (Fixed CSR)
UDA50   160334
TU81    174500  (Fixed CSR)
TU81    160444

For a machine with one ethernet, one MSCP and two TMSCP, the values are:

DEUNA   174510  (Fixed CSR)
UDA50   172150  (Fixed CSR)
TU81    174500  (Fixed CSR)
TU81    160404

Note how the second TMSCP drive moved to another address.

Since the TMSCP drive are last on the system, the configuration for two 
MSCP and one TMSCP are the same as for two MSCP and two TMSCP, except you 
just skip the seconds TMSCP.

But all this is just if you want DEC software to automatically detect the 
controller. Otherwise you're free to use any addresses you feel like.

And NetBSD don't implement the DEC scheme to automatically detect 
hardware.

 	Johnny

Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol