> -Original Message-
> From: arndbergm...@gmail.com [mailto:arndbergm...@gmail.com] On Behalf Of
> Arnd Bergmann
> Subject: Re: [PATCH] dpaa_eth: use correct device for DMA mapping API
>
> On Tue, Jul 11, 2017 at 10:50 AM, Madalin-cristian Bucur
> wrote:
>
>
On Tue, Jul 11, 2017 at 10:50 AM, Madalin-cristian Bucur
wrote:
> Hi Arnd,
>
> Thanks for looking into this, I've tested your fix, it seems to need more
> work:
>
> [0.894968] platform: DMA map failed
> [0.898627] platform: DMA map failed
> [0.902288] platform: DMA map failed
> [
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Monday, July 10, 2017 6:14 PM
> Subject: [PATCH] dpaa_eth: use correct device for DMA mapping API
>
> Geert Uytterhoeven ran into a build error without CONFIG_HAS_DMA,
> as a result of the drive
On 10/07/17 16:14, Arnd Bergmann wrote:
> Geert Uytterhoeven ran into a build error without CONFIG_HAS_DMA,
> as a result of the driver calling set_dma_ops(). While we can
> fix the build error in the dma-mapping implementation, there is
> another problem in this driver:
>
> The configuration for
Hi Arnd,
On Mon, Jul 10, 2017 at 5:14 PM, Arnd Bergmann wrote:
> Geert Uytterhoeven ran into a build error without CONFIG_HAS_DMA,
> as a result of the driver calling set_dma_ops(). While we can
> fix the build error in the dma-mapping implementation, there is
> another problem in this driver:
>
Geert Uytterhoeven ran into a build error without CONFIG_HAS_DMA,
as a result of the driver calling set_dma_ops(). While we can
fix the build error in the dma-mapping implementation, there is
another problem in this driver:
The configuration for the DMA is done by the platform code,
looking up inf
