> On Thu, Aug 12, 2010 at 2:16 AM, Kamoolkar, Mugdha <[email protected]> wrote: >> You are correct that dynamic linking and loading is a feature that is >> available in DSPBridge, and which is missing in DSPLink, which could work on >> OMAPL1xx if you ported DSPBridge to OMAPL1xx > > I imagined that the lack of MMU would be a blocker in porting > dspbridge since it would be impossible to support scattered (in PAs) > pages on the DSP-side. But Mugdha makes it sound like the port could > be accomplished with DMM omitted. > > Also I believe that the new Contiguous Memory Allocation (CMA) > framework was developed specifically for systems that need to allocate > physically contiguous memory because they don't have an MMU. What > would say to avoiding the IOMMU requirement and keeping DMM by using > physically contiguous dynamically allocated memory regions like those > provided by the new CMA [2]? >
Just curious as how CMA is different from Android's pmem. > Thank you, Best regards, Hari -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
