Local codecs are codecs that run on the same processor as the
application. Remote codecs are codecs that run on a different processor
than the application.
In single processor architectures (e.g. DM643x), all codecs are local.
In DM644x, the application processor is typically the ARM, and codecs
typically run on the DSP. In this case, most of the codecs are remote.
There are exceptions to this general rule. One example would be:
If you don't want to use the Codec Engine framework as your
inter-processor communication (IPC), you can create your own framework -
perhaps based on DSP Link - and use the Codec Engine on the DSP only.
In this case, the CE 'app' is on the DSP, and would invoke 'local'
codecs. You can still benefit from the configuration support, and
resource management CE provides.
Regardless of whether the codec is local or remote, it must be present
(i.e. the codec 'package' must be on the 'package path' - XDCPATH)
during the application's configuration step. This may seem strange -
after all, if I have DSP-side codecs, why do I need them available when
I configure my ARM-side application? The answer is that the codecs'
'packaging' contains meta data which the XDC tooling utilizes during
both the application config step _and_ the server config step.
Chris
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of maxim maxim
Sent: Sunday, February 18, 2007 7:30 AM
To: [email protected]
Subject: local and remote codecs
what is the meaning of local codec and remote codec. Whether
for both codecs are necessary to build a codec server, if one of them
run on GPP platform?
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
