> Why not use normal uncached memory? Strongly ordered is pretty > inefficient as it cannot do any reordering or write buffer merging > (it's > like having a memory barrier before and after each instruction). > Speculative accesses are not allowed either. Strongly ordered memory > is > not really meant for executing code from. It could be. This is a discussion we were having off line. The code in question is a small bit of assembly interacting with hardware mainly and has not been audited for full pipeline/buffering correctness. Most of the weak memory attributes in newer ARMs are not exploited today in tree. I'll guess this was more a correctness and capability judgment from Russell. Regards, Richard W. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
