chris
f809b9b7ea
With ARNITECH_BLADE the screen editor, the keyboard matrix scan, and the VIC-II set-up are left out, and devices 3 and 0 are the Terminal Card the Arnitech controller finds by its type, $04. CHROUT writes each byte to its Output, or to its Literal while quote or insert mode is on, keeping QTSW and INSRT as the screen editor does. CHRIN marks where input starts, echoes the keys typed, and on RETURN has the Card take the logical line under the cursor and reads it back. SCNKEY moves the Card's keys into the keyboard buffer up to XMAX, UDTIM sets STKEY from its RUN/STOP, SCREEN answers 80x25, PLOT moves and reads its cursor, and CINT resets it and puts the native-mode vectors in place. With no Terminal Card, bytes printed go nowhere and no key comes.
30 lines
623 B
ArmAsm
30 lines
623 B
ArmAsm
;; #LAYOUT# STD * #TAKE
|
|
;; #LAYOUT# * * #IGNORE
|
|
|
|
; Not on a Blade, whose Terminal Card holds the screen editor (src/kernal/arnitech)
|
|
!ifndef CONFIG_ARNITECH_BLADE {
|
|
|
|
;
|
|
; Well-known Kernal routine, described in:
|
|
;
|
|
; - [CM64] Computes Mapping the Commodore 64 - $EA24
|
|
;
|
|
; Sets USER to the colour RAM location of PNT's screen line. Screen RAM starts on a
|
|
; kilobyte boundary, as the VIC-II fetches it, so the line's place within its kilobyte
|
|
; is its place in the colour RAM.
|
|
;
|
|
|
|
|
|
screen_calculate_USER:
|
|
|
|
lda PNT+0
|
|
sta USER+0
|
|
lda PNT+1
|
|
and #$03
|
|
ora #>COLOR_RAM
|
|
sta USER+1
|
|
|
|
rts
|
|
|
|
} ; CONFIG_ARNITECH_BLADE
|