From: Oliver Schmidt Date: Tue, 13 Nov 2018 17:31:53 +0000 (+0100) Subject: Added target docs on the clock_... functions. X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=4b42d6ad54a9e8d3adc801fca7b19092396a6c42;p=cc65 Added target docs on the clock_... functions. --- diff --git a/doc/apple2.sgml b/doc/apple2.sgml index aa3089957..f61a8a68e 100644 --- a/doc/apple2.sgml +++ b/doc/apple2.sgml @@ -469,25 +469,47 @@ BASIC.SYSTEM) there are some limitations for DOS 3.3: Direct console I/O

- - -

+The Apple ][ has no color text mode. Therefore the functions +Random number generator

- - -

+The random number seed is generated from the time the program waits for user input. +Therefore it is necessary to wait for at least one user keypress either via Standard +I/O or via Direct console I/O before initializing the pseudo random number generator. + + +Realtime clock

+ +There are several types of realtime clocks. It's not desirable to have specific code +for all of them. As ProDOS 8 supports file timestamps, realtime clock owners usually +use ProDOS 8 drivers for their realtime clock. Those drivers read the realtime clock +and write the result to the date/time location in RAM ($BF90 to $BF93). +ProDOS 8 reads the date/time from that RAM location. If there's no realtime clock the +RAM location keeps containing zeros. ProDOS 8 uses those zeros as timestamps and the +files show up in a directory as Direct console I/O

- - -

+The enhanced Apple //e has no color text mode. Therefore the functions +Random number generator

- - -

+The random number seed is generated from the time the program waits for user input. +Therefore it is necessary to wait for at least one user keypress either via Standard +I/O or via Direct console I/O before initializing the pseudo random number generator. + + +Realtime clock

+ +There are several types of realtime clocks. It's not desirable to have specific code +for all of them. As ProDOS 8 supports file timestamps, realtime clock owners usually +use ProDOS 8 drivers for their realtime clock. Those drivers read the realtime clock +and write the result to the date/time location in RAM ($BF90 to $BF93). +ProDOS 8 reads the date/time from that RAM location. If there's no realtime clock the +RAM location keeps containing zeros. ProDOS 8 uses those zeros as timestamps and the +files show up in a directory as Limitations

+Realtime clock

+ +The realtime clock functions use the CIA1 TOD clock. As that clock only stores +the time but not the date, the date set by Other hints

diff --git a/doc/c64.sgml b/doc/c64.sgml index 328a77ab6..8c910666c 100644 --- a/doc/c64.sgml +++ b/doc/c64.sgml @@ -418,6 +418,13 @@ The default drivers, Limitations

+Realtime clock

+ +The realtime clock functions use the CIA1 TOD clock. As that clock only stores +the time but not the date, the date set by Other hints

diff --git a/doc/cbm510.sgml b/doc/cbm510.sgml index 5c7c0f767..5df8f06f6 100644 --- a/doc/cbm510.sgml +++ b/doc/cbm510.sgml @@ -242,6 +242,13 @@ The default drivers, Limitations

+Realtime clock

+ +The realtime clock functions use the CIA1 TOD clock. As that clock only stores +the time but not the date, the date set by Kernal and hardware access

Since the program runs in bank 0, and the kernal and all I/O chips are located diff --git a/doc/cbm610.sgml b/doc/cbm610.sgml index c1faefd51..49313c4d2 100644 --- a/doc/cbm610.sgml +++ b/doc/cbm610.sgml @@ -224,6 +224,13 @@ No mouse drivers are currently available for the Commodore 610. Limitations

+Realtime clock

+ +The realtime clock functions use the CIA1 TOD clock. As that clock only stores +the time but not the date, the date set by Kernal and hardware access

Since the program runs in bank 1, and the kernal and all I/O chips are located