Port-vax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Address of second TMSCP controller



David that is awfully nice of you, but I had no idea it would be necessary to rebuild!  It is 9.1. Obviously I am not going to be able to do that on the MVII since my wife would complain about the noise if it was left running for 11 nights! (Assuming 1 VUP :-) )

I really don't want to put you to the trouble - the TK70 and my other drive, a TK50, are both borked anyway,. so maybe I should just put the Dilog at the main CSR.

Right now it is at 160404/160406 but I can change it pretty easily.

cheers,

Nigel



Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype:  TILBURY2591 nw.johnson%ieee.org@localhost



On 2021-01-26 3:08 p.m., David Brownlee wrote:
Hi Nigel

This is building a NetBSD kernel from its config, which is typically
in sys/arch/vax/config/GENERIC in a NetBSD source tree.

If you can confirm what NetBSD version you're running I'd be happy to
drop a pre-built one back, and/or help you get setup to build.

You should be able to download NetBSD source,
(https://www.netbsd.org/docs/guide/en/chap-fetch.html - or pull from
github mirror) then on a faster box (BSD/Linux) run

./build.sh -U -m vax tools kernel=GENERIC

David


On Tue, 26 Jan 2021 at 20:02, Nigel Johnson <nw.johnson%ieee.org@localhost> wrote:
I'd love to try this, but have been searching both the winchester and the manuals for the last two hours to try and find this config file!  Can anybody tell me where it i?

thanks

Nigel


Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype:  TILBURY2591 nw.johnson%ieee.org@localhost



On 2021-01-26 12:32 p.m., Johnny Billquist wrote:

On 2021-01-26 16:56, David Brownlee wrote:

On Tue, 26 Jan 2021 at 15:20, Anders Magnusson <ragge%tethuvudet.se@localhost> wrote:


Den 2021-01-26 kl. 16:05, skrev Paul Koning:


  I imagine you could add a second mtc line to your config at whatever
address you put your Dilog card at.  ISTR that DEC had a bunch of rules
for such addresses - the phrase "floating CSR space" comes to mind -

Right.  In the DEC rules, this is a "first unit fixed, rest float"
device, just like the MSCP disk controllers.  The float CSR rank is 30.
Does NetBSD do the floating CSR address algorithm?  If not, yes, just
pick some address and tell the OS what it is.

No, NetBSD do obey the floating CSR spec.
This code is actually from 4BSD which didn't either.


Is it just a matter of adding mtc* lines to the config for the 2nd and
subsequent floating address - or is there some risk of false positives
if a different device is at that address?


To do it properly, you cannot at all use the config lines as NetBSD have it today.
But yes, you can add additional lines for mtc with other CSRs. But there are limits to how well devices can be probed, so if you have something else on that address, it might be a false positive indeed.

The whole point of the DEC defined floating CSR configuration rules was in order to reliably identify each controller type. But it requires a rather more intelligent contextual probing of the address space instead of the NetBSD rules based matching system.

  Johnny



Home | Main Index | Thread Index | Old Index