Difference between revisions of "UNIBUS parity"
m (typo) |
(→Second version: move parity failure action to KB11-A) |
||
| Line 19: | Line 19: | ||
This version was apparently actually implemented in the [[MM11-E and MM1-F core memories|MM11-F]]; in the ''MM11-F Core Memory Manual'' (DEC-11-HMFA-D, on the subject of parity it says (Appendix A - Parity Option): "The data bits on the bus are called BUS DPB0 and BUS DPB1." There is nothing else on how the two parity bits are used, but the clear implication is that the memory just stores them, and hands them to the master over the bus, for actual use. | This version was apparently actually implemented in the [[MM11-E and MM1-F core memories|MM11-F]]; in the ''MM11-F Core Memory Manual'' (DEC-11-HMFA-D, on the subject of parity it says (Appendix A - Parity Option): "The data bits on the bus are called BUS DPB0 and BUS DPB1." There is nothing else on how the two parity bits are used, but the clear implication is that the memory just stores them, and hands them to the master over the bus, for actual use. | ||
| − | Another apparent 'tombstone' from this era can be found in the ''pdp-11/45 processsor handbook'' (1972 and 1973 editions) where a little-known "Appendix E: Memory Parity", referred to in "2.5.6 Memory Parity", indicates that there are "16 memory status registers ... each one associated with an 8K section of memory". | + | Another apparent 'tombstone' from this era can be found in the ''pdp-11/45 processsor handbook'' (1972 and 1973 editions) where a little-known "Appendix E: Memory Parity", referred to in "2.5.6 Memory Parity", indicates that there are "16 memory status registers ... each one associated with an 8K section of memory". It can control, for each 4k block of that section, whether the memory uses odd or even parity - which would be possible with this version of the UNIBUS parity functionality, and e.g. the MM11-F. It is not known whether these registers were actually implemented in an early version of the -11/45, and if so, exactly what functionality was included. |
[[Category: UNIBUS]] | [[Category: UNIBUS]] | ||
Revision as of 20:29, 22 January 2019
UNIBUS parity has a somewhat complex history. The final UNIBUS spec says parity implementation is wholly within the slave device, and only an error signal is transferred over the bus. From the pdp11 peripherals handbook, 1975 edition (pg. 5-8): "PA and PB are generated by a slave ... [it] negates PA and asserts PB to indicate a parity error ... both negated indicates no parity error. [other combinations] are conditions reserved for future use."
However, originally the UNIBUS parity functionality was planned to be different; sometime around the introduction of the PDP-11/45, DEC changed it, twice.
First version
The first version is described in the unibus interface manual, first edition (DEC-11-HIAA-D).
In there, Table 2-1 has these entries for the PA and PB lines of the UNIBUS: "Parity Available - PA ... Indicates paritied data" and "Parity Bit - PB ... Transmits parity bit". Also, at the bottom of page 2-4, we find "PA indicates that the data being transferred is to use parity, and PB transmits the parity bit. Neither line is used by the KA11 processor."
This first version was not, as far is as known, actually implemented in anything.
Second version
The second version is described in the unibus interface manual. second editioni (DEC-11-HIAB-D).
There, Table 2-1 has these changed entries for PA and PB: "Parity Bit Low - PA ... Transmits parity bit, low byte" and "Parity Bit High - PB ... Transmits parity bit, high byte"; at the top of page 2-5, the text there is wholly different from the version above, including "These lines are used by the MP11 Parity Option in conjunction with parity memories such as the MM11-FP."
This version was apparently actually implemented in the MM11-F; in the MM11-F Core Memory Manual (DEC-11-HMFA-D, on the subject of parity it says (Appendix A - Parity Option): "The data bits on the bus are called BUS DPB0 and BUS DPB1." There is nothing else on how the two parity bits are used, but the clear implication is that the memory just stores them, and hands them to the master over the bus, for actual use.
Another apparent 'tombstone' from this era can be found in the pdp-11/45 processsor handbook (1972 and 1973 editions) where a little-known "Appendix E: Memory Parity", referred to in "2.5.6 Memory Parity", indicates that there are "16 memory status registers ... each one associated with an 8K section of memory". It can control, for each 4k block of that section, whether the memory uses odd or even parity - which would be possible with this version of the UNIBUS parity functionality, and e.g. the MM11-F. It is not known whether these registers were actually implemented in an early version of the -11/45, and if so, exactly what functionality was included.
