Comments on: DMA vs ARM9 – fight!

By: cearn

cearn — Wed, 18 Nov 2009 14:00:46 +0000

ChaimLeib, yes it should. C&P error, it happens sometimes :(

For those interested, also read ant’s post regarding my ‘safe’ functions. There could be more at play here than I initially thought.

By: ChaimLeib

ChaimLeib — Wed, 18 Nov 2009 10:35:07 +0000

In section 4.5, shouldn't DC_FlushRange(...); be replaced with DC_InvalidateRange;(...) ?

By: ant.simianzombie.com » Woopsi Updates and DMA Mayhem

ant.simianzombie.com » Woopsi Updates and DMA Mayhem — Sat, 14 Nov 2009 18:40:27 +0000

[...] Woopsi was only performing the first of these three actions, and it wasn’t doing so consistently. The result of this is that, no matter what I do, the last 4 pixels of every bitmap I attempt to blit to another bitmap are not drawn. Some research led me to two useful sources: a GBADEV topic and a blog post from cearn on coranac.com. [...]

By: link run « console-dev.de

link run « console-dev.de — Mon, 01 Jun 2009 10:18:37 +0000

[...] “cearn” Vijn has written an article called DMA vs ARM9 – fight! He explains what problems you can run into when using DMA and gives a brief introduction to cache. [...]

By: sylvainulg

sylvainulg — Fri, 29 May 2009 11:37:09 +0000

Thanks for the tip. I already had noticed some oddities with DMA transfers a while ago, but i re-parsed my code after reading your document and fixed a couple of other errors (such as flushing target after a dmacopy rather than invalidating it) in my project.

Live long and prosper.