1. has both wince and linux support
2. has 2 boot options .. from nand and mmc/sd
3. mmc/sd serves the purpose of floppy on desktop
4. with a bareskeleton nand , mmc booting can be used to flash other components to it
5. with a zero nand content , special techniques of using serial null modem cable to set it up for
basic booting
6. binaries used for mmc/sd booting .. MLO,uboot,kernel,rfs .. for nand XLOADER,uboot,kernel rfs
7. another important component the environment variables .. they are stored on the nand
8. there is separate section for mmc/sd env and nand env .. inaddition on the nand there are some other basic data
9. rfs can be on nand or sd interchangebly
10.some useful system running over it wince,0xdroid,rowboat etc
Tuesday, August 10, 2010
code.google.com
1.use eclipse for easier usage
2.install svn,openssh,git-core,git-svn on ubuntu
3.precreate google project
4.add repository path in eclipse
https://prototest.googlecode.com/svn/trunk
5.goto team option in the elclipse project,click on share project
6.when asked for username and passwd goto
https://code.google.com/hosting/settings
7.select files and commit
2.install svn,openssh,git-core,git-svn on ubuntu
3.precreate google project
4.add repository path in eclipse
https://prototest.googlecode.com/svn/trunk
5.goto team option in the elclipse project,click on share project
6.when asked for username and passwd goto
https://code.google.com/hosting/settings
7.select files and commit
c++, protocol
1.common class to keep reference count
2.common class to stackup or organize similar objects
3.common class that helps to minimize operations, and demux all operations through a single interface
4.contexts to define an operations ... the operation parameters will be symmetrical across but the context determines what is done
1.context contains src,sink and signature routine that is overloaded and takes a event pointer or void args
2.it moves the data in units , minimal transition in a system
3.All layers are contexts,has a default signature functions
4.a layer has a chain of contexts each having the signature function
5.when the source to signature function is null the signature function may be in a demux context
2.common class to stackup or organize similar objects
3.common class that helps to minimize operations, and demux all operations through a single interface
4.contexts to define an operations ... the operation parameters will be symmetrical across but the context determines what is done
1.context contains src,sink and signature routine that is overloaded and takes a event pointer or void args
2.it moves the data in units , minimal transition in a system
3.All layers are contexts,has a default signature functions
4.a layer has a chain of contexts each having the signature function
5.when the source to signature function is null the signature function may be in a demux context
code.google.com
it has its own repository either svn or mercurial
to add code , local system needs svn or mercurial installed
git and mercurial are alike because they allow collaboration better
there is also a way in which your personal repository can be mirrored on code.google.com.so the
original remains with you and what you see on the web is a mirror.In addition it provides all the
flexibilities of the hosted site
to add code , local system needs svn or mercurial installed
git and mercurial are alike because they allow collaboration better
there is also a way in which your personal repository can be mirrored on code.google.com.so the
original remains with you and what you see on the web is a mirror.In addition it provides all the
flexibilities of the hosted site
Subscribe to:
Posts (Atom)