Hello.
On 08-07-2013 16:38, Sebastian Andrzej Siewior wrote:
not using dmaengine and the network driver (cpsw) which is also using
cppi 3.1 is having its own implementation of the cppi-dma part. So I
think dma enggine implementation is a must here.
Not at all. I'm not familiar with CPSW
On 07/08/2013 02:16 PM, Sergei Shtylyov wrote:
>> not using dmaengine and the network driver (cpsw) which is also using
>> cppi 3.1 is having its own implementation of the cppi-dma part. So I
>> think dma enggine implementation is a must here.
>
>Not at all. I'm not familiar with CPSW but DaVi
On 08.07.2013 12:52, Sebastian Andrzej Siewior wrote:
On 07/07/2013 04:55 PM, Sergei Shtylyov wrote:
Hello.
Hello Sergei,
On 05-07-2013 20:12, Sebastian Andrzej Siewior wrote:
This is a first shot of the cppi41 DMA driver.
Where have you been when I submitted my drivers back in 2009?
On 07/07/2013 04:55 PM, Sergei Shtylyov wrote:
> Hello.
Hello Sergei,
> On 05-07-2013 20:12, Sebastian Andrzej Siewior wrote:
>
>> This is a first shot of the cppi41 DMA driver.
>
>Where have you been when I submitted my drivers back in 2009? :-)
Not here it seems :) There is a driver I go
Hello.
On 05-07-2013 20:12, Sebastian Andrzej Siewior wrote:
This is a first shot of the cppi41 DMA driver.
Where have you been when I submitted my drivers back in 2009? :-)
It is currently used by
a new musb dma-engine implementation. I have to test it somehow.
The state of the cpp41
5 matches
Mail list logo
