On Thu, Aug 09, 2007 at 06:21:01PM +0100, Alan Cox wrote: > > > Seems to be some kind of AMD64 specific DMA mapping bug ? > > > > I think it's dev->dma_mask == NULL. Clearly you're passing a non DMA > > able device to dma_alloc_coherent(). Which seems like a caller bug. > > Ok - other archs seem to just return NULL in this case. If its your view Ok then the initialization would fail. I could do that, but clearly there must be some other bug in the process that tries to do DMA on such random devices in the first place. > that dma_alloc_coherent(dev) should explode not return NULL then we can > wrap dma_alloc_coherent but I'm not sure the caller library has any > business knowing whether a specific class of device is DMA capable on a > specific platform ? Someone must ask that caller library to DMA to/from that device in the first place. Whoever it is it is wrong. Or perhaps you got the wrong device here? For ISA devices we traditionally used NULL. Or if you set up your own ISA devices (which I can't see a reason for but there might be one I'm missing) at least give them a dma mask. Then it should probably work on x86-64. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
