gingerbread 2.3.4 DSP memory hole seetings for beagleboard-xm rev C

```
What steps will reproduce the problem?

if i use "mem=99M@0x80000000 mem=384M@0x88000000" settings when booting

I got

# insmod /system/ti-dsp/cmemk.ko "phys_start=0x84F00000 phys_end=0x85900000
allowOverlap=1 useHeapIfPoolUnavailable=1"
CMEMK module: built on Jul 8 2011 at 02:32:28
Reference Linux version 2.6.32
File /beagleboard/rowboat-android/external/ti-dsp/ti-dvsdk_dm3730-evm_4_01_00_09/linuxutils_2_25_05_11/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0x84f00000) overlaps kernel (0x80000000 -> 0x9e300000)
CMEMK Error: Failed to request_mem_region(0x84f00000, 10485760)
insmod: init_module '/system/ti-dsp/cmemk.ko' failed (Bad address)

this error ,

when i use "mem=76M@0x80000000 mem=128M@0x88000000'
everythings work perfect.

What is the correct settings cmemk.ko for 512MB.

Additional Info

I load u-Image @0x82000000

```

Original issue reported on code.google.com by `mehmet.u...@gmail.com` on 9 Jul 2011 at 4:41

Start with the boot memory arguments and the cmemk.ko parameters shown in the report, then inspect external/ti-dsp/ti-dvsdk_dm3730-evm_4_01_00_09/linuxutils_2_25_05_11/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c. Compare the failing 512MB layout with the working layout and the u-Image load address. Done means identifying compatible settings that let cmemk.ko load without overlapping the kernel.

Written by the indexing model from the issue text.