On Wed, 30 May 2007 14:40:02 -0700,
"Williams, Dan J" <[EMAIL PROTECTED]> wrote:
> With the patch non-dma-architectures that try to build code with true
> dependencies on the DMA api will fail to link i.e.:
>
> CONFIG_DMA_ENGINE=y CONFIG_HAS_DMA=n ASYNC_MEMCPY=y
> CC init/version.o
> LD
[ please let me know if you want to be dropped from the cc ]
> From: Cornelia Huck [mailto:[EMAIL PROTECTED]
> IMO, well-placed #ifdefs are preferrable to dragging non-working code
> around. Like:
>
> - put the DMA path in a file only build for MY_STUFF_USE_DMA
> - let MY_STUFF select MY_STUFF_US
On Fri, 25 May 2007 09:36:31 -0700,
"Dan Williams" <[EMAIL PROTECTED]> wrote:
> I went back and read the thread leading up to this patch and I am of
> the opinion that John's approach (adding more stubs to
> dma-mapping-broken.h:
> http://marc.info/?l=linux-kernel&m=117219377712232&w=2) is needed
[ apologies for reviving an old conversation ]
On 2/26/07, Heiko Carstens <[EMAIL PROTECTED]> wrote:
From: Heiko Carstens <[EMAIL PROTECTED]>
Architectures that don't support DMA can say so by adding a
config NO_DMA to their Kconfig file. This will prevent compilation
of some dma specific drive
From: Heiko Carstens <[EMAIL PROTECTED]>
Architectures that don't support DMA can say so by adding a
config NO_DMA to their Kconfig file. This will prevent compilation
of some dma specific driver code. Also dma-mapping-broken.h isn't
needed anymore on at least s390.
This avoids compilation and lin
5 matches
Mail list logo
