ExMem.AllocCacheable and not ExMem.AllocCacheableMemory as stand in your intro post.
exmem_heap = suba_init((void*)(((unsigned long)mem)&~CAM_UNCACHED_BIT),EXMEM_HEAP_SIZE,1,1024);
Another thing I've noticed is that the base address of the memory (exmem_heap) is 0x47c00000 (on the SX30 with 4MB allocated).Isn't this an non-cacheable address (CAM_UNCACHED_BIT is set)?If so, will this have a performance impact?
Quote from: philmoz on 02 / January / 2011, 21:51:17Another thing I've noticed is that the base address of the memory (exmem_heap) is 0x47c00000 (on the SX30 with 4MB allocated).Isn't this an non-cacheable address (CAM_UNCACHED_BIT is set)?If so, will this have a performance impact?On d10 at least, the camera function twiddles the bits on the returned pointer for you. Exmem View always reports the uncached version.As for the other stuff... not sure what to make of it.
Looks like the camera is using this memory without properly allocating it (or there is a bug in the memory allocator).
Have you run an exmem.view while recording video ?
Or there is some subtlety of the exmem api we haven't understood. There is a third param to exmem_alloc. I initially thought it indicated cacheable or not, but it clearly isn't.
Started by Microfunguy General Discussion and Assistance
Started by mp9_sit Script Writing
Started by Barney Fife Completed and Working Scripts
Started by Lebeau General Discussion and Assistance
Started by CanonBlue General Help and Assistance on using CHDK stable releases