6502/cc65
1
0
Fork 0
mirror of https://github.com/cc65/cc65.git synced 2024-09-25 06:55:13 +00:00
Code Issues Projects Releases Wiki Activity

Made DOS 3.3 IRQ statement more general.

Browse Source 
I recently came across that the question if a driver is compatible with DOS 3.3 isn't about the fact if it actually uses IRQs but if it potentially could use IRQs as the driver kernel pulls in the IRQ handler anyway. This is especially suboptimal in the scenario of statically linked drivers where it is concpetually totally clear at link time they use IRQs or not. Apart from that it might make sense to be able to define on a per-target basis if _any_ of the drivers of a certain class uses IRQs. If that isn't the cases the driver kernel for that driver class for that target could omit IRQ handling too. I'm aware that Uz imagined drivers being loaded which weren't known when the program was linked - but I don't see this.
This commit is contained in:
Oliver Schmidt 2017-06-30 09:50:28 +02:00
parent 26a2d8a5c6
commit 6de78c536f
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/apple2.sgml
View File

@ -435,7 +435,7 @@ BASIC.SYSTEM) there are some limitations for DOS 3.3:
<tag/Interrupts/ <tag/Interrupts/
There's no <tt/interruptor/ support. Any attempt to use it yields the message There's no <tt/interruptor/ support. Any attempt to use it yields the message
'FAILED TO ALLOC INTERRUPT' on program startup. This implicitly means that 'FAILED TO ALLOC INTERRUPT' on program startup. This implicitly means that
<tt/a2.stdmou.mou/ and <tt/a2.ssc.ser/ are not functional as they depend on joystick, mouse and RS232 device drivers are not functional as they depend on
interrupts. interrupts.
</descrip><p> </descrip><p>

2
doc/apple2enh.sgml
View File

@ -436,7 +436,7 @@ BASIC.SYSTEM) there are some limitations for DOS 3.3:
<tag/Interrupts/ <tag/Interrupts/
There's no <tt/interruptor/ support. Any attempt to use it yields the message There's no <tt/interruptor/ support. Any attempt to use it yields the message
'Failed to alloc interrupt' on program startup. This implicitly means that 'Failed to alloc interrupt' on program startup. This implicitly means that
<tt/a2e.stdmou.mou/ and <tt/a2e.ssc.ser/ are not functional as they depend on joystick, mouse and RS232 device drivers are not functional as they depend on
interrupts. interrupts.
</descrip><p> </descrip><p>