Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Working on v1.30.6 now

Browse source
This commit is contained in:
Jeff Parsons 2016-12-03 09:04:33 -08:00 • committed by Jeff Parsons
commit aa2aebd89a
238 changed files with 267 additions and 262 deletions
Download patch file Download diff file Expand all files Collapse all files

4
modules/pc8080/lib/serialport.js
View file

@ -479,8 +479,8 @@ SerialPort8080.prototype.initBus = function(cmp, bus, cpu, dbg)
* receiveStatus(pins): called when our control signals have changed; aliased internally to updateStatus(pins)
*
* For now, we're not going to worry about communication in the other direction, because when the target component
* performs its own initConnection(), it will find our receiveData() function, at which point communication in both
* directions should be established.
* performs its own initConnection(), it will find our receiveData() and receiveStatus() functions, at which point
* communication in both directions should be established, and the circle of life complete.
*
* For added robustness, if the target machine initializes much more slowly than we do, and our connection attempt
* fails, that's OK, because when it finally initializes, its initConnection() will call our initConnection();

4
modules/pcx86/lib/serialport.js
View file

@ -477,8 +477,8 @@ SerialPort.prototype.initBus = function(cmp, bus, cpu, dbg)
* receiveStatus(pins): called when our control signals have changed; aliased internally to updateStatus(pins)
*
* For now, we're not going to worry about communication in the other direction, because when the target component
* performs its own initConnection(), it will find our receiveData() function, at which point communication in both
* directions should be established.
* performs its own initConnection(), it will find our receiveData() and receiveStatus() functions, at which point
* communication in both directions should be established, and the circle of life complete.
*
* For added robustness, if the target machine initializes much more slowly than we do, and our connection attempt
* fails, that's OK, because when it finally initializes, its initConnection() will call our initConnection();

4
modules/pdp11/lib/serialport.js
View file

@ -354,8 +354,8 @@ SerialPortPDP11.prototype.initBus = function(cmp, bus, cpu, dbg)
* receiveStatus(pins): called when our control signals have changed; aliased internally to updateStatus(pins)
*
* For now, we're not going to worry about communication in the other direction, because when the target component
* performs its own initConnection(), it will find our receiveData() function, at which point communication in both
* directions should be established.
* performs its own initConnection(), it will find our receiveData() and receiveStatus() functions, at which point
* communication in both directions should be established, and the circle of life complete.
*
* For added robustness, if the target machine initializes much more slowly than we do, and our connection attempt
* fails, that's OK, because when it finally initializes, its initConnection() will call our initConnection();