| To: | Jon Dufresne <jon.dufresne@infinitevideocorporation.com> |
|---|---|
| Subject: | Re: Linux mips and DMA |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 10 Jan 2008 13:46:34 +0000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <1199971818.4344.5.camel@microwave.infinitevideocorporation.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <1199905038.3572.8.camel@microwave.infinitevideocorporation.com> <20080110113931.GA4774@linux-mips.org> <1199971818.4344.5.camel@microwave.infinitevideocorporation.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Thu, Jan 10, 2008 at 08:30:16AM -0500, Jon Dufresne wrote:
> > MIPS hardware is different so pci_alloc_consistent is implemented
> > differently. For correct use however this should not matter. Any bugs
> > you may find porting to MIPS were already bugs on x86.
> >
> > (Or in pci_alloc_consistent but I'm optimistic ;-)
>
>
> Is there a chance that my platform does not support coherent DMA
> mappings? Or is this unheard of for a MIPs platform?
Hardware coherency for DMA is the exception for low-end embedded MIPS
systems andgiven the CPU address your's is no exception from that.
If your system was supporting hardware coherency for DMA I/O you would
have obtained a cachable CPU address like:
dma_handle=0x026f0000 size=0x00010000 cpu_addr=0x826f0000
^^^
A 0x8??????? would be in KSEG0 so cachable.
What hardware are you using anyway?
Ralf
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux mips and DMA, Jon Dufresne |
|---|---|
| Next by Date: | pnx8xxx: move to clocksource, Vitaly Wool |
| Previous by Thread: | Re: Linux mips and DMA, Jon Dufresne |
| Next by Thread: | Re: Linux mips and DMA, Jon Dufresne |
| Indexes: | [Date] [Thread] [Top] [All Lists] |