From: Groepaz (groepaz_at_gmx.net)
Date: 2003-05-03 16:41:51
On Saturday 03 May 2003 13:03, karri wrote: > The memories available are a 128 byte EEPROM and a ROM cart space that can > be equipped by ROM, SRAM or Flash memory. > > This brings up a need for very different models for the file I/O. > In an EEPROM I need just a byte to address the whole chip. In an Intel > StrataFlash I can access 1MB of R/W memory so 16 bit is not enough... > > Is this treated by having "loadable modules" somehow? Or should I just use > a huge bunch of IFDEF's and write just one module? > > The point is that you have to choose your hardware first and then you need > certain support routines. There is no sense to have dynamically loadable > modules for EEPROM support if there in no EEPROM on the board. i have a simelar problem with the NES (there exist hundreds of so called "mappers" for the NES). however, ifdefs are BAD imho.... since they would be in the library and it would require the user to recompile the library... i would probably go for "loadable" modules, but dont "load" them (whatever faked thing one could come up with) but link one of them statically.... this is a little more effort at first, but probably the easiest solution for the enduser. gpz ---------------------------------------------------------------------- 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 : 2003-05-03 16:45:30 CEST