@lofty Hmm.
-
@lofty Hmm. I think of a DMA engine's main function being to offload data transfer from someone else so they can go off and do other stuff. So, have A order a transfer from B to C and then A can go and do other stuff. In my case, A wants to transfer from B to itself, and I'm just trying to factor out the machinery of that transfer... But I guess maybe my definition of what a DMA engine is doesn't make sense?...
-
@lofty In software terms what I'm writing is almost just a library function rather than a standalone entity, whereas I think of a DMA engine as a standalone thing. But again maybe the problem here is my definitions? Hmm...
-
big awoo notationreplied to Dave Anderson last edited by
@[email protected] I mean, "A wants to transfer from B to itself" is just - I hate how I don't know any term for this other than "bus mastering". I need to find better language for it.
-
Dave Andersonreplied to big awoo notation last edited by
@lofty Yeah that's sort of the weird thing right? I have a peripheral, that is provided with an arbitrator port on which it can act as bus initiator. The bus itself only supports unbursted request/response, and so I'm making a reusable thing I can slot between the bus port and the peripheral that exposes a burst interface on top of the single transactions... So maybe it's just a "nothing" really, but that's not a great library name