Ticket #1171: tim2.diff

doc/user/timer.t

@@ -60 +60 @@
 The Timer Server task is responsible for executing the timer
 service routines associated with all task-based timers. 
 This task executes at a priority higher than any RTEMS application
-task and thus can be viewed logically as the lowest priority interrupt.
+task, and is created non-preemptable, and thus can be viewed logically as
+the lowest priority interrupt.
 
 By providing a mechanism where timer service routines execute
 in task rather than interrupt space, the application is 
@@ -70 +71 @@
 it would be save to perform floating point operations
 from a task-based timer.  Most of the time, executing floating
 point instructions from an interrupt service routine
-is not considered safe.
+is not considered safe. However, since the Timer Server task
+is non-preemptable, only directives allowed from an ISR can be
+called in the timer service routine.
 
 The Timer Server is designed to remain blocked until a 
 task-based timer fires.  This reduces the execution overhead
@@ -512 +515 @@
 @findex rtems_timer_initiate_server
 @example
 rtems_status_code rtems_timer_initiate_server(
+  unsigned32           priority,
   unsigned32           stack_size,
   rtems_attribute      attribute_set
 )