miles@gnu.org said:
> How is the driver supposed to tell whether a given dma_addr_t value
> represents consistent memory or not? It seems like an (arch-specific)
> `dma_addr_is_consistent' function is necessary, but I couldn't see one
> in your patch.
well, the patch was only for x86, which is fully consistent. For parisc, that
becomes a field for the dma accessor functions.
However, even on parisc, the (supported) machines are either entirely
consistent or entirely inconsistent.
If you have a machine that has both consistent and inconsistent blocks, you
need to encode that in dma_addr_t (which is a platform definable type).
The sync functions would just decode the type and either nop or perform the
sync.
James
-
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/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:20 EST