From adee597960ce3c5ff0ce303ae9ac25b7eebdfe32 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Thu, 4 May 2000 19:45:17 +0000 Subject: Numerous changes based on comments from Stephan Wilms including a new section in the Getting Started called "Where to Go From Here", lots of index entries added, and more configuration table information. --- doc/user/signal.t | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc/user/signal.t') diff --git a/doc/user/signal.t b/doc/user/signal.t index 012824fc71..50beb752f9 100644 --- a/doc/user/signal.t +++ b/doc/user/signal.t @@ -37,11 +37,16 @@ signal is sent to a task, that task's execution path will be "interrupted" by the ASR. Sending a signal to a task has no effect on the receiving task's current execution state. +@findex rtems_signal_set + A signal flag is used by a task (or ISR) to inform another task of the occurrence of a significant situation. Thirty-two signal flags are associated with each task. A collection of one or more signals is referred to as a signal -set. A signal set is posted when it is directed (or sent) to a +set. The data type @code{@value{DIRPREFIX}signal_set} +is used to manipulate signal sets. + +A signal set is posted when it is directed (or sent) to a task. A pending signal is a signal that has been sent to a task with a valid ASR, but has not been processed by that task's ASR. @@ -216,6 +221,7 @@ The ASR should have the following calling sequence and adhere to @value{LANGUAGE} calling conventions: @ifset is-C +@findex rtems_asr @example rtems_asr user_routine( rtems_signal_set signals -- cgit v1.2.3