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

cluster

1.need for building ubuntu based clustor and expanding
2.needs 2 nics per node

scene builder

1. will have database,tomcat,webview,user account
2. will have in-channel for data,requirement and rules
3. will have run command
4. will have run save option
5. will have favourable selection criteria
6. will have favourables isolation criteria
7. will have favourables as start set for next run option
8. generates an xml with the favourable scenes organized as nodes and options to see its predecessors
9. later,will have networking option between user accounts and across physical networks
10. later will have , 3 way scene building with moderator
11. later will have n party scene building with moderator
12. later will have archive reference for common paths

rules are interdata relations, data a and b's OK range with c in range OK range

data represented in sets
as none,as one,as n-1, as n defines it
if n is represented as j,k clone or other, in programming a visitor may have life
dependency or other on another one
data as,
A B C but if some scene is not favourable its as,
A B C D, D is the marker for non favourable

lte mac

Angles:

1. uses 8 timers
2. transport channels 
3. crnti and harq 
4. mimo phy 
5. platform interface
6. user interface
7. platform driver states 
8. mac states 
9. phy states
10. internal queues
11. mdb's
12. Memory tabulation
13. Event path counters(will show if previous event path has been taken ,entry till return definer)
14. Event path markers(shows what events are in progress now) is Event counters
15. Assertions
16. Multi level checks for data, datastructures
17. spec version to code mapping information
19. doxygen based annotation
20. perl based automation tool , multithreaded
21. perl tool capable of remote communication by independent channel
22. perl tool capable of log generation
23. scripts directory individually runnable

code will cover the above areas plus,

timestamping
will have module specific in-ram traces(circular)
will have platform event traces
will have platform data structure and protocol internals dump
will have xml interface for default globals and current globals
will have hardware submodule in-ram dump

will work with plarform debugger to give a verbose snap

later, xml for default interfaces and methods and a metadata channel
derived from java model

graphics android,linux,windows

android uses opengl over TI SGX over omap dsp linux uses opengl over ?? vpdau over nvidia windows uses opengl over?? dxva over nvidia