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

New blog post about the PDP-10 (and added machine support for the PDP-10 to Jekyll)

Browse source
This commit is contained in:
Jeff Parsons 2017-02-28 19:38:14 -08:00 • committed by Jeff Parsons
commit 1370563e97
3 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

5
_includes/machine-engines.html
View file

@ -5,7 +5,7 @@ in the Front Matter of our Markdown documents, for compatibility with the Jekyll
'id' (eg, "ibm5150")
'name' (eg, "IBM PC (Model 5150) with Monochrome Display")
'type' (eg, "c1p", "pcx86", "pc8080", "pdp11")
'type' (eg, "c1p", "pcx86", "pc8080", "pdp10", "pdp11")
'debugger' (default is false)
'config' (default is "machine.xml")
'template' (default is "machine.xsl")
@ -38,7 +38,7 @@ of our Markdown or XML documents. Examples: 'automount' becomes 'autoMount', 'a
{% capture machine_type %}{{ machine.type | remove:"-dbg" }}{% endcapture %}
{% if machine_type == "c1p" %}
{% assign machine_app = "c1pjs" %}
{% elsif machine_type == "pdp11" %}
{% elsif machine_type == "pdp10" or machine_type == "pdp11" %}
{% assign machine_app = "pdpjs" %}
{% else %}
{% capture machine_app %}{{ machine_type }}{% endcapture %}
@ -116,6 +116,7 @@ of our Markdown or XML documents. Examples: 'automount' becomes 'autoMount', 'a
{% if machine_type == "c1p" %}{% assign array_scripts = site.pcjs.c1p_scripts %}{% endif %}
{% if machine_type == "pcx86" %}{% assign array_scripts = site.pcjs.pcx86_scripts %}{% endif %}
{% if machine_type == "pc8080" %}{% assign array_scripts = site.pcjs.pc8080_scripts %}{% endif %}
{% if machine_type == "pdp10" %}{% assign array_scripts = site.pcjs.pdp10_scripts %}{% endif %}
{% if machine_type == "pdp11" %}{% assign array_scripts = site.pcjs.pdp11_scripts %}{% endif %}
{% for script in array_scripts %}
{% if script != "/modules/shared/lib/nodebug.js" or machine.debug != true and site.pcjs.debug != true %}

2
_includes/machine-styles.html
View file

@ -2,7 +2,7 @@
{% capture machine_type %}{{ machine.type | remove:"-dbg" }}{% endcapture %}
{% if machine_type == "c1p" %}
{% assign machine_app = "c1pjs" %}
{% elsif machine_type == "pdp11" %}
{% elsif machine_type == "pdp10" or machine_type == "pdp11" %}
{% assign machine_app = "pdpjs" %}
{% else %}
{% capture machine_app %}{{ machine_type }}{% endcapture %}

6
_posts/2017-02-28-learning-the-pdp-10.md
View file

@ -12,9 +12,9 @@ Having never used a real DEC PDP-10, I've had a steep learning curve creating a
So far, the only [PDP-10 Hardware Documentation](/pubs/dec/pdp10/) I've read (or rather, skimmed) is the
[PDP-10 System Reference Manual (1968)](http://archive.pcjs.org/pubs/dec/pdp10/ka10/DEC-10-HGAA-D_PDP-10_System_Reference_Manual_May1968.pdf).
To make the process a little less painful, most of my initial development efforts have centered on the built-in PDP-10
Debugger. In addition to the usual disassembler capabilities, I've also included an assembler, so that I can easily enter
instruction sequences like this:
To make it easier to create and run some simple [PDP-10 Opcode Tests](/apps/pdp10/tests/), most of my initial development
efforts have centered on the built-in PDP-10 Debugger. In addition to the usual disassembler capabilities, I've also included
an assembler, so that I can easily enter instruction sequences like this:
a 100;
hrli 1,111111;