Changeset 13fb305 in rtems


Ignore:
Timestamp:
10/06/99 17:50:07 (23 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
a446d455
Parents:
defc332
Message:

Enabled images. They appear to work ok for PostScript? but not as well
for PDF -- at least according to ghostview.

Location:
doc/user
Files:
2 added
3 edited

Legend:

Unmodified
Added
Removed
  • doc/user/Makefile

    rdefc332 r13fb305  
    5555html: dirs $(FILES)
    5656        -mkdir -p $(WWW_INSTALL)/c_user
    57         cp rtemsarc.gif rtemspie.gif states.gif $(WWW_INSTALL)/c_user
     57        cp rtemsarc.png rtemspie.png states.png $(WWW_INSTALL)/c_user
    5858        $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \
    5959            $(PROJECT).texi
  • doc/user/overview.t

    rdefc332 r13fb305  
    271271@ifset use-html
    272272@html
    273 <IMG SRC="rtemspie.gif" WIDTH=500 HEIGHT=300 ALT="RTEMS Architecture">
     273<IMG SRC="rtemspie.png" WIDTH=500 HEIGHT=300 ALT="RTEMS Architecture">
    274274@end html
    275275@end ifset
  • doc/user/schedule.t

    rdefc332 r13fb305  
    172172blocked, dormant, and non-existent.
    173173
     174A task occupies the non-existent state before a
     175@code{@value{DIRPREFIX}task_create} has been
     176issued on its behalf.  A task enters the
     177non-existent state from any other state in the system when it is
     178deleted with the @code{@value{DIRPREFIX}task_delete}
     179directive.  While a task occupies
     180this state it does not have a TCB or a task ID assigned to it;
     181therefore, no other tasks in the system may reference this task.
     182
     183When a task is created via the @code{@value{DIRPREFIX}task_create} directive
     184it enters the dormant state.  This state is not entered through
     185any other means.  Although the task exists in the system, it
     186cannot actively compete for system resources.  It will remain in
     187the dormant state until it is started via the @code{@value{DIRPREFIX}task_start}
     188directive, at which time it enters the ready state.  The task is
     189now permitted to be scheduled for the processor and to compete
     190for other system resources.
     191
    174192@ifset use-ascii
    175193@example
     
    206224
    207225@ifset use-tex
    208 @c for now use the ascii version
     226@c @page
     227@c @image{states,5in,4in}
    209228@example
    210229@group
     
    237256@end group
    238257@end example
    239 @tex
    240 @end tex
    241258@end ifset
    242259
    243260@ifset use-html
    244261@html
    245 <IMG SRC="states.gif" WIDTH=550 HEIGHT=400 ALT="RTEMS Task States">
     262<IMG SRC="states.png" WIDTH=550 HEIGHT=400 ALT="RTEMS Task States">
    246263@end html
    247264@end ifset
    248 
    249 A task occupies the non-existent state before a
    250 @code{@value{DIRPREFIX}task_create} has been
    251 issued on its behalf.  A task enters the
    252 non-existent state from any other state in the system when it is
    253 deleted with the @code{@value{DIRPREFIX}task_delete}
    254 directive.  While a task occupies
    255 this state it does not have a TCB or a task ID assigned to it;
    256 therefore, no other tasks in the system may reference this task.
    257 
    258 When a task is created via the @code{@value{DIRPREFIX}task_create} directive
    259 it enters the dormant state.  This state is not entered through
    260 any other means.  Although the task exists in the system, it
    261 cannot actively compete for system resources.  It will remain in
    262 the dormant state until it is started via the @code{@value{DIRPREFIX}task_start}
    263 directive, at which time it enters the ready state.  The task is
    264 now permitted to be scheduled for the processor and to compete
    265 for other system resources.
    266265
    267266A task occupies the blocked state whenever it is
Note: See TracChangeset for help on using the changeset viewer.