[Tinyos-beta-commits] CVS: tinyos-1.x/beta/teps/txt tep106.txt, 1.3, 1.4

[Phil Levis]

Update of /cvsroot/tinyos/tinyos-1.x/beta/teps/txt
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16793/txt

Modified Files:
	tep106.txt 
Log Message:
Remove the echos in the Makefile, further text in tep106, an updated 
HTML version of tep1.


Index: tep106.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-1.x/beta/teps/txt/tep106.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** tep106.txt	15 Dec 2004 22:49:33 -0000	1.3
--- tep106.txt	18 Dec 2004 00:21:58 -0000	1.4
***************
*** 18,22 ****
     This memo documents a part of TinyOS for the TinyOS Community, and
     requests discussion and suggestions for improvements.  Distribution
!    of this memo is unlimited.
  
  Abstract
--- 18,23 ----
     This memo documents a part of TinyOS for the TinyOS Community, and
     requests discussion and suggestions for improvements.  Distribution
!    of this memo is unlimited. This memo is in full compliance with
!    TEP 1.
  
  Abstract
***************
*** 24,28 ****
  
  This memo documents the structure and implementation of TinyOS tasks
! and task schedulers.
  
  
--- 25,29 ----
  
  This memo documents the structure and implementation of TinyOS tasks
! and task schedulers in TinyOS 2.x.
  
  
***************
*** 40,44 ****
  the structure of how it does so.
  
- 
  2. Tasks and the Scheduler in TinyOS 1.x
  ====================================================================
--- 41,44 ----
***************
*** 109,115 ****
  
  The solution to this problem in TinyOS 1.x is to signal sendDone() in
! the radio send complete interrupt if the post fails: this violates
! the sync/async boundary, but the justification is that a *possible*
! rare race condition is better than *certain* failure.
  
  3. Tasks in TinyOS 2.x
--- 109,116 ----
  
  The solution to this problem in TinyOS 1.x is to signal sendDone() in
! the radio send complete interrupt if the post fails: this violates the
! sync/async boundary, but the justification is that a *possible* rare
! race condition is better than *certain* failure. The TinyOS 1.x model
! prevents it from doing any better.
  
  3. Tasks in TinyOS 2.x
***************
*** 120,124 ****
  introduce new kinds of tasks beyond the basic use case. TinyOS
  actualizes this by keeping ``post`` and ``task`` for the basic case,
! and introducing task interfaces for additional ones.
  
  Task interfaces allow users to extend the syntax and semantics of
--- 121,125 ----
  introduce new kinds of tasks beyond the basic use case. TinyOS
  actualizes this by keeping ``post`` and ``task`` for the basic case,
! and introducing task interfaces for additional ones. 
  
  Task interfaces allow users to extend the syntax and semantics of
***************
*** 138,145 ****
--- 139,160 ----
  the task's logic.
  
+ .. Note::
+    Need to settle on exact basic task semantics.
  
  4. The Scheduler in TinyOS 2.x
  ====================================================================
  
+ In TinyOS 2.x, the scheduler is a TinyOS component. Every scheduler
+ must support basic nesC tasks. It may also support any number of
+ additional task interfaces. The scheduler component is resonsible for
+ the policy of reconciling different task types (e.g., earliest
+ deadline first tasks vs. priority tasks).
+ 
+ .. Note::
+    The format and implementation of basic tasks greatly depends on their semantics. Need to hash this out.
+ 
+ .. Note:: 
+    Need a better story on this. Separate component? Main?
+