[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep106.txt, 1.1.2.6, 1.1.2.7 tep107.txt, 1.1.2.8, 1.1.2.9

Phil Levis scipio at users.sourceforge.net
Fri Jun 9 10:45:00 PDT 2006


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

Modified Files:
      Tag: tinyos-2_0_devel-BRANCH
	tep106.txt tep107.txt 
Log Message:
Fixed citations.


Index: tep106.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/Attic/tep106.txt,v
retrieving revision 1.1.2.6
retrieving revision 1.1.2.7
diff -C2 -d -r1.1.2.6 -r1.1.2.7
*** tep106.txt	9 Jun 2006 16:51:45 -0000	1.1.2.6
--- tep106.txt	9 Jun 2006 17:44:58 -0000	1.1.2.7
***************
*** 46,55 ****
  ====================================================================
  
! Tasks in TinyOS are a form of deferred procedure call (DPC)[1]_, which
  enable a program to defer a computation or operation until a later
  time. TinyOS tasks run to completion and do not pre-empt one
  another.  These two constraints mean that code called from tasks
  runs synchonously with respect to other tasks. Put another way, tasks
! are atomic with respect to other tasks[2]_.
  
  In TinyOS 1.x, the nesC language supports tasks through two
--- 46,55 ----
  ====================================================================
  
! Tasks in TinyOS are a form of deferred procedure call (DPC) [1]_, which
  enable a program to defer a computation or operation until a later
  time. TinyOS tasks run to completion and do not pre-empt one
  another.  These two constraints mean that code called from tasks
  runs synchonously with respect to other tasks. Put another way, tasks
! are atomic with respect to other tasks [2]_.
  
  In TinyOS 1.x, the nesC language supports tasks through two
***************
*** 246,250 ****
  that task's TaskBasic.runTask() event has been signaled. The 
  McuSleep interface is used for microcontroller power management;
! its workings are explained in TEP 112[3]_.
  
  A scheduler MUST provide the Scheduler interface. 
--- 246,250 ----
  that task's TaskBasic.runTask() event has been signaled. The 
  McuSleep interface is used for microcontroller power management;
! its workings are explained in TEP 112 [3]_.
  
  A scheduler MUST provide the Scheduler interface. 
***************
*** 415,424 ****
  
  | Philip Levis
! | 467 Soda Hall
! | UC Berkeley
! | Berkeley, CA 94720
  |
! | phone - +1 510 290 5283
! | email - pal at cs.berkeley.edu
  |
  | Cory Sharp
--- 415,424 ----
  
  | Philip Levis
! | 358 Gates Hall
! | Stanford University
! | Stanford, CA 94305
  |
! | phone - +1 650 725 9046 
! | email - pal at cs.stanford.edu
  |
  | Cory Sharp

Index: tep107.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/Attic/tep107.txt,v
retrieving revision 1.1.2.8
retrieving revision 1.1.2.9
diff -C2 -d -r1.1.2.8 -r1.1.2.9
*** tep107.txt	9 Jun 2006 16:51:45 -0000	1.1.2.8
--- tep107.txt	9 Jun 2006 17:44:58 -0000	1.1.2.9
***************
*** 132,136 ****
  
  The Scheduler interface is for initializing and controlling task
! execution. It is detailed in TEP 106[tep106].
  
  The Boot interface has a single event, booted(), which the boot
--- 132,136 ----
  
  The Scheduler interface is for initializing and controlling task
! execution. It is detailed in TEP 106 [1]_.
  
  The Boot interface has a single event, booted(), which the boot
***************
*** 296,300 ****
  components.
  
! Unless part of a hardware abstraction architecture (HAA)[tep2]_, the
  Init.init() command MUST NOT assume that other components have been
  initialized unless it has initialized them, and MUST NOT call any
--- 296,300 ----
  components.
  
! Unless part of a hardware abstraction architecture (HAA) [2]_, the
  Init.init() command MUST NOT assume that other components have been
  initialized unless it has initialized them, and MUST NOT call any
***************
*** 326,329 ****
  ====================================================================
  
! .. [tep2] TEP 2: Hardware Abstraction Architecture. Vladi Handziski, Joseph Polastre, Jan-Hinrich Hauer, Cory Sharp. Adam Wolisz and David Culler.
   
--- 326,331 ----
  ====================================================================
  
! .. [1] TEP 106: Schedulers and Tasks.
! 
! .. [2] TEP 2: Hardware Abstraction Architecture. 
   



More information about the Tinyos-2-commits mailing list