[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep107.txt, 1.10, 1.11 tep111.txt, 1.7, 1.8

[Phil Levis]

Update of /cvsroot/tinyos/tinyos-2.x/doc/txt
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv26485/txt

Modified Files:
	tep107.txt tep111.txt 
Log Message:
Updates.


Index: tep107.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep107.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** tep107.txt	1 Mar 2007 04:21:44 -0000	1.10
--- tep107.txt	1 Mar 2007 17:15:57 -0000	1.11
***************
*** 200,205 ****
  Examples of platform_bootstrap() operations are configuring the memory
  system and setting the processor mode. Generally, platform_bootstrap() 
! is an empty function. The platform_bootstrap() function SHOULD be
! specified in a platform's ``hardware.h`` file. 
  
  The boot sequence has three separate initializations: Scheduler,
--- 200,215 ----
  Examples of platform_bootstrap() operations are configuring the memory
  system and setting the processor mode. Generally, platform_bootstrap() 
! is an empty function. TinyOS's top-level include file, ``tos.h``, includes
! a default implementation of this function which does nothing. If a platform
! needs to replace the default, it SHOULD put it in a platform's
! ``platform.h`` file as a #define. The implementation of ``tos.h`` 
! supports this::
! 
!   /* This platform_bootstrap macro exists in accordance with TEP
!      107. A platform may override this through a platform.h file. */
!   #include <platform.h>
!   #ifndef platform_bootstrap
!   #define platform_bootstrap() {}
!   #endif
  
  The boot sequence has three separate initializations: Scheduler,

Index: tep111.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep111.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep111.txt	5 Feb 2007 20:23:35 -0000	1.7
--- tep111.txt	1 Mar 2007 17:15:57 -0000	1.8
***************
*** 6,18 ****
  :Group: Core Working Group 
  :Type: Documentary
! :Status: Draft
  :TinyOS-Version: 2.x
  :Author: Philip Levis
  
- :Draft-Created: 11-Jul-2005
- :Draft-Version: $Revision$
- :Draft-Modified: $Date$
- :Draft-Discuss: TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu>
- 
  .. Note::
  
--- 6,13 ----
  :Group: Core Working Group 
  :Type: Documentary
! :Status: Final
  :TinyOS-Version: 2.x
  :Author: Philip Levis
  
  .. Note::
  
***************
*** 78,82 ****
    } TOS_Msg;
  
! while on a mote with a CC420 radio (e.g., micaZ), ``TOS_Msg`` is defined as::
  
    typedef struct TOS_Msg {
--- 73,77 ----
    } TOS_Msg;
  
! while on a mote with a CC2420 radio (e.g., micaZ), ``TOS_Msg`` is defined as::
  
    typedef struct TOS_Msg {
***************
*** 368,372 ****
  different versions of an application can have different MTU sizes.
  If a packet layer receives a packet whose payload size is 
! longer than TOSH_DATA_LENGTH, it MUST discard the packet. 
  
  3.3 Footer
--- 363,370 ----
  different versions of an application can have different MTU sizes.
  If a packet layer receives a packet whose payload size is 
! longer than TOSH_DATA_LENGTH, it MUST discard the packet. As
! headers are right justified to the beginning of the data payload,
! the data payloads of all link layers on a platform start
! at the same fixed offset from the beginning of the message buffer.
  
  3.3 Footer