[Tinyos-2-commits] CVS: tinyos-2.x/doc/html tep107.html,1.7,1.8

Mon Feb 5 11:59:14 PST 2007

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

Modified Files:
	tep107.html 
Log Message:
Fixed links.


Index: tep107.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep107.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep107.html	5 Feb 2007 19:11:25 -0000	1.7
--- tep107.html	5 Feb 2007 19:59:12 -0000	1.8
***************
*** 421,425 ****
  may start before initialization is complete.</p>
  <p>The Scheduler interface is for initializing and controlling task
! execution. It is detailed in TEP 106 <a class="footnote-reference" href="#id5" id="id1" name="id1">[1]</a>.</p>
  <p>The Boot interface has a single event, booted(), which the boot
  sequence signals when it has completed:</p>
--- 421,425 ----
  may start before initialization is complete.</p>
  <p>The Scheduler interface is for initializing and controlling task
! execution. It is detailed in TEP 106 <a class="footnote-reference" href="#id7" id="id1" name="id1">[1]</a>.</p>
  <p>The Boot interface has a single event, booted(), which the boot
  sequence signals when it has completed:</p>
***************
*** 534,538 ****
  (regardless of what components the OS uses) for low-power reasons:
  incorrectly configured pins can draw current and prevent the MCU from
! entering its lowest power sleep state[<a class="reference" href="#id6">2</a>]. Clock calibration meets
  all three criteria. LED configuration is a special case: while it
  nominally meets all three criteria, the most important one is the third:
--- 534,538 ----
  (regardless of what components the OS uses) for low-power reasons:
  incorrectly configured pins can draw current and prevent the MCU from
! entering its lowest power sleep state <a class="footnote-reference" href="#id8" id="id3" name="id3">[2]</a>. Clock calibration meets
  all three criteria. LED configuration is a special case: while it
  nominally meets all three criteria, the most important one is the third:
***************
*** 547,554 ****
  <p>One common approach is for a configuration to &quot;auto-wire&quot; the
  initialization routines of its internal components. The configuration
! does not provide an Init interface. Virtualized services (TEP 108)
  often take this approach, as the service, rather than the clients, is
  what needs to be initialized. For example, the standard Timer
! virtualization (TEP 102), TimerMilliC, wires to TimerMilliP, which is
  a very simple configuration that takes the underlying implementation
  (HilTimerMilliC) and wires it to MainC:</p>
--- 547,554 ----
  <p>One common approach is for a configuration to &quot;auto-wire&quot; the
  initialization routines of its internal components. The configuration
! does not provide an Init interface. Virtualized services
  often take this approach, as the service, rather than the clients, is
  what needs to be initialized. For example, the standard Timer
! virtualization <a class="footnote-reference" href="#id9" id="id4" name="id4">[3]</a>, TimerMilliC, wires to TimerMilliP, which is
  a very simple configuration that takes the underlying implementation
  (HilTimerMilliC) and wires it to MainC:</p>
***************
*** 605,609 ****
  care needs to be used in order to not disrupt the operation of other
  components.</p>
! <p>Unless part of a hardware abstraction architecture (HAA) <a class="footnote-reference" href="#id6" id="id3" name="id3">[2]</a>, the
  Init.init() command MUST NOT assume that other components have been
  initialized unless it has initialized them, and MUST NOT call any
--- 605,609 ----
  care needs to be used in order to not disrupt the operation of other
  components.</p>
! <p>Unless part of a hardware abstraction architecture (HAA) <a class="footnote-reference" href="#id10" id="id5" name="id5">[4]</a>, the
  Init.init() command MUST NOT assume that other components have been
  initialized unless it has initialized them, and MUST NOT call any
***************
*** 633,637 ****
  <li><tt class="docutils literal"><span class="pre">RealMainP.nc</span></tt> is the module containing the function <tt class="docutils literal"><span class="pre">main</span></tt>.</li>
  <li><tt class="docutils literal"><span class="pre">MainC.nc</span></tt> is the configuration that wires RealMainP to
! PlatformC and TinySchedulerC <a class="footnote-reference" href="#id5" id="id4" name="id4">[1]</a>.</li>
  </ul>
  </blockquote>
--- 633,637 ----
  <li><tt class="docutils literal"><span class="pre">RealMainP.nc</span></tt> is the module containing the function <tt class="docutils literal"><span class="pre">main</span></tt>.</li>
  <li><tt class="docutils literal"><span class="pre">MainC.nc</span></tt> is the configuration that wires RealMainP to
! PlatformC and TinySchedulerC <a class="footnote-reference" href="#id7" id="id6" name="id6">[1]</a>.</li>
  </ul>
  </blockquote>
***************
*** 652,665 ****
  <div class="section">
  <h1><a id="citations" name="citations">7. Citations</a></h1>
! <table class="docutils footnote" frame="void" id="id5" rules="none">
  <colgroup><col class="label" /><col /></colgroup>
  <tbody valign="top">
! <tr><td class="label"><a name="id5">[1]</a></td><td><em>(<a class="fn-backref" href="#id1">1</a>, <a class="fn-backref" href="#id4">2</a>)</em> TEP 106: Schedulers and Tasks.</td></tr>
  </tbody>
  </table>
! <table class="docutils footnote" frame="void" id="id6" rules="none">
  <colgroup><col class="label" /><col /></colgroup>
  <tbody valign="top">
! <tr><td class="label"><a class="fn-backref" href="#id3" name="id6">[2]</a></td><td>TEP 2: Hardware Abstraction Architecture.</td></tr>
  </tbody>
  </table>
--- 652,677 ----
  <div class="section">
  <h1><a id="citations" name="citations">7. Citations</a></h1>
! <table class="docutils footnote" frame="void" id="id7" rules="none">
  <colgroup><col class="label" /><col /></colgroup>
  <tbody valign="top">
! <tr><td class="label"><a name="id7">[1]</a></td><td><em>(<a class="fn-backref" href="#id1">1</a>, <a class="fn-backref" href="#id6">2</a>)</em> TEP 106: Schedulers and Tasks.</td></tr>
  </tbody>
  </table>
! <table class="docutils footnote" frame="void" id="id8" rules="none">
  <colgroup><col class="label" /><col /></colgroup>
  <tbody valign="top">
! <tr><td class="label"><a class="fn-backref" href="#id3" name="id8">[2]</a></td><td>TEP 112: Microcontroller Power Management.</td></tr>
! </tbody>
! </table>
! <table class="docutils footnote" frame="void" id="id9" rules="none">
! <colgroup><col class="label" /><col /></colgroup>
! <tbody valign="top">
! <tr><td class="label"><a class="fn-backref" href="#id4" name="id9">[3]</a></td><td>TEP 102: Timers.</td></tr>
! </tbody>
! </table>
! <table class="docutils footnote" frame="void" id="id10" rules="none">
! <colgroup><col class="label" /><col /></colgroup>
! <tbody valign="top">
! <tr><td class="label"><a class="fn-backref" href="#id5" name="id10">[4]</a></td><td>TEP 2: Hardware Abstraction Architecture.</td></tr>
  </tbody>
  </table>