Gary, Scott <sg@...> writes:
>
> Bernard,
>
> Sorry for the slow reply.
>
> LAD was initially created for a specific use case where multiple
> independent Linux processes needed to be able to simultaneously access
> the DSP, and these processes could come and go in any order at runtime.
> LAD was needed because there were some limitations with the DSP/BIOS
> Link APIs that required coordination between the different apps, as well
> as an ownership model that required the first app to keep alive in order
> for the other apps to continue to use the DSP. When LAD is used, LAD is
> the "owner" of the DSP, and it handles all the DSP/BIOS Link startup and
> shutdown calls that require arbitration between the different apps.
>
> LAD was left very lightly documented because we've been looking at a few
> different options going forward. Today it can be used "under the hood"
> by Codec Engine, and the details are abstracted underneath CE's OS
> abstraction layer. For CE apps, all that is needed (as you can see in
> the speech_copy_LAD example), is to specify in the engine configuration
> file: 1) that LAD is to be used, 2) the particular Link configuration to
> be used, and 3) the path to the DSP server executable.
>
> For non-CE apps that want to communicate with LAD, those apps will need
> to call the "ladclient" APIs at the appropriate parts of their startup
> and shutdown. There is also some work required to define the "common"
> Link configuration that will be used for the DSP server, and all the
> client Linux apps.
>
> I will be adding some LAD information to the DaVinci Wiki. In the mean
> time, I will send you in a private email a document that describes LAD,
> configuration, and usage constraints.
>
> Please contact me directly if you have questions.
>
> Regards,
> Scott
>
Hello Scott,
I am facing a problem trying to use LAD on an OMAP35x based system. I have been
able to built and load the LAD with the following log:
Initializing LAD...
running LAD config inits...
opening FIFO: /tmp/LAD/LADCMDS
I want to use LAD in order to get two GStreamer pipelines running together and
using the DSP. I already have added the following lines to the GStreamer's
engine configuration file:
osalGlobal.useLinkArbiter = true;
demoEngine.linkCfg= "user0";
But it seems like GStreamer is not using the LAD to access the DSP.
In your last email you mention the need of specify the path to the LAD into the
configuration file, I am not completely sure about how to specify it, can you
help me on this? Do you think the problem I am getting is due to the lack of
this path?
Regards,
Marco
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
