From a94c5a5d6992b6dca9afec09352ab80db4643078 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Sat, 31 May 1997 15:55:10 +0000 Subject: Changed bitwise OR's used to build up option and attribute sets to be correct in either C or Ada. Added the interrupt disable, enable, flash, and is in progress directives. changed "97" to "1997" --- doc/user/schedule.t | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/user/schedule.t') diff --git a/doc/user/schedule.t b/doc/user/schedule.t index 5781a670b7..6007a89244 100644 --- a/doc/user/schedule.t +++ b/doc/user/schedule.t @@ -165,7 +165,7 @@ entire timeslice. The final mechanism for altering the RTEMS scheduling algorithm is called manual round-robin. Manual round-robin is invoked by using the task_wake_after directive with a time -interval of YIELD_PROCESSOR. This allows a task to give up the +interval of @code{YIELD_PROCESSOR}. This allows a task to give up the processor and be immediately returned to the ready chain at the end of its priority group. If no other tasks of the same priority are ready to run, then the task does not lose control @@ -193,12 +193,12 @@ saved or restored for a context switch is located either in the TCB or on the task's stacks. Tasks that utilize a numeric coprocessor and are -created with the FLOATING_POINT attribute require additional +created with the @code{FLOATING_POINT} attribute require additional operations during a context switch. These additional operations are necessary to save and restore the floating point context of -FLOATING_POINT tasks. To avoid unnecessary save and restore +@code{FLOATING_POINT} tasks. To avoid unnecessary save and restore operations, the state of the numeric coprocessor is only saved -when a FLOATING_POINT task is dispatched and that task was not +when a @code{FLOATING_POINT} task is dispatched and that task was not the last task to utilize the coprocessor. @ifinfo -- cgit v1.2.3