26 Feb
2002
26 Feb
'02
11:14 p.m.
On Wed, Feb 27, 2002 at 12:03:49PM +0100, Johnny Billquist wrote:
:-) I have a bunch of UDA50, both for my PDP-11s, and
for the 8650.
Hmpf. I need the machine for a UDA50. Don't you have a PDP 11/70
handy? ;-)
However, the Ultrix driver is a beautiful beast. When
you declare an MSCP
disk, you don't say where it's located. You just say:
disk ra<x> at mscp drive <y>
Controllers are declared as:
controller uda0 at uba0
controller uq0 at uda0
controller hsc0 at ci0
And then the disks can be either at hsc0 or uq0, and you can move them
without problems.
DSSI is yet another, and so on...
This is also true for NetBSD. From my knowledge
the shebang should
be build like this:
mainbus0 at root
ibus0 at mainbus0
shac0 at ibus0
sii0 at ibus0
dssibus* at shac?
dssibus* at sii?
scs* at dssibus?
mscpbus* at scs?
(SCS, System Communication Services seams to be the protocol that
is spoken on a DSSI bus and that transports MSCP. Got this from
http://www3.sympatico.ca/n.rieck/docs/vax_vms_storage_notes.html)
Maybe HSC instead of SCS, don't know, I hve no manuals...
I can get a KA680 TM from a friend. So what is really needed
is information about DSSI. (I am afraid that this is hard to get.)
True. And also, the NetBSD RA support have some bug in
it, along with
being very much tied to the UDA50/KDA50 right now.
As Ragge already stated, at
least the last objection is not true
anymore. The NetBSD MSCP stuff resides now in sys/dev/mscp what means
that it is machine independent. This also implies proper abstraction
of the MSCP stuff from the underlieing controller hardware.
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/