On Thu, Dec 23, 2010 at 02:35:00PM +0100, Tomasz Fujak wrote: > Dear Mr. King, > > AFAIK the CMA is the fourth attempt since 2008 taken to solve the > multimedia memory allocation issue on some embedded devices. Most > notably on ARM, that happens to be present in the SoCs we care about > along the IOMMU-incapable multimedia IPs. > > I understand that you have your guidelines taken from the ARM > specification, but this approach is not helping us. I'm sorry you feel like that, but I'm living in reality. If we didn't have these architecture restrictions then we wouldn't have this problem in the first place. What I'm trying to do here is to ensure that we remain _legal_ to the architecture specification - which for this issue means that we avoid corrupting people's data. Maybe you like having a system which randomly corrupts people's data? I most certainly don't. But that's the way CMA is heading at the moment on ARM. It is not up to me to solve these problems - that's for the proposer of the new API to do so. So, please, don't try to lump this problem on my shoulders. It's not my problem to sort out. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>