Originally Posted by Mrs Beanbag
And another thing i'd suggest we could have really done with is a second copper for initialising the Blitter, because it's quite a task to do it with the normal copper and at the same time get it to do fancy screen effects. Depending on how you implement that, you could create something that can do what a SIMD can do but much more flexible.
Yup, that is also on my list of regrets.
A dedicated Blitter list would have made a world of difference and reduced CPU overhead enormously. It could even have been a simplified Copper:
- waitblitter: pauses and wakes up on Blitter finish.
- pause: waits until woken up by main Copper.
- move: well, move.
No need to wait on a given line: that can be handled by the main Copper who can then drive the Blitterlist based on the video beam.