linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	bcm43xx-dev@lists.berlios.de
Subject: Re: [Bcm43xx-dev] 30 bits DMA and ppc
Date: Sun, 30 Oct 2005 09:47:21 +0100	[thread overview]
Message-ID: <200510300947.21917.mbuesch@freenet.de> (raw)
In-Reply-To: <1130645036.29054.229.camel@gaston>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Sunday 30 October 2005 05:03, Benjamin Herrenschmidt wrote:
[snip]
> However, the above would require arch specific hacks, and would only
> work for one card in the system (too bad if you plug a cardbus one).
[snap]

I think we should not need to modify the driver.
Drivers already set the DMA mask. As far as I can see, this mask
is currently (mostly) ignored on PPC and i386 (at least).
As far as I can see, PPC ignores it completely and i386 allocates in the
GFP_DMA region, if DMA is limited.
So I would say, it should be possible to use this mask
with some bounce buffers, as you suggested. That sounds like a good
solution to me. It's worth a try.

-- 
Greetings Michael.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-30  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30  4:03 30 bits DMA and ppc Benjamin Herrenschmidt
2005-10-30  8:47 ` Michael Buesch [this message]
2005-10-30 17:59 ` Olof Johansson
2005-10-30 21:14   ` Benjamin Herrenschmidt
2005-10-30 21:35     ` Olof Johansson
2005-10-30 21:41       ` Benjamin Herrenschmidt
2005-10-30 22:02         ` Olof Johansson
2005-10-31  0:35 ` exception vectors Ingmar
2005-10-31  2:17   ` Benjamin Herrenschmidt
2005-10-31  2:28   ` Hollis Blanchard
2005-10-31  9:58     ` Ingmar
2005-11-01  1:46       ` Olof Johansson
2005-11-01  8:28         ` Ingmar

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=200510300947.21917.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).