Subject: Re: [TG3]: Add DMA address workaround
From: "Michael Chan" <mchan@broadcom.com>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
       "David S. Miller" <davem@davemloft.net>,
       "Anton Blanchard" <anton@samba.org>,
       "Paul Mackerras" <paulus@samba.org>
In-Reply-To: <1141773668.11221.110.camel@localhost.localdomain>
References: <200603071900.k27J0YSP023014@hera.kernel.org>
 <1141773668.11221.110.camel@localhost.localdomain>
Date: Tue, 07 Mar 2006 14:18:58 -0800
Message-ID: <1141769938.8146.19.camel@rh4>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 868
Lines: 20

On Wed, 2006-03-08 at 10:21 +1100, Benjamin Herrenschmidt wrote:

> 
> 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)
> 
So how does powerpc handle 32-bit PCI devices that don't support dual
address cycles? Such devices will set the dma_mask to 32-bit. Shouldn't
40-bit be handled in a similar way?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/