Number: 1776

Date:  9-Aug-84 12':34':19

Submitter: Sannella.PA

Source: masinter.pa

Subject: Need support from Lisp to access the new parallel port

Assigned To: 

Attn: 

Status: Fixed

In/By: Harmony

Problem Type: Documentation

Impact: Serious

Difficulty: 

Frequency: 

Priority: Hopefully

System: Language Support

Subsystem: Microcode

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Sannella.PA" "28-Aug-84 11':36':30" Attn': System':(Communications->Language% Support) Subsystem':(Other->Microcode) Description':]'
["Sannella.PA" "25-Sep-84 12':04':45" Attn': Status':(Open->Fixed) In/By': Description':]

Description: '
Date': 25 Jun 84 18':19 PDT'
From': masinter.pa'
Subject': scheduling development tasks to complete announced products'
To': Sheil'
cc': LispSupport, Purcell, vanMelle'
'
AR#1':'
We need support from Lisp to access the new parallel port. I suggest an equivalent READPRINTERPORT and WRITEPRINTERPORT. I don''t like it that the cable is different, unless we also supply an adapter cable. I would prefer to manufacture as many cables as there are new CP boards and just install it as part of the field upgrade. So':'
'
Lisp AR is to create the microcode and document it; action item for manufacturing and field support is to cut in the cable that brings it out to the back of the machine and to produce the adapters.'
'
-----'
'
Date': 22 AUG 84 22':02 PDT'
From': MASINTER.PA'
Subject': AR#1776 parallel port'
To':   lispsupport'
cc':   charnley, purcell, herring'
'
This is DLion microcode, not communication. Should be attn to charnley, purcell, herring. I think we want READPRINTERPORT WRITEPRINTERPORT same args.'
'
Add to AR that we need specs for the cable, documentation on how to use port, too.'
'
-----'
'
Date': 16 Sep 84 22':19 PDT'
From': herring.pa'
Subject': PRINTERPORT non-Library-package'
To': Sannella'
cc': herring.pa'
'
We were going to have a Library package for Harmony for using the DandyLion parallel port (Dolphin-like).  However, integration has proceeded to the point that there is no longer any software "in the package"!  Where shall I put the documentation ({eris}<herring>printerport.tedit) ??'
'
(The two functions referred to in the documentation are identical to the opcodes for the Dolphin printer port.  So they have been subsumed there.  At that point I doubled up the documentation to cover the Dolphin as well.  The Dolphin hardware manual has some more stuff, that would not be of much use to anyone wanting to use the printer port for a "user device".)'
'
-----'
'
currently, doc. is on {eris}<Herring>harmony>Printerport.tedit'
'
'


Workaround: 

Test Case: 

Edit-By: Sannella.PA

Edit-Date: 25-Sep-84 12':04':46