Cc: <arnd@...>, <linux-arch@...>, John Linn <linnj@...>, <matthew@...>, <will.newton@...>, <drepper@...>, <microblaze-uclinux@...>, <grant.likely@...>, Michal Simek <monstr@...>, <linux-kernel@...>
matthew@wil.cx; will.newton@gmail.com;
grant.likely@secretlab.ca; Michal Simek;
refactorcache flush code.
then
Yes, in fact this is one of the keys to getting the lltemac driver to
work right. see Documentation/DMA-API.txt
My understanding is that on other architectures (x86, for instance)
'dma' memory ensures other things, like it's accessible in PCI memory
space. On microblaze, there's nothing really special about dma memory,
but you get the API as a chunk.
a
I think it's definitely a simple way of solving the problem (in fact,
the version of the code that's currently at git.xilinx.com includes it).
Would it be better dealt with at the page level, rather than at the
address level, then one of the architecture-reserved flags could be used
for it?
If it really does have value, then I want to make sure it goes in, along
with bits in EDK that make it straightforward to use. For me, the
biggest barrier to using it is understanding exactly what assumptions it
is making on the hardware, and making those assumptions bulletproof.
Steve
--
