mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
To: Michael Buesch <mb@bu3sch.de>,
	netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [RFC/PATCH] remove unneeded check in bcm43xx
Date: Tue, 11 Apr 2006 00:13:59 +0200	[thread overview]
Message-ID: <20060410221359.GC27596@ens-lyon.fr> (raw)
In-Reply-To: <20060410134625.GA25360@tuxdriver.com>

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 ?

regards,

Benoit

ps: i do not have the hardware so i sadly cannot test.

-- 
powered by bash/screen/(urxvt/fvwm|linux-console)/gentoo/gnu/linux OS

  parent reply	other threads:[~2006-04-10 22:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10  4:01 Benoit Boissinot
     [not found] ` <200604100607.33362.mb@bu3sch.de>
2006-04-10  4:22   ` Benoit Boissinot
     [not found]     ` <200604100628.01483.mb@bu3sch.de>
2006-04-10  4:38       ` Benoit Boissinot
2006-04-10 13:46       ` John W. Linville
2006-04-10 16:18         ` Arjan van de Ven
2006-04-10 22:13         ` Benoit Boissinot [this message]
2006-04-10 22:28           ` David S. Miller
2006-04-11  1:47           ` Benjamin Herrenschmidt
2006-04-11  1:46     ` Benjamin Herrenschmidt
     [not found]       ` <200604110353.52067.mb@bu3sch.de>
2006-04-11  2:23         ` Benoit Boissinot
2006-04-11  5:49       ` David S. Miller
2006-04-11 20:49         ` Benjamin Herrenschmidt
2006-04-11 21:34           ` David S. Miller
2006-04-11 22:20             ` Benjamin Herrenschmidt
2006-04-11 22:21             ` Benjamin Herrenschmidt
2006-04-11 22:30               ` Benoit Boissinot
2006-04-11 22:35                 ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060410221359.GC27596@ens-lyon.fr \
    --to=benoit.boissinot@ens-lyon.org \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome