![]() | |||||||||||
Messages in this thread |
"Bryan O'Sullivan" <bos@pathscale.com> wrote: > > This arch-independent routine copies data to a memory-mapped I/O region, > using 32-bit accesses. It does not guarantee access ordering, nor does > it perform a memory barrier afterwards. This style of access is required > by some devices. Not providing orderingor barriers makes this a rather risky thing to export - people might use it, find their driver "works" on one architecture, but fails on another. I guess the "__" is a decent warning of this, and the patch anticipates a higher-level raw_memcpy_toio32() which implements those things, yes? How come __raw_memcpy_toio32() is inlined? - 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/ | ||||||||||
| Last update: 2006-01-10 10:21 [from the cache] ©2003-2008 | |||||||||||