Lines Matching refs:DMA

53   can do pseudo-DMA, then you might want to point these to functions
57   This function is called to set up a DMA transfer.  You must create and
58   return a "DMA handle" in sc->sc_dma_hand which identifies the DMA transfer.
59   The driver will pass you your DMA handle in sc->sc_dma_hand for future
60   operations.  The contents of the DMA handle are immaterial to the MI
61   code - the DMA handle is for your bookkeeping only.  Usually, you
65   buffer.  The Sun driver places an Am9516 UDC control block in the DMA
68   If for some reason you decide not to do DMA for the transfer, make
77   be updated to reflect the portion of the DMA already done.
81   the DMA or stop the DMA.
84   This function frees the current DMA handle.
88   These variables form the active SCSI data pointer.  DMA code must start
89   DMA at the location given, and update the pointer/length in response to
90   DMA operations.
97 Writing your DMA code
100 DMA on a system with protected or virtual memory is always a problem.  Even
104 DMA chains: the DMA is broken up into a list of contiguous segments.  The first
105 segment is submitted to the DMA controller, and when it completes, the second
107 function can do efficiently - if you have a DMA chain, it can quickly load up
111 DVMA: Direct Virtual Memory Access.  In this scheme, DMA requests go through
113 things so the DMA controller sees contiguous data.  In this mode, sc_dma_alloc()
132 The sun3, DMA/Interrupt appears to be working now, but needs testing.