Stanford 1822 Interface - Revision history

Jnc: more specific cat; clarify functionality

2021-11-08T14:53:02Z

more specific cat; clarify functionality

← Older revision		Revision as of 14:53, 8 November 2021
Line 1:		Line 1:
	The '''Stanford 1822 Interface''' ~~was~~ an [[~~IMP~~ interface]]~~. (The name is made up~~; ~~examining contemporaneous documentation does not reveal an official or universally~~-~~used name. It was also commonly called the '''SRI~~ 1822 interface~~''', or some variant thereof, since although it was initially created at the Digital Systems Laboratory at Stanford University~~, [[~~SRI International~~\|~~SRI~~]] ~~shortly thereafter took over provision of~~ [[~~printed circuit board\|boards~~]] ~~to other DARPA contractors who wanted them~~.)		The '''Stanford 1822 Interface''' provided an conversion between a [[parallel interface\|parallel port]] and an [[1822 interface]]; the latter could connect to anything that provided a BBN-1822 bit-serial interface, most commonly including [[IMP interface]]s to [[ARPANET]] [[Interface Message Processor\|IMP]]s, but also [[Packet Radio Network]] interfaces.

	~~Technically, it could connect to anything that provided a BBN~~-1822 ~~bit-serial~~ interface, ~~including [[Packet Radio Network]] interfaces~~, ~~not just~~ [[~~ARPANET~~]] [[~~Interface Message Processor~~\|~~IMP~~]]s.		(The name is made up; examining contemporaneous documentation does not reveal an official or universally-used name. It was also commonly called the '''SRI 1822 interface''', or some variant thereof, since although it was initially created at the Digital Systems Laboratory at Stanford University, [[SRI International\|SRI]] shortly thereafter took over provision of [[printed circuit board\|boards]] to other DARPA contractors who wanted them.)

	It was for all machines (mostly [[PDP-11]]s) with either a [[UNIBUS]] (via a [[DR11-C parallel interface]]) or [[QBUS]] (via a [[DRV11 Parallel Line Unit\|DRV11]]). Since it used the [[programmed I/O]] of the underlying DR11-C/DRV11, with an [[interrupt]] for every byte, it was not very suitable for high-throughput applications.		It was for all machines (mostly [[PDP-11]]s) with either a [[UNIBUS]] (via a [[DR11-C parallel interface]]) or [[QBUS]] (via a [[DRV11 Parallel Line Unit\|DRV11]]) (which had identical parallel ports). Since it used the [[programmed I/O]] of the underlying DR11-C/DRV11, with an [[interrupt]] for every byte, it was not very suitable for high-throughput applications.

	It consisted of a [[DEC card form factor\|dual-width]] board with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.		It consisted of a [[DEC card form factor\|dual-width]] board with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.
