Subject: TMSCP/MSCP question
To: 'port-vax' <port-vax@netbsd.org>
From: Lindgren, Jon <jlindgren@espus.com>
List: port-vax
Date: 06/11/1999 11:11:36
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BEB41C.678EA940
Content-Type: text/plain;
charset="iso-8859-1"
A question about MSCP/TMSCP:
I managed to grab a VAX with a bunch of qbus boards in it, among which was a
TK50 controller and a CMD CDQ-220 (SCSI adapter). I know the TK50 is TMSCP
compliant, and the CMD board says it's MSCP or TMSCP (not both at the same
time) compliant.
So my question is - where exactly does the MSCP protocol fit? Is it a
protocol used to communicate to the controller, or is it a software access
layer which provides a common API to the driver subsystem? If I have any
MSCP compliant board, would it automatically work if NetBSD supports MSCP
boards?
Thanks.
BTW - this machine also has a Dilog DQ256 (SMD controller) and a Dilog DQ152
(1/2 tape controller) which I will most likely not be using. If anyone has
a need and can aide in reconfiguring my system to be sans DQ256 and DQ152,
drop me a line and I'll ship 'em out to ya.
-Jon Lindgren
------_=_NextPart_001_01BEB41C.678EA940
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2232.0">
<TITLE>TMSCP/MSCP question</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>A question about MSCP/TMSCP:</FONT>
</P>
<P><FONT SIZE=3D2>I managed to grab a VAX with a bunch of qbus boards =
in it, among which was a TK50 controller and a CMD CDQ-220 (SCSI =
adapter). I know the TK50 is TMSCP compliant, and the CMD board =
says it's MSCP or TMSCP (not both at the same time) =
compliant.</FONT></P>
<P><FONT SIZE=3D2>So my question is - where exactly does the MSCP =
protocol fit? Is it a protocol used to communicate to the =
controller, or is it a software access layer which provides a common =
API to the driver subsystem? If I have any MSCP compliant board, =
would it automatically work if NetBSD supports MSCP boards?</FONT></P>
<P><FONT SIZE=3D2>Thanks.</FONT>
</P>
<P><FONT SIZE=3D2>BTW - this machine also has a Dilog DQ256 (SMD =
controller) and a Dilog DQ152 (1/2 tape controller) which I will most =
likely not be using. If anyone has a need and can aide in =
reconfiguring my system to be sans DQ256 and DQ152, drop me a line and =
I'll ship 'em out to ya.</FONT></P>
<P><FONT SIZE=3D2> -Jon Lindgren</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BEB41C.678EA940--