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=0x86D00000 phys_end=0x88000000
pools=1x3600000,16x829440,2x1244160,1x40960,2x8192

2.
The other way is to get rid of all other pools that are existing, and
keep only the 829440 bytes sized pool, eg.
# insert cmemk, tell it to occupy physical 115MB-128MB (13M).
insmod cmemk.ko phys_start=0x87300000 phys_end=0x88000000 pools=16x829440

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).

there should be at least one other CMEM buffer to pass the h264 data fro
the ARM to the DSP. There is something in /proc or /sys where you can
see the cmem memory usage...

Also, with CE_DEBUG=2|3 you should be able to see all cmem allocations
that your codec/setup does.

_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to