kernel module

1. local dir> on ubuntu make -C kdir M=$(pwd) ... works
local dir> on ubuntu make -C kdir M=$(pwd) modules puts in standard directory
...M=$(shell pwd) .. doesnt work
---M=$(PWD) ... may work
all the above in makefile
kdir is separate

measured development

1.caliberation of the process
2.perday objectives,finer split
3.requirements perday
4.functional block,bit block views

windows vista ndis 6 driver and mobile stack

1.use preexisting phy code
2.need kernel module .. non pnp
3.need a nic ndis 6 driver
4.can export any function from driver/module using
__declspec(dllexport),__declspec(dllimport)
5.for importing function the .lib of exporting module
should be statically linked
6.kernel dll is different from above,
it gets loaded in the context of first call of a driver,
check when its driverentry is called to test

star type data processing

1.atleast 3 threads contribute
2.one thread atomic write only
3.one thread check continuity
check single condition
update states
process
4.one thread
check continuity
check single
update
process
goto continuity

global continuity
check single
process
update
check another
...

5.using split names in c code
using atleast 15-20 char name would give a pleasent
look to code
But, remember every time that variable is used
u need to type 15 chars

c functions

1.parameter validatio
2.entry level state validattion
3.incoming outgoing traces
4.passing last states and updations to global debug access
5.aggressive benign checks
6.use of macros,inlines
7.use check and process pardigm.split check and processing blocks.effictive use of while

android media fw

1.use pvlogger to get a complete trace to start

incremental development

1.2 stages
a. functional block
b. bit block

functional block involves
prototype,code modifications,dependency changes,additions,deletions together

--->mostly compilable and runnable

bit block
just prototype ...etc

--->just compilable