iscasi

1.normal --- disk,partition/volume,filesystem
2.iscasi --- disk,partition/volume/lun,filesystem
3.create lun
arg - the disk
arg - size of partition
arg - ip address associated
arg - tcp port associated
arg - filesystem

4.can non iscasi and iscasi exist together
5.can a folder be shared through iscasi and scasi

account this

1.dsp on board runs using dhcp
2.using nfs
need server side
check during boot suppress permission issues
verified kernel args for nfs
verified dhcp can be used
issue dhcp on client,nfs req on client dhcp on server
issue server needs .tar.bz2 or expanded ones
issue use /tftboot with symbolic links with kernel and rootfs
solved issue sdcard does not see media , ??
solved dns gateway, ??


3.android - tiny android
4.stripping packages
5.pipeline -- sources,binaries,confi files,system.img,data.img,root file system
6.pipeline - - kernel
7.sipdroid
8.dolby
9.diceplayer

more on alsa v4l2 saa

1.sox is a master application used to test many sound related functions
2.alsa 1.0.19/21/24 are latest needed for nvidia gt400 pro working
3.alsa has tools that list the properties of sound card
4.aplay can play mp3s or wav
5.alsa can be compiled from source
6.saa alsa usually comes with kernel with saa dvb,tuner,radio etc , it doesnt have a separate branch outside to compile with any needed kernel
7.tuners are designed for saa specification, all analog , digital tuners are complaint
8.saa71xx is for video and saa71xx-alsa for audio
9.these are interfaced to v4l2 and alsa in the system
10.v4l2-ctl can show details of all video devices in the system
11.pinnacle pctv 310i can do sound in 2 ways , through an internal wire it can give the sound to
real sound card IN hence the sound cards LINEIN can be used as capture device
or
it can expose a sound device interface
12.issue with saa incompatibility b.w in kernel saa alsa and external updated alsa
13.v4l2 sees video devices as /dev/video0
14.saa alsa? sees devices as /dev/dsp /dev/dsp1
15.latest alsa sees devices as hw:1,0 plughw:1,0 ??
16.like alsa oss and pulse audio are independent drivers , they can run sound without alsa
17.can work parallely on different devices, on one device only one can work
18.pulse and oss have a glue layer for alsa??
19.there are sound stack for each of them independently
20.digital video devices are /dev/adapter/dvb0
21.xbmc needs plugin to show bind with vdr
22.vdr needs components from private repo to be functional
23.video with hw accel and non hw accel has different drivers, according to what driver is loaded
for the device hw accel is exposed or disabled.
24.powerful card can expose sterio functionality if old drivers are loaded for it
25.video drivers have persistant switch entries in conf files only at restart they are looked up
26.there is always way to bring up vga
27.codec stack comes on top of saa,and other alsa drivers
28.similar to alsa nvidia and other hw will have latest in place compilable oss and pulseaudio
drivers provided by vendor
29.similarly for video v4l2 ES 1/2/3 compatible drivers updated
30.codecs eat on low level v4l2 and alsa drivers
31.v4l2 and alsa provides apis to apps
32.main apps like flash will use plugins that use these apis
33.xclient startx will use these apis for remote/local sessions
34.for a 5.1 system each channel is a sound device
35.linux has a master firmeare directory used to keep latest fw of all devices
36.vpdau is a v4l2 specification ie from v4l2 to vpdau driver, ES is specification from within vpdau to real hw
37.lirc is v4l2 of ir commn
38.fm radio other radio uses tuner devices and alsa
39.tuner will have /dev/vvv alsa with /dev/aaa
40.they can use v4l2-ctl for scanning and freq
41.so tuner device , sound device, video device basics of multimedia

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

mythtv and xbmc are equivalents

http://en.wikipedia.org/wiki/XBMC

home network pending

1.getting nintendo ... windows 2.changing tv tuner to nintendo 3.getting tv working on nintendo 4.getting usbwifi for pc2 5.getting windows media centre on pc2 6.relaying streams from pc1 to pc2 using darwin and vlc client which contains apache streaming setup 7.get hp touch screen monitor 9.installation