From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Michael Chan <mchan@broadcom.com>,
Anton Blanchard <anton@samba.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [TG3]: Add DMA address workaround
Date: Wed, 08 Mar 2006 10:21:07 +1100 [thread overview]
Message-ID: <1141773668.11221.110.camel@localhost.localdomain> (raw)
In-Reply-To: <200603071900.k27J0YSP023014@hera.kernel.org>
On Tue, 2006-03-07 at 19:00 +0000, Linux Kernel Mailing List wrote:
> commit 72f2afb8a6858edd9335cd158eb21053a0c2c39a
> tree 1cc6884bf4e48822423d23d68d7b2699cd2e68fd
> parent d11d9b2dd2c43dd99a491df8a83ae28401db0044
> author Michael Chan <mchan@broadcom.com> Tue, 07 Mar 2006 11:28:35 -0800
> committer David S. Miller <davem@davemloft.net> Tue, 07 Mar 2006 11:28:35 -0800
>
> [TG3]: Add DMA address workaround
>
> Add DMA workaround for chips that do not support full 64-bit DMA
> addresses.
>
> 5714, 5715, and 5780 chips only support DMA addresses less than 40
> bits. On 64-bit systems with IOMMU, set the dma_mask to 40-bit so
> that pci_map_xxx() calls will map the DMA address below 40 bits if
> necessary. On 64-bit systems without IOMMU, set the dma_mask to
> 64-bit and check for DMA addresses exceeding the limit in
> tg3_start_xmit().
>
> 5788 only supports 32-bit DMA so need to set the mask appropriately
> also.
I suppose that means I need to update the ppc64 iommu code to actually
honor the DMA mask when allocating ;) That will be easy for "dumb"
iommu's like the G5 but might be a bit more tricky with pSeries.
Anton, Paul, we have no control on the DMA ranges allocated to each phb
in the system, do we know if they go beyond 32 bits ? (And if yes,
beyond 40 bits)
Ben.
next parent reply other threads:[~2006-03-07 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603071900.k27J0YSP023014@hera.kernel.org>
2006-03-07 23:21 ` Benjamin Herrenschmidt [this message]
2006-03-07 22:18 ` [TG3]: Add DMA address workaround Michael Chan
2006-03-08 0:28 ` 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=1141773668.11221.110.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=paulus@samba.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