diff options
author | 2014-09-17 20:50:32 +0000 | |
---|---|---|
committer | 2014-09-17 20:50:32 +0000 | |
commit | f5570dc9c61adc03e008c6e23f911ea9bd1f0366 (patch) | |
tree | 40d7a0c39fc600776bcf1402400054979ea2ff7f /docs | |
parent | c61142c217aaf03f7c319a2a56a987516d63d066 (diff) |
If we were documented, we'd be dangerous (nw)
Diffstat (limited to 'docs')
-rw-r--r-- | docs/m6502.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/m6502.txt b/docs/m6502.txt index 56e761ebf5a..2a45a3e172e 100644 --- a/docs/m6502.txt +++ b/docs/m6502.txt @@ -95,13 +95,13 @@ everything goes through normal memory-map read/write calls. The state of the sync line is given by the cpu method get_sync(), making implementing the decryption in the handler possible. -In a final addition, the cpu method get_cycle() gives the current time -in cycles since the start of the machine from the point of view of the -cpu. Or, in other words, what is usually called the cycle number for -the cpu when somebody talks about bus contention or wait states. The -call is designed to be fast (no system-wide sync, usually no call to -machine.time()) and is precise. Cycle number for every access is -exact at the sub-instruction level. +Also, as for every executable device, the cpu method total_cycles() +gives the current time in cycles since the start of the machine from +the point of view of the cpu. Or, in other words, what is usually +called the cycle number for the cpu when somebody talks about bus +contention or wait states. The call is designed to be fast (no +system-wide sync, no call to machine.time()) and is precise. Cycle +number for every access is exact at the sub-instruction level. The 4510 special nomap line is accessible through get_nomap(). |