|Re: [hatari-devel] Most wanted debugger/profiler feature or convenience? (Blitter/LED)|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
On torstai 11 huhtikuu 2013, Eero Tamminen wrote:
> > > > Another useful thing for blitter problems - having the debugger
> > > > notice/alert when the blitter HW registers (other than busy bit)
> > > > are modified
> Do you mean changes in any of the registers, or or just the control
> Easiest would be to take a copy of the register values when blitter
> starts working and checking when blitter stops working whether any
> of them had changed. This would of course need to disregard any
> regs that change while blitter works:
> lines, words, src and dst adress and halftone bits in control register.
Probably best would be to add separate trace level to blitter for
It would be good to have common part in name for these kind of "coding
bug detection" messages, maybe a "_bug" postix?
I.e. trace option name for such blitter messages would be "blitter_bug"
("blitter" is used to enable control register tracing)...
> > > > while the blitter is running.
> And "running" means the time from setting the "busy" bit, until blitter
> clears it (after it has processed all lines)?
> Attached is a patch to do that when blitter tracing is enabled. It also
> adds "info blitter" command as that was only couple of lines more code.
I'll make the output of "info blitter" a bit more condensed and commit
> Apparently Paradox's Pacemaker demo changes blitter skew register while
> Blitter is still working, both at the start and end of the whole demo.