for kernel part first you need to modify DMA memory size in kernel/include/asm-arm/memory.h modify CONSISTENT_DMA_SIZE originally it was only 2M , so when you specify larger than 800x650 (800 * 650 * 4 = 2080000 => almost 2M) you can see out of memory in framebuffer
but the maximux value of DMA_SIZE is only for 4M (the size of the page table used by DMA) if you want to use more video memory you can use boot_mem_alloc functions for emulator part i have also enlarge linux memory in qemu external/qemu/vl.c modify DEFAULT_RAM_SIZE otherwise the available memory after booting up is only a few for framework part you need to modify the heap size for dalvikvm and surfaceflinger if you want a very high resolution surfaceflinger: mSurfaceHeapManager = new SurfaceHeapManager( SIZE_YOU_WANT << 20) and modify dalvik startup options -Xms4m or 8m at that time i found that if the startup memory size and maximux size are the same dalvik will behave strangely i've done this several months ago so somethins might have changed but above is what i have done before good luck to you anyway On Mar 9, 8:11 pm, Bill <[email protected]> wrote: > I'm trying to port Android to a screen with a higher resolution. I > saw a previous post about this but, no one responded. Seems the issue > has something to do with a limit possibly set in the kernel. Has > anyone had any success porting to a bigger screen with resolution > greater than 800x600 and if so could you please share your experience? > > Here is the previous thread on the > topic:http://groups.google.com/group/android-porting/browse_thread/thread/6... > > Thanks! --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
