Sameer Naik wrote:
One way to achieve this is my simply increasing the cmem memory, so
that the module load line, for example, would look like this:
1.
# insert cmemk, tell it to occupy physical 109MB-128MB (19M).
insmod cmemk.ko phys_start=0x86D0 phys_end=0x8800
Sameer Naik spiffera, alle Monday 15 February 2010 circa:
At least currently i am not allocating buffers other than of size
829440, using CMEM, but at the same time i am not sure whether any of
the dsp algorithms allocated memory using CMEM (by guess would be no).
I would want this to be
thats right!
On Mon, Feb 15, 2010 at 6:09 PM, Andrea Gasparini gaspar...@imavis.com wrote:
Sameer Naik spiffera, alle Monday 15 February 2010 circa:
At least currently i am not allocating buffers other than of size
829440, using CMEM, but at the same time i am not sure whether any of
the dsp
Greetings,
As far as I knew, any XDAIS or XDM spec'd algorithms cannot allocate their
own CMEM buffers.
CMEM allocations are always under application control and thus you can
dictate where the shared memory is allocated.
In fact, you could not use CMEM at all and just have a section of memory
: davinci-linux-open-source@linux.davincidsp.com
Subject: RE: CMEM Memory Map
Greetings,
As far as I knew, any XDAIS or XDM spec'd algorithms cannot
allocate their
own CMEM buffers.
CMEM allocations are always under application control and thus you can
dictate where the shared memory
-linux-open-source@linux.davincidsp.com
Subject: Re: CMEM Memory Map
Sameer Naik wrote:
One way to achieve this is my simply increasing the cmem memory, so
that the module load line, for example, would look like this:
1.
# insert cmemk, tell it to occupy physical 109MB-128MB (19M
] On Behalf Of Vladimir Pantelic
Sent: Monday, February 15, 2010 4:27 AM
To: davinci-linux-open-source@linux.davincidsp.com
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: CMEM Memory Map
Sameer Naik wrote:
One way to achieve this is my simply increasing the cmem memory, so