Line 67:		Line 67:
	* [http://minnie.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/sys/pdpif/if_sri.c if_sri.c]		* [http://minnie.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/sys/pdpif/if_sri.c if_sri.c]

			[[Category: 1822 Interfaces]]
	[[Category: UNIBUS Network Interfaces]]		[[Category: UNIBUS Network Interfaces]]
	[[Category: QBUS Network Interfaces]]		[[Category: QBUS Network Interfaces]]
	~~[[Category: ARPANET]]~~

Larsbrinkhoff: Meow.

2021-11-08T10:15:54Z

Meow.

← Older revision		Revision as of 10:15, 8 November 2021
Line 69:		Line 69:
	[[Category: UNIBUS Network Interfaces]]		[[Category: UNIBUS Network Interfaces]]
	[[Category: QBUS Network Interfaces]]		[[Category: QBUS Network Interfaces]]
			[[Category: ARPANET]]

Jnc: link SRI

2021-10-30T20:15:44Z

link SRI

← Older revision		Revision as of 20:15, 30 October 2021
Line 1:		Line 1:
	The '''Stanford 1822 Interface''' was an [[IMP interface]]. (The name is made up; examining contemporaneous documentation does not reveal an official or universally-used name. It was also commonly called the '''SRI 1822 interface''', or some variant thereof, since although it was initially created at the Digital Systems Laboratory at Stanford University, SRI shortly thereafter took over provision of [[printed circuit board\|boards]] to other DARPA contractors who wanted them.)		The '''Stanford 1822 Interface''' was an [[IMP interface]]. (The name is made up; examining contemporaneous documentation does not reveal an official or universally-used name. It was also commonly called the '''SRI 1822 interface''', or some variant thereof, since although it was initially created at the Digital Systems Laboratory at Stanford University, [[SRI International\|SRI]] shortly thereafter took over provision of [[printed circuit board\|boards]] to other DARPA contractors who wanted them.)

	Technically, it could connect to anything that provided a BBN-1822 bit-serial interface, including [[Packet Radio Network]] interfaces, not just [[ARPANET]] [[Interface Message Processor\|IMP]]s.		Technically, it could connect to anything that provided a BBN-1822 bit-serial interface, including [[Packet Radio Network]] interfaces, not just [[ARPANET]] [[Interface Message Processor\|IMP]]s.

Jnc: Clarify origins; link 2.22 driver

2021-10-21T13:03:43Z

Clarify origins; link 2.22 driver

← Older revision		Revision as of 13:03, 21 October 2021
Line 1:		Line 1:
	The '''Stanford 1822 Interface''' (~~the~~ name is made up; examining contemporaneous documentation does not reveal an official or universally-used name) was ~~an [[IMP~~ interface~~]] (technically~~, it ~~could connect to anything that provided a BBN-1822 bit-serial interface~~, ~~including~~ [[~~Packet Radio Network]] interfaces, not just [[ARPANET]] [[Interface Message Processor~~\|~~IMP~~]]s) ~~for all machines (mostly [[PDP-11]]s) with either [[UNIBUS]] (via a [[DR11-C parallel interface]]) or [[QBUS]] (via a [[DRV11 Parallel Line Unit\|DRV11]]).~~		The '''Stanford 1822 Interface''' was an [[IMP interface]]. (The name is made up; examining contemporaneous documentation does not reveal an official or universally-used name. It was also commonly called the '''SRI 1822 interface''', or some variant thereof, since although it was initially created at the Digital Systems Laboratory at Stanford University, SRI shortly thereafter took over provision of [[printed circuit board\|boards]] to other DARPA contractors who wanted them.)

	~~Since~~ it ~~used the~~ [[~~programmed I/O~~]] ~~of the underlying DR11-C/DRV11~~, ~~with an~~ [[~~interrupt~~]] ~~for every byte, it was not suitable for high-throughput applications~~.		Technically, it could connect to anything that provided a BBN-1822 bit-serial interface, including [[Packet Radio Network]] interfaces, not just [[ARPANET]] [[Interface Message Processor\|IMP]]s.

	It consisted of a [[DEC card form factor\|dual-width]] ~~[[printed circuit~~ board~~\|board]]~~ with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.		It was for all machines (mostly [[PDP-11]]s) with either a [[UNIBUS]] (via a [[DR11-C parallel interface]]) or [[QBUS]] (via a [[DRV11 Parallel Line Unit\|DRV11]]). Since it used the [[programmed I/O]] of the underlying DR11-C/DRV11, with an [[interrupt]] for every byte, it was not very suitable for high-throughput applications.

			It consisted of a [[DEC card form factor\|dual-width]] board with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.

	==Registers==		==Registers==
Line 62:		Line 64:

	* [http://i.stanford.edu/pub/cstr/reports/csl/tr/76/116/CSL-TR-76-116.pdf Asynchronous Serial Interface for Connecting a PDP-11 to the ARPANET (BBN 1822)] (CSL-TR-76-116) - detailed description, including circuit diagrams		* [http://i.stanford.edu/pub/cstr/reports/csl/tr/76/116/CSL-TR-76-116.pdf Asynchronous Serial Interface for Connecting a PDP-11 to the ARPANET (BBN 1822)] (CSL-TR-76-116) - detailed description, including circuit diagrams
			* [http://minnie.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/sys/pdpif/if_sri.h if_sri.h] - 2.11 driver
			* [http://minnie.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/sys/pdpif/if_sri.c if_sri.c]

	[[Category: UNIBUS Network Interfaces]]		[[Category: UNIBUS Network Interfaces]]
	[[Category: QBUS Network Interfaces]]		[[Category: QBUS Network Interfaces]]

Jnc: Avoid redir

2021-10-20T22:58:31Z

Avoid redir

← Older revision		Revision as of 22:58, 20 October 2021
Line 3:		Line 3:
	Since it used the [[programmed I/O]] of the underlying DR11-C/DRV11, with an [[interrupt]] for every byte, it was not suitable for high-throughput applications.		Since it used the [[programmed I/O]] of the underlying DR11-C/DRV11, with an [[interrupt]] for every byte, it was not suitable for high-throughput applications.

	It consisted of a [[DEC card form factor\|dual-width]] [[board]] with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.		It consisted of a [[DEC card form factor\|dual-width]] [[printed circuit board\|board]] with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.

	==Registers==		==Registers==

Jnc: Fairly complete

2021-10-20T22:26:02Z

Fairly complete

New page

The '''Stanford 1822 Interface''' (the name is made up; examining contemporaneous documentation does not reveal an official or universally-used name) was an [[IMP interface]] (technically, it could connect to anything that provided a BBN-1822 bit-serial interface, including [[Packet Radio Network]] interfaces, not just [[ARPANET]] [[Interface Message Processor|IMP]]s) for all machines (mostly [[PDP-11]]s) with either [[UNIBUS]] (via a [[DR11-C parallel interface]]) or [[QBUS]] (via a [[DRV11 Parallel Line Unit|DRV11]]).

Since it used the [[programmed I/O]] of the underlying DR11-C/DRV11, with an [[interrupt]] for every byte, it was not suitable for high-throughput applications.

It consisted of a [[DEC card form factor|dual-width]] [[board]] with three [[Berg connector]] headers on it; two held [[flat cable]]s going to the [[parallel interface]], which connected up to the [[host]] computer's [[input/output]] [[bus]]. A 26-pin Berg header held a cable which led to the standard round Amphenol connector used for the 1822 interface. This board plugged into either the UNIBUS or QBUS [[backplane]], near the parallel interface board.

==Registers==

The device had three control and [[buffer]] [[register]]s, which could be configured to any three sequential [[word]] locations in the I/O page. The first was normally configured to [[address]]es 767770-767774; the second to 767760-767764, the third to 767750-767754, and so on.

{| border=1
! Register !! Abbreviation !! Address
|-
|Control and Status Register || SCSR || 0167770
|-
|Output Buffer Register || SOUTBUF || 0167772
|-
|Input Buffer Register || SINBUF || 0167774
|}

In the register contents (below), bits which are read/write or unused are shown in normal font, those which are read-only are in ''italics''.

"Reading or writing into a register while it is in the process of transferring a byte may cause some bits to become lost and/or out of synchronization. This can waiting until be avoided by either an interrupt or interrupt request (as seen in the status register) is present before accessing the register."

===Status Register (SCSR)===
{{16bit-header}}
| ''RDONE'' || colspan=7 | Unused || ''TDONE'' || TINTE || RINTE || colspan=3 | Unused || RENABL || TENABL
{{16bit-bitout}}

*RDONE - Receive done, interrupt requested
*TDONE - Transmit done, interrupt requested
*TINTE - Transmit Interrupt Enable
*RINTE - Receive Interrupt Enable
*RENABL - Receive data enable
*TENABL - Transmit data enable

===Output Buffer Register (SOUTBUF)===
{{16bit-header}}
| colspan=2 | Unused || HSTCLR || HSTPWR || LSTBYT || colspan=3 | Unused || colspan=8 | OUT7 <-> OUT0
{{16bit-bitout}}

*HSTCLR - Open Host Ready relay
*HSTPWR - Close Host Ready relay
*LSTBYT - Last byte sent

"Either bit 13 OR bit 12 should be set. NOT BOTH."

===Input Buffer Register (SINBUF)===
{{16bit-header}}
| ''IMPODD'' || ''IMPDWN'' || ''HSTMRY'' || ''IMPMRY || ''LSTBYT'' || colspan=3 | Unused || colspan=8 | ''IN7 <-> IN0''
{{16bit-bitout}}

*IMPODD - IMP was down or last byte received
*IMPDWN - "IMP has been down since the last interrupt was serviced"
*HSTMRY - Host relay check, 0 = closed
*IMPMRY - IMP relay check, 0 = closed
*LSTBYT - Last byte received

"The interface will receive bits until either it is full, or it receives the last IMP data bit (LIDB) signal. At this point the interface stops and requests an interrupt. It will not accept any new bits until the present load of bits is read from INBUF. ... Reading the receive register clears the receive buffer making it ready for another byte. Thus program testing of control bits should be done after the contents of the receive register have been moved elsewhere."

==External links==

* [http://i.stanford.edu/pub/cstr/reports/csl/tr/76/116/CSL-TR-76-116.pdf Asynchronous Serial Interface for Connecting a PDP-11 to the ARPANET (BBN 1822)] (CSL-TR-76-116) - detailed description, including circuit diagrams

[[Category: UNIBUS Network Interfaces]]
[[Category: QBUS Network Interfaces]]