Hi, On Wed, Aug 11, 2010 at 3:56 PM, Ben Gardiner <bengardiner@xxxxxxxxxxxxxx> wrote: > 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. The dsp-bridge can map scattered user-space pages just fine. > 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. Indeed, you can dynamically load socket-nodes. > I am very interested in learning details about both dsplink and > dspbridge; please reply with more details or corrections as you see > fit. Have you looked into dsp-gateway[1]? The code is very simple and AFAIK it was close to getting merged upstream, but it's unmaintained nowadays. It was used on OMAP1 and OMAP2 by Nokia, and shares code with dsp-bridge, like mailbox and soon iommu. So it might be possible to port the OMAP1 stuff from dsp-gateway into dsp-bridge. Cheers. [1] http://dspgateway.sourceforge.net/pub/index.php -- Felipe Contreras -- 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
