Hello Hari, Thank you for reading and replying to our email. On Tue, Aug 10, 2010 at 6:12 PM, Hari Kanigeri <hari.kanigeri@xxxxxxxxx> wrote: > Do you mean dynamic memory management ? Can you please elaborate on > what feature you are referring to ? Yes, dynamic memory management. With DSP Link on the OMAPL138 the memory allocated to the DSP must be specified as a 'hole' in Linux memory at boot-time [1[2][3]. It seems (perhaps this is wishful thinking) that dspbridge does not have this limitation. Also dynamic application loading. With DSP Link it is possible to run multiple linux processes concurrently communicating with DSP tasks but the image loaded and executed on the DSP side must contain the code for all of the tasks at load time [4]. It seems that dspbridge does not have this limitation. I am very interested in learning details about both dsplink and dspbridge; please reply with more details or corrections as you see fit. Best Regards, Ben Gardiner [1] http://processors.wiki.ti.com/index.php/Changing_DSPLink_Memory_Map [2] http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/29571.aspx [3] http://code.google.com/p/rowboat/wiki/DSP [4] http://processors.wiki.ti.com/index.php/Using_DSPLink_from_multiple_processes --- Nanometrics Inc. http://www.nanometrics.ca -- 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
