SECOND/TKSA compatibility fix

This commit is contained in:
FeralChild64 committed 2019-11-07 17:23:27 +01:00
1 parent 7453771219
commit 2e9a0b1610
5 files changed
+15 -15

No files matched your search

+6 -7
View File
@@ -14,13 +14,12 @@ SECOND:
#if CONFIG_IEC
// Due to OPEN/CLOSE/TKSA/SECOND command encoding (see https://www.pagetable.com/?p=1031),
// allowed channels are 0-15; report error if out of range
cmp #$10
bcc !+
jmp kernalerror_DEVICE_NOT_FOUND // XXX find a better error message for wrong channel (create new one?)
!:
ora #$60
// Due to OPEN/CLOSE/TKSA/SECOND command encoding, allowed channels are 0-15; it is the caller
// responsibility, hovewer, to provide value ORed with $60
// - https://www.lemon64.com/forum/viewtopic.php?t=57694&sid=531ba3592bcffadef2ac8b9162f2e529
// - https://www.pagetable.com/?p=1031 (Kernal API description)
// XXX consider checking whether value is in range (contrary to original ROM implementation)
jmp common_open_close_unlsn_second