diff level1/modules/vtio.asm @ 2966:e84a638d1c16

cohr: Support both COVDG control codes and COHR Esc codes $0B is the only control character that is used by both protocols. I decided to keep the the COVDG command as this protocol is more common. So far I've been able to find only 3 OS9 applications that are using the CoHR drivers, all by Dragon Data: Stylograph, Dynacalc and RMS. Only RMS seems to use the $0B (Home) control code, but it is easy to patch the RMS.trm file to replace $0B with the $01 CoVDG Home command. So this seems like a reasonable sacrifice.
author Ken H. <dragon.atv@gmail.com>
date Mon, 10 Feb 2014 10:10:40 +0200
parents 999159b0e7c0
children adcbab1e0f36 8f5a6fe2d09e
line wrap: on
line diff
--- a/level1/modules/vtio.asm	Mon Feb 10 01:36:20 2014 +0100
+++ b/level1/modules/vtio.asm	Mon Feb 10 10:10:40 2014 +0200
@@ -603,8 +603,12 @@
 Write    ldb   <V.NGChr,u are we in the process of getting parameters?
          bne   PrmHandl   yes, go process
          sta   <V.WrChr,u save character to write
+         ldb   V.51EscSeq,u     * in Escape sequence?
+         bne   GoCo             * yes, send to COHR
          cmpa  #C$SPAC    space or higher?
          bcc   GoCo       yes, normal write
+         cmpa  #$1B             * COHR Escape Code?
+         beq   GoCo
          cmpa  #$1E       escape sequence $1E or $1F?
          bcc   Escape     yes, go process
          cmpa  #$0F       GFX codes?