Friday, October 7, 2011

android with dsp

1.issue
/etc/vold.fstab
dev_mount sdcard /mnt/sdcard 3 /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
for gallery not detecting media clips

2.Ensure DSP
The DSP Link was correctly created as I can see during boot messages:
... VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 172K CMEMK module: built on Nov 23 2010 at 17:47:20 Reference Linux version 2.6.32 File /home/imc/i-tv/rowboat-froyo-dsp/external/ti-dsp/ dvsdk_3_01_00_10/codec_engine_2_25_05_16/cetools/packages/ti/sdo/ linuxutils/cmem/src/module/cmemk.c CMEM Range Overlaps Kernel Physical - allowing overlap CMEM phys_start (0x85800000) overlaps kernel (0x80000000 -> 0x8d800000) allocated heap buffer 0xd1000000 of size 0x4be000 cmemk initialized DSPLINK Module (1.65.00.02) created on Date: Nov 23 2010 Time: 17:45:38 SDMAK module: built on Nov 23 2010 at 17:47:41 Reference Linux version 2.6.32 File /home/imc/i-tv/rowboat-froyo-dsp/external/ti-dsp/ dvsdk_3_01_00_10/codec_engine_2_25_05_16/cetools/packages/ti/sdo/ linuxutils/sdma/src/module/sdmak.c init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' #


3.relation of resolution and vram
try to add these option in your kernel command line: vram=XXX for example for 1280x1024MR-16@60 you should add vram=4M 1440x1050MR-16@60, vram=6M 1600x1024MR-16@60, vram=7M etc, the equation to calculate the vram value is x_res*y_rex*4

xserver

1.xserver has a network interface and a window manager interface
2.xclient will have lower graphics hw interface and upper x server interface
3.xserver will have frame buffer abstraction
4.startx is client
5.frame buffer can be switched from local to remote x client
6.remote connection can have a compression protocol

ti android dsp checks

http://processors.wiki.ti.com/index.php/SGXDbg