From: Benoit Boissinot <[EMAIL PROTECTED]> Date: Tue, 11 Apr 2006 00:13:59 +0200
> On Mon, Apr 10, 2006 at 09:46:30AM -0400, John W. Linville wrote: > > On Mon, Apr 10, 2006 at 06:28:00AM +0200, Michael Buesch wrote: > > > > > To summerize: I actually added these messages, because people were > > > hitting "this does not work with >1G" issues and did not get an error > > > message. > > > So I decided to insert warnings until the issue is fixed inside the arch > > > code. > > > I will remove them once the issue is fixed. > > > > This sounds like the same sort of problems w/ the b44 driver. > > I surmise that both use the same (broken) DMA engine from Broadcom. > > > > Unfortunately, I don't know of any good solution to this. There are > > a few hacks in b44 that deal with the issue. I don't like them, > > although I am the perpetrator of at least one of them. It might be > > worth looking at what was done there? > > The hacks i see there is reallocating a buffer with GFP_DMA, so that > means that if the ppc dma_alloc_coherent did the same thing as the i386 > counterpart (adding GFP_DMA if dma_mask is less than 32bits) it should > work, no ? PowerPC doesn't have a seperate GFP_DMA page pool, so this won't work. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
