:31 PM
To: Jerry Johns
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: RE: DSP Stack Memory Map
> > So what exactly do I have to purchase to get to the stage
> > where I can recompile the codec server to occupy a smaller memory
> > footprint? Does the DVSDK c
> > So what exactly do I have to purchase to get to the stage
> > where I can recompile the codec server to occupy a smaller memory
> > footprint? Does the DVSDK come with the codec server sources?
>
>
> Hi Jerry,
>
> Here is what you need:
>
> 1). DSP tool chain (available via purcha
> So what exactly do I have to purchase to get to the
> stage where I can recompile the codec server to occupy a
> smaller memory footprint? Does the DVSDK come with the codec
> server sources?
Hi Jerry,
Here is what you need:
1). DSP tool chain (available via purchasing DVSDK ($6995
Title: RE: DSP Stack Memory Map
Hello,
So what exactly do I have to
purchase to get to the stage where I can recompile the codec server to occupy a
smaller memory footprint? Does the DVSDK come with the codec server sources?
Thanks
From: Ring, Chris
[mailto:[EMAIL
Title: RE: DSP Stack Memory Map
So, in a nutshell, there is no way I can
do what I’m intending to do (shrink memory map to <=128M) without
buying the DVSDK?
Is there a way around this? I don’t need
to peer into the source code – I just want to change the allocated
memory, and I do
Title: RE: DSP Stack Memory Map
The copy codec packages (e.g. codecs.videnc_copy)
include libraries - and even sources(!), and are there as examples for the Codec
Engine product. Provided you have all the DSP-side requirements
(provided with the DVSDK) like DSP-side compilers, DSP/BIOS
Title: RE: DSP Stack Memory Map
But then how do they expect us to compile the video_copy server, and the associated codecs (videnc_copy, viddec_copy) with it? How are these different from the encode,decode demos H264 codecs in terms of compilability?
-Original Message-
From: DDV
