On Fri, Feb 14, 2014 at 3:32 PM, Siva Yerramreddy
wrote:
> When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
> engine, dmatest detected "dma0chan3-copy5: result #8096161:completion busy
> status with src_off=0x0 dst_off=0x0 len=0x40 (0)". This is caused by reading
>
On Fri, Feb 14, 2014 at 3:32 PM, Siva Yerramreddy
siva.krishna.kumar.reddy.yerramre...@intel.com wrote:
When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
engine, dmatest detected dma0chan3-copy5: result #8096161:completion busy
status with src_off=0x0 dst_off=0x0
On Fri, Feb 14, 2014 at 03:32:57PM -0800, Siva Yerramreddy wrote:
> When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
> engine, dmatest detected "dma0chan3-copy5: result #8096161:completion busy
> status with src_off=0x0 dst_off=0x0 len=0x40 (0)". This is caused by
On Fri, Feb 14, 2014 at 03:32:57PM -0800, Siva Yerramreddy wrote:
When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
engine, dmatest detected dma0chan3-copy5: result #8096161:completion busy
status with src_off=0x0 dst_off=0x0 len=0x40 (0). This is caused by reading
When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
engine, dmatest detected "dma0chan3-copy5: result #8096161:completion busy
status with src_off=0x0 dst_off=0x0 len=0x40 (0)". This is caused by reading
the used cookie before the completed cookie in dma_cookie_status(),
When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
engine, dmatest detected dma0chan3-copy5: result #8096161:completion busy
status with src_off=0x0 dst_off=0x0 len=0x40 (0). This is caused by reading
the used cookie before the completed cookie in dma_cookie_status(),
6 matches
Mail list logo