Re: DMA API issues

From: James Bottomley
Date: Fri Jun 18 2004 - 22:52:13 EST


On Fri, 2004-06-18 at 19:14, Ian Molton wrote:
> On 18 Jun 2004 19:04:11 -0500
> James Bottomley <James.Bottomley@xxxxxxxxxxxx> wrote:
>
> > Because the piece of memory you wish to access is bus remote.
>
> No, its *not*
>
> my CPU can write there directly.
>
> no strings attached.
>
> the DMA API just only understands how to map from RAM, not anything
> else.

I think you'll actually find that it is. OHCI is a device (representing
a USB hub), it's attached to the system by some interface that
constitutes a bus (the bus interface transforming the CPU access cycles
to device access cycles, translating interrupts etc.).

But even if you've somehow managed to glue an OHCI directly on to the
system memory controller, from the point of view of the DMA API, the
memory the device contains is still bus remote. To be useful, the API
has to deal with bus remote memory in all its forms.

James


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