On Tue, Jun 13, 2006 at 02:45:35PM +0200, Benoit Boissinot wrote:
> On Tue, Jun 13, 2006 at 12:28:40PM -0000, Ben Collins wrote:
> > It seems like to me that the bug is not so much in the bcm43xx driver,
> > but in the architectures dma allocation routines. The driver correctly
> > sets DMA_30BIT_MASK for the device, but still seems to be getting > 30
> > bit dma addresses from the allocator.
> >
> > Not sure how this can be fixed.
>
> Did you follow the thread on the lkml ? I believe it was fixed, I could
> search it if you want.
>
A fix is included in .17-rc3
"Olof Johansson:
powerpc: IOMMU support for honoring dma_mask"
I believe the driver was "fixed" to fallback to non-dma mode too, but I
cannot remember what the final conclusion was.
regards,
Benoit
--
powered by bash/screen/(urxvt/fvwm|linux-console)/gentoo/gnu/linux OS
On Tue, Jun 13, 2006 at 02:45:35PM +0200, Benoit Boissinot wrote:
> On Tue, Jun 13, 2006 at 12:28:40PM -0000, Ben Collins wrote:
> > It seems like to me that the bug is not so much in the bcm43xx driver,
> > but in the architectures dma allocation routines. The driver correctly
> > sets DMA_30BIT_MASK for the device, but still seems to be getting > 30
> > bit dma addresses from the allocator.
> >
> > Not sure how this can be fixed.
>
> Did you follow the thread on the lkml ? I believe it was fixed, I could
> search it if you want.
>
A fix is included in .17-rc3
"Olof Johansson:
powerpc: IOMMU support for honoring dma_mask"
I believe the driver was "fixed" to fallback to non-dma mode too, but I
cannot remember what the final conclusion was.
regards,
Benoit
-- (urxvt/ fvwm|linux- console) /gentoo/ gnu/linux OS
powered by bash/screen/