Name the VICE test programs, not VICE's emulation, as the source of the VIC-II timing rules - #356
Merged
Conversation
…he VIC-II timing rules
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewords two older mentions that attributed VIC-II timing to VICE itself:
docs/systems/c64/libraries.md: the points within a cycle at which register changes reach the output are described as the chip's observed behaviour as VICE's VICII test programs show it, whose reference pictures the output is checked against.Vic2BusStallTests.cs: the 6567R8 sprite fetch cycles are stated as chip behaviour, matching the comment inVic2BusStalls.cs.Documentation and comment only; no behaviour change. Strict docs build passes;
Vic2BusStallTestspass (32/32).