On Wednesday 28 March 2012, you wrote: [...] > So the first command lists all memories, this should not change unless VICE > is reconfigured to emulate different HWs, or restarted to have other SHM > ids, whatever. > > The second can change, it is used to query memory configuration: [...] > Anyway, it seems to be a bit complex solution, maybe it's even similier and > faster to extend remote monitor protocol for quering information returned > in raw byte stream, it's still true that SHM memory is faster to use, but > since you need to know mapping information etc, I am not sure it will be > faster than, and at least it's quite complex task then ... the problem is that a cartridge may (almost) completely change the memory map based on which address is accessed, so not only would it be quite complex to even get this kind of info from the monitor - you'd also have to query it every time before reading each byte to make sure that you will actually get what the cpu will access. and the vice monitor provides all that functionality already (for the most part atleast, its broken in some areas, as said). -- http://www.hitmen-console.org http://magicdisk.untergrund.net http://www.pokefinder.org http://ftp.pokefinder.org Wanted dead and alive: Schroedinger's cat ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Mar 28 12:52:59 2012
This archive was generated by hypermail 2.1.8 : 2012-03-28 12:53:03 CEST