[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep111.txt, 1.1.2.1, 1.1.2.2

[Phil Levis]

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

Modified Files:
      Tag: tinyos-2_0_devel-BRANCH
	tep111.txt 
Log Message:
Incorporated David Gay's comments on network types. Fixed citations.


Index: tep111.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/Attic/tep111.txt,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -C2 -d -r1.1.2.1 -r1.1.2.2
*** tep111.txt	31 Oct 2005 22:16:36 -0000	1.1.2.1
--- tep111.txt	16 Dec 2005 19:18:10 -0000	1.1.2.2
***************
*** 152,157 ****
  
  Every link layer defines its header, footer, and metadata
! structures. For example, the CC1000 radio implementation defines its
! structures in ``CC1000Msg.h``:
  
  |  ``typedef nx_struct CC1KHeader {``
--- 152,159 ----
  
  Every link layer defines its header, footer, and metadata
! structures. These structures MUST be network structs, and all of their
! fields MUST be network types, in order to ensure cross-platform
! compatibility.  For example, the CC1000 radio implementation defines
! its structures in ``CC1000Msg.h``:
  
  |  ``typedef nx_struct CC1KHeader {``
***************
*** 212,216 ****
  This ensures that enough space is allocated for all underlying link layers.
  
! 3. Accessing message_t fields
  ====================================================================
  
--- 214,218 ----
  This ensures that enough space is allocated for all underlying link layers.
  
! 3. Message_t fields
  ====================================================================
  
***************
*** 320,325 ****
  dependent. A component MUST cast these fields to link specific structures. 
  
- Following these rules means that a packet is 
- 
  The basic issue driving these design considerations is that 
  the C naming layout of message_t fields is platform specific. As a
--- 322,325 ----
***************
*** 330,334 ****
  Following this approach means that the packet header and data payload
  are contiguous in memory, which allows other communication abstractions
! (such as a UART) to easily encapsulate a packet.
  
  4. Author's Address
--- 330,334 ----
  Following this approach means that the packet header and data payload
  are contiguous in memory, which allows other communication abstractions
! (such as a UART, see TEP 113[_tep113]) to easily encapsulate a packet.
  
  4. Author's Address
***************
*** 336,353 ****
  
  | Philip Levis
! | 467 Soda Hall
! | UC Berkeley
! | Berkeley, CA 94720
! |
! | phone - +1 510 290 5283
  |
! | email - pal at cs.berkeley.edu
  
! 7. Citations
  ====================================================================
  
! .. [rst] reStructuredText Markup Specification. <http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html>
!  
! .. [sipattern] The Service Instance Pattern. In *Software Design Patterns for TinyOS.* David Gay, Philip Levis, and David Culler. Published in Proceedings of the ACM SIGPLAN/SIGBED 2005 Conference on Languages, Compilers, and Tools for Embedded Systems (LCTES'05).
! 
! .. [boot] TEP 107: TinyOS 2.x Boot Sequence.
--- 336,349 ----
  
  | Philip Levis
! | 358 Gates Hall
! | Computer Science Laboratory
! | Stanford University
! | Stanford, CA 94305
  |
! | phone - +1 650 725 9046
! | email - pal at cs.stanford.edu
  
! 5. Citations
  ====================================================================
  
! .. [tep113] TEP 113: Serial Communication.