<url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">,<newline>
<url url="mailto:polluks@sdf.lonestar.org" name="Stefan A. Haubenthal">,<newline>
<url url="mailto:greg.king5@verizon.net" name="Greg King">
-<date>2014-04-02
+<date>2014-04-25
<abstract>
An overview over the Commodore 510 runtime system as it is implemented for the
allow access to hardware located in the address space. Some variables are
structures; accessing the struct fields will access the chip registers.
-<bf>Note:</bf> All I/O chips are located in the system bank (bank 15); and can
+<em/Note:/ All I/O chips are located in the system bank (bank 15); and can
therefore not be accessed like on other platforms. Please use one of the
<tt/peekbsys/, <tt/peekwsys/, <tt/pokebsys/, and <tt/pokewsys/ functions to
access the I/O chips. Direct reads and writes to the structures named below
<author>
<url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">,<newline>
<url url="mailto:greg.king5@verizon.net" name="Greg King">
-<date>2014-04-02
+<date>2014-04-25
<abstract>
An overview over the Commodore 610 runtime system as it is implemented for the
allow access to hardware located in the address space. Some variables are
structures; accessing the struct fields will access the chip registers.
-<bf>Note:</bf> All I/O chips are located in the system bank (bank 15); and can
+<em/Note:/ All I/O chips are located in the system bank (bank 15); and can
therefore not be accessed like on other platforms. Please use one of the
<tt/peekbsys/, <tt/peekwsys/, <tt/pokebsys/, and <tt/pokewsys/ functions to
access the I/O chips. Direct reads and writes to the structures named below