1
0
mirror of https://github.com/TomHarte/CLK.git synced 2024-11-19 23:32:28 +00:00
CLK/OSBindings/Mac/Clock SignalTests/Amiga Blitter Tests
Ryan Carsten Schmidt d811501421 Compatibility fixes in Markdown files.
Improve compatibility with some Markdown readers like MacDown by adding
blank lines before lists. Blank lines around headers were added for
consistency. One header level was fixed. One code block was fixed.
2024-01-27 13:24:35 -06:00
..
Addams Family Intro.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
clock.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
gadget toggle.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
icon highlight.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
inclusive fills.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
kickstart13 boot logo.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
RAM disk open.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
README.md Compatibility fixes in Markdown files. 2024-01-27 13:24:35 -06:00
sector decode.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
Spindizzy Worlds.json.gz Remove 'Faulty peek' JSON breakages. 2022-08-08 15:22:18 -04:00
spots.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
window drag.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00
window resize.json.gz Compress all Blitter logs. 2022-08-07 21:55:33 -04:00

Amiga Blitter Tests

These tests record register writes and subsequent memory accesses by the Amiga Blitter over a variety of test cases. It is believed that they test all functionality other than stippled lines.

They were generated using a slightly-inaccurate public domain model of the chip rather than from the real thing. In particular:

  • these tests record the output as though the Blitter weren't pipelined — assuming all channels enabled, it always reads via A, then B, then C, then writes via D. The real Blitter performs two cycles of reads before its first write, and adds a final write with no additional reads; and
  • the tests do not record which pointer is used for a write target and therefore do not observe that the Blitter will use pointer C as a write destination for the first pixel of a line.