From: Greg King (gngking_at_erols.com)
Date: 2002-11-23 19:35:22
-----Original Message----- From: Ullrich von Bassewitz Date: Friday, November 22, 2002 01:18 PM > > On Fri, Nov 22, 2002 at 01:05:11PM -0500, Greg King wrote: > > When I read the IDE64 Hard-disk Controller's documents, I realized that the > > C64 target, also, needs to protect interrupt-handlers (for the mouse, too). > > I don't see why the C64 would need that. Sometimes, the IDE64 banks ROM-images onto the $8000-$BFFF region. It doesn't stop interrupts during that time, therefore we must not have any active interrupt-handlers sitting in that range while we do I/O. > > I've started to do exactly what you suggested. There will be an > additional segment named LOWCODE that follows startup, and should, therefore, > always be in non-banked memory (provided no one packs kilobytes of code into > this segment). Everyone should agree that LOWCODE will hold only the minimum amount of code and data that absolutely needs to be "visible" all of the time. Data and code that can afford to be banked out of sight, or coverred by ROMs, should go into other segments. ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2002-11-23 19:39:55 CET