From d5e393115929dd892626fb4a3282cddc0d3d4548 Mon Sep 17 00:00:00 2001 From: cvs2git Date: Fri, 11 Feb 2000 15:54:48 +0000 Subject: This commit was manufactured by cvs2svn to create branch 'rtems-4-5-branch'. Sprout from master 2000-02-11 15:54:47 UTC Joel Sherrill 'Increased block size to 128 and added comments based on feedback from' Delete: c/src/ada-tests/mptests/mp01/config.h c/src/ada-tests/mptests/mp01/mp01.adb c/src/ada-tests/mptests/mp01/mptest.adb c/src/ada-tests/mptests/mp01/mptest.ads c/src/ada-tests/mptests/mp01/node1/mp01.scn c/src/ada-tests/mptests/mp01/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp01/node2/mp01.scn c/src/ada-tests/mptests/mp01/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp02/mptest.adb c/src/ada-tests/mptests/mp02/mptest.ads c/src/ada-tests/mptests/mp02/node1/mp02.scn c/src/ada-tests/mptests/mp02/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp02/node2/mp02.scn c/src/ada-tests/mptests/mp02/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp03/mptest.adb c/src/ada-tests/mptests/mp03/mptest.ads c/src/ada-tests/mptests/mp03/node1/mp03.scn c/src/ada-tests/mptests/mp03/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp03/node2/mp03.scn c/src/ada-tests/mptests/mp03/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp04/mptest.adb c/src/ada-tests/mptests/mp04/mptest.ads c/src/ada-tests/mptests/mp04/node1/mp04.scn c/src/ada-tests/mptests/mp04/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp04/node2/mp04.scn c/src/ada-tests/mptests/mp04/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp05/mptest.adb c/src/ada-tests/mptests/mp05/mptest.ads c/src/ada-tests/mptests/mp05/node1/mp05.scn c/src/ada-tests/mptests/mp05/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp05/node2/mp05.scn c/src/ada-tests/mptests/mp05/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp06/mptest.adb c/src/ada-tests/mptests/mp06/mptest.ads c/src/ada-tests/mptests/mp06/node1/mp06.scn c/src/ada-tests/mptests/mp06/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp06/node2/mp06.scn c/src/ada-tests/mptests/mp06/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp07/mptest.adb c/src/ada-tests/mptests/mp07/mptest.ads c/src/ada-tests/mptests/mp07/node1/mp07.scn c/src/ada-tests/mptests/mp07/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp07/node2/mp07.scn c/src/ada-tests/mptests/mp07/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp08/mptest.adb c/src/ada-tests/mptests/mp08/mptest.ads c/src/ada-tests/mptests/mp08/node1/mp08.scn c/src/ada-tests/mptests/mp08/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp08/node2/mp08.scn c/src/ada-tests/mptests/mp08/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp09/mptest.adb c/src/ada-tests/mptests/mp09/mptest.ads c/src/ada-tests/mptests/mp09/node1/mp09.scn c/src/ada-tests/mptests/mp09/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp09/node2/mp09.scn c/src/ada-tests/mptests/mp09/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp10/mptest.adb c/src/ada-tests/mptests/mp10/mptest.ads c/src/ada-tests/mptests/mp10/node1/mp10.scn c/src/ada-tests/mptests/mp10/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp10/node2/mp10.scn c/src/ada-tests/mptests/mp10/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp11/mptest.adb c/src/ada-tests/mptests/mp11/mptest.ads c/src/ada-tests/mptests/mp11/node1/mp11.scn c/src/ada-tests/mptests/mp11/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp11/node2/mp11.scn c/src/ada-tests/mptests/mp11/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp12/mptest.adb c/src/ada-tests/mptests/mp12/mptest.ads c/src/ada-tests/mptests/mp12/node1/mp12.scn c/src/ada-tests/mptests/mp12/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp12/node2/mp12.scn c/src/ada-tests/mptests/mp12/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp13/mptest.adb c/src/ada-tests/mptests/mp13/mptest.ads c/src/ada-tests/mptests/mp13/node1/mp13.scn c/src/ada-tests/mptests/mp13/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp13/node2/mp13.scn c/src/ada-tests/mptests/mp13/node2/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp14/mptest.adb c/src/ada-tests/mptests/mp14/mptest.ads c/src/ada-tests/mptests/mp14/node1/mp14.scn c/src/ada-tests/mptests/mp14/node1/mptest-per_node_configuration.adb c/src/ada-tests/mptests/mp14/node2/mp14.scn c/src/ada-tests/mptests/mp14/node2/mptest-per_node_configuration.adb c/src/ada-tests/samples/base_mp/mptest.adb c/src/ada-tests/samples/base_mp/mptest.ads c/src/ada-tests/samples/base_mp/node1/base_mp.scn c/src/ada-tests/samples/base_mp/node1/mptest-per_node_configuration.adb c/src/ada-tests/samples/base_mp/node2/base_mp.scn c/src/ada-tests/samples/base_mp/node2/mptest-per_node_configuration.adb c/src/ada-tests/samples/base_sp/base_sp.adb c/src/ada-tests/samples/base_sp/base_sp.scn c/src/ada-tests/samples/base_sp/config.h c/src/ada-tests/samples/base_sp/sptest.adb c/src/ada-tests/samples/base_sp/sptest.ads c/src/ada-tests/samples/hello/config.h c/src/ada-tests/samples/hello/hello.adb c/src/ada-tests/samples/hello/hello.scn c/src/ada-tests/samples/hello/sptest.adb c/src/ada-tests/samples/hello/sptest.ads c/src/ada-tests/samples/ticker/config.h c/src/ada-tests/samples/ticker/sptest.adb c/src/ada-tests/samples/ticker/sptest.ads c/src/ada-tests/samples/ticker/ticker.adb c/src/ada-tests/samples/ticker/ticker.scn c/src/ada-tests/sptests/sp01/config.h c/src/ada-tests/sptests/sp01/sp01.adb c/src/ada-tests/sptests/sp01/sp01.scn c/src/ada-tests/sptests/sp01/sptest.adb c/src/ada-tests/sptests/sp01/sptest.ads c/src/ada-tests/sptests/sp02/config.h c/src/ada-tests/sptests/sp02/sp02.adb c/src/ada-tests/sptests/sp02/sp02.scn c/src/ada-tests/sptests/sp02/sptest.adb c/src/ada-tests/sptests/sp02/sptest.ads c/src/ada-tests/sptests/sp03/config.h c/src/ada-tests/sptests/sp03/sp03.adb c/src/ada-tests/sptests/sp03/sp03.scn c/src/ada-tests/sptests/sp03/sptest.adb c/src/ada-tests/sptests/sp03/sptest.ads c/src/ada-tests/sptests/sp04/README c/src/ada-tests/sptests/sp04/config.h c/src/ada-tests/sptests/sp04/sp04.adb c/src/ada-tests/sptests/sp04/sp04.scn c/src/ada-tests/sptests/sp04/sptest.adb c/src/ada-tests/sptests/sp04/sptest.ads c/src/ada-tests/sptests/sp05/config.h c/src/ada-tests/sptests/sp05/sp05.adb c/src/ada-tests/sptests/sp05/sp05.scn c/src/ada-tests/sptests/sp05/sptest.adb c/src/ada-tests/sptests/sp05/sptest.ads c/src/ada-tests/sptests/sp06/config.h c/src/ada-tests/sptests/sp06/sp06.adb c/src/ada-tests/sptests/sp06/sp06.scn c/src/ada-tests/sptests/sp06/sptest.adb c/src/ada-tests/sptests/sp06/sptest.ads c/src/ada-tests/sptests/sp07/config.h c/src/ada-tests/sptests/sp07/sp07.adb c/src/ada-tests/sptests/sp07/sp07.scn c/src/ada-tests/sptests/sp07/sptest.adb c/src/ada-tests/sptests/sp07/sptest.ads c/src/ada-tests/sptests/sp08/config.h c/src/ada-tests/sptests/sp08/sp08.adb c/src/ada-tests/sptests/sp08/sp08.scn c/src/ada-tests/sptests/sp08/sptest.adb c/src/ada-tests/sptests/sp08/sptest.ads c/src/ada-tests/sptests/sp09/config.h c/src/ada-tests/sptests/sp09/sp09.adb c/src/ada-tests/sptests/sp09/sp09.scn c/src/ada-tests/sptests/sp09/sptest.adb c/src/ada-tests/sptests/sp09/sptest.ads c/src/ada-tests/sptests/sp11/config.h c/src/ada-tests/sptests/sp11/sp11.adb c/src/ada-tests/sptests/sp11/sp11.scn c/src/ada-tests/sptests/sp11/sptest.adb c/src/ada-tests/sptests/sp11/sptest.ads c/src/ada-tests/sptests/sp12/config.h c/src/ada-tests/sptests/sp12/sp12.adb c/src/ada-tests/sptests/sp12/sp12.scn c/src/ada-tests/sptests/sp12/sptest.adb c/src/ada-tests/sptests/sp12/sptest.ads c/src/ada-tests/sptests/sp13/config.h c/src/ada-tests/sptests/sp13/sp13.adb c/src/ada-tests/sptests/sp13/sp13.scn c/src/ada-tests/sptests/sp13/sptest.adb c/src/ada-tests/sptests/sp13/sptest.ads c/src/ada-tests/sptests/sp14/config.h c/src/ada-tests/sptests/sp14/sp14.adb c/src/ada-tests/sptests/sp14/sp14.scn c/src/ada-tests/sptests/sp14/sptest.adb c/src/ada-tests/sptests/sp14/sptest.ads c/src/ada-tests/sptests/sp15/config.h c/src/ada-tests/sptests/sp15/sp15.adb c/src/ada-tests/sptests/sp15/sp15.scn c/src/ada-tests/sptests/sp15/sptest.adb c/src/ada-tests/sptests/sp15/sptest.ads c/src/ada-tests/sptests/sp16/config.h c/src/ada-tests/sptests/sp16/sp16.adb c/src/ada-tests/sptests/sp16/sp16.scn c/src/ada-tests/sptests/sp16/sptest.adb c/src/ada-tests/sptests/sp16/sptest.ads c/src/ada-tests/sptests/sp17/config.h c/src/ada-tests/sptests/sp17/sp17.adb c/src/ada-tests/sptests/sp17/sp17.scn c/src/ada-tests/sptests/sp17/sptest.adb c/src/ada-tests/sptests/sp17/sptest.ads c/src/ada-tests/sptests/sp19/README c/src/ada-tests/sptests/sp19/config.h c/src/ada-tests/sptests/sp19/sp19.adb c/src/ada-tests/sptests/sp19/sp19.scn c/src/ada-tests/sptests/sp19/sptest.ads c/src/ada-tests/sptests/sp20/config.h c/src/ada-tests/sptests/sp20/sp20.adb c/src/ada-tests/sptests/sp20/sp20.scn c/src/ada-tests/sptests/sp20/sptest.adb c/src/ada-tests/sptests/sp20/sptest.ads c/src/ada-tests/sptests/sp21/config.h c/src/ada-tests/sptests/sp21/sp21.adb c/src/ada-tests/sptests/sp21/sp21.scn c/src/ada-tests/sptests/sp21/sptest.adb c/src/ada-tests/sptests/sp21/sptest.ads c/src/ada-tests/sptests/sp22/config.h c/src/ada-tests/sptests/sp22/sp22.adb c/src/ada-tests/sptests/sp22/sp22.scn c/src/ada-tests/sptests/sp22/sptest.adb c/src/ada-tests/sptests/sp22/sptest.ads c/src/ada-tests/sptests/sp23/config.h c/src/ada-tests/sptests/sp23/sp23.adb c/src/ada-tests/sptests/sp23/sp23.scn c/src/ada-tests/sptests/sp23/sptest.adb c/src/ada-tests/sptests/sp23/sptest.ads c/src/ada-tests/sptests/sp24/config.h c/src/ada-tests/sptests/sp24/sp24.adb c/src/ada-tests/sptests/sp24/sp24.scn c/src/ada-tests/sptests/sp24/sptest.adb c/src/ada-tests/sptests/sp24/sptest.ads c/src/ada-tests/sptests/sp25/config.h c/src/ada-tests/sptests/sp25/sp25.adb c/src/ada-tests/sptests/sp25/sp25.scn c/src/ada-tests/sptests/sp25/sptest.adb c/src/ada-tests/sptests/sp25/sptest.ads c/src/ada-tests/sptests/spsize/spsize.adb c/src/ada-tests/sptests/spsize/sptest.adb c/src/ada-tests/sptests/spsize/sptest.ads c/src/ada-tests/support/address_io.adb c/src/ada-tests/support/address_io.ads c/src/ada-tests/support/float_io.ads c/src/ada-tests/support/fp.inc c/src/ada-tests/support/init.c c/src/ada-tests/support/integer.inc c/src/ada-tests/support/rtems_calling_overhead.ads c/src/ada-tests/support/status_io.ads c/src/ada-tests/support/test_support.adb c/src/ada-tests/support/test_support.ads c/src/ada-tests/support/time_test_support.adb c/src/ada-tests/support/time_test_support.ads c/src/ada-tests/support/timer_driver.adb c/src/ada-tests/support/timer_driver.ads c/src/ada-tests/support/unsigned32_io.ads c/src/ada-tests/tmtests/tm01/config.h c/src/ada-tests/tmtests/tm01/tm01.adb c/src/ada-tests/tmtests/tm01/tmtest.adb c/src/ada-tests/tmtests/tm01/tmtest.ads c/src/ada-tests/tmtests/tm02/config.h c/src/ada-tests/tmtests/tm02/tm02.adb c/src/ada-tests/tmtests/tm02/tmtest.adb c/src/ada-tests/tmtests/tm02/tmtest.ads c/src/ada-tests/tmtests/tm03/config.h c/src/ada-tests/tmtests/tm03/tm03.adb c/src/ada-tests/tmtests/tm03/tmtest.adb c/src/ada-tests/tmtests/tm03/tmtest.ads c/src/ada-tests/tmtests/tm04/config.h c/src/ada-tests/tmtests/tm04/tm04.adb c/src/ada-tests/tmtests/tm04/tmtest.adb c/src/ada-tests/tmtests/tm04/tmtest.ads c/src/ada-tests/tmtests/tm05/config.h c/src/ada-tests/tmtests/tm05/tm05.adb c/src/ada-tests/tmtests/tm05/tmtest.adb c/src/ada-tests/tmtests/tm05/tmtest.ads c/src/ada-tests/tmtests/tm06/config.h c/src/ada-tests/tmtests/tm06/tm06.adb c/src/ada-tests/tmtests/tm06/tmtest.adb c/src/ada-tests/tmtests/tm06/tmtest.ads c/src/ada-tests/tmtests/tm07/config.h c/src/ada-tests/tmtests/tm07/tm07.adb c/src/ada-tests/tmtests/tm07/tmtest.adb c/src/ada-tests/tmtests/tm07/tmtest.ads c/src/ada-tests/tmtests/tm08/config.h c/src/ada-tests/tmtests/tm08/tm08.adb c/src/ada-tests/tmtests/tm08/tmtest.adb c/src/ada-tests/tmtests/tm08/tmtest.ads c/src/ada-tests/tmtests/tm09/config.h c/src/ada-tests/tmtests/tm09/tm09.adb c/src/ada-tests/tmtests/tm09/tmtest.adb c/src/ada-tests/tmtests/tm09/tmtest.ads c/src/ada-tests/tmtests/tm10/config.h c/src/ada-tests/tmtests/tm10/tm10.adb c/src/ada-tests/tmtests/tm10/tmtest.adb c/src/ada-tests/tmtests/tm10/tmtest.ads c/src/ada-tests/tmtests/tm11/config.h c/src/ada-tests/tmtests/tm11/tm11.adb c/src/ada-tests/tmtests/tm11/tmtest.adb c/src/ada-tests/tmtests/tm11/tmtest.ads c/src/ada-tests/tmtests/tm12/config.h c/src/ada-tests/tmtests/tm12/tm12.adb c/src/ada-tests/tmtests/tm12/tmtest.adb c/src/ada-tests/tmtests/tm12/tmtest.ads c/src/ada-tests/tmtests/tm13/config.h c/src/ada-tests/tmtests/tm13/tm13.adb c/src/ada-tests/tmtests/tm13/tmtest.adb c/src/ada-tests/tmtests/tm13/tmtest.ads c/src/ada-tests/tmtests/tm14/config.h c/src/ada-tests/tmtests/tm14/tm14.adb c/src/ada-tests/tmtests/tm14/tmtest.adb c/src/ada-tests/tmtests/tm14/tmtest.ads c/src/ada-tests/tmtests/tm15/config.h c/src/ada-tests/tmtests/tm15/tm15.adb c/src/ada-tests/tmtests/tm15/tmtest.adb c/src/ada-tests/tmtests/tm15/tmtest.ads c/src/ada-tests/tmtests/tm16/config.h c/src/ada-tests/tmtests/tm16/tm16.adb c/src/ada-tests/tmtests/tm16/tmtest.adb c/src/ada-tests/tmtests/tm16/tmtest.ads c/src/ada-tests/tmtests/tm17/config.h c/src/ada-tests/tmtests/tm17/tm17.adb c/src/ada-tests/tmtests/tm17/tmtest.adb c/src/ada-tests/tmtests/tm17/tmtest.ads c/src/ada-tests/tmtests/tm18/config.h c/src/ada-tests/tmtests/tm18/tm18.adb c/src/ada-tests/tmtests/tm18/tmtest.adb c/src/ada-tests/tmtests/tm18/tmtest.ads c/src/ada-tests/tmtests/tm19/config.h c/src/ada-tests/tmtests/tm19/tm19.adb c/src/ada-tests/tmtests/tm19/tmtest.adb c/src/ada-tests/tmtests/tm19/tmtest.ads c/src/ada-tests/tmtests/tm20/config.h c/src/ada-tests/tmtests/tm20/tm20.adb c/src/ada-tests/tmtests/tm20/tmtest.adb c/src/ada-tests/tmtests/tm20/tmtest.ads c/src/ada-tests/tmtests/tm21/config.h c/src/ada-tests/tmtests/tm21/tm21.adb c/src/ada-tests/tmtests/tm21/tmtest.adb c/src/ada-tests/tmtests/tm21/tmtest.ads c/src/ada-tests/tmtests/tm22/config.h c/src/ada-tests/tmtests/tm22/tm22.adb c/src/ada-tests/tmtests/tm22/tmtest.adb c/src/ada-tests/tmtests/tm22/tmtest.ads c/src/ada-tests/tmtests/tm23/config.h c/src/ada-tests/tmtests/tm23/tm23.adb c/src/ada-tests/tmtests/tm23/tmtest.adb c/src/ada-tests/tmtests/tm23/tmtest.ads c/src/ada-tests/tmtests/tm24/config.h c/src/ada-tests/tmtests/tm24/tm24.adb c/src/ada-tests/tmtests/tm24/tmtest.adb c/src/ada-tests/tmtests/tm24/tmtest.ads c/src/ada-tests/tmtests/tm25/config.h c/src/ada-tests/tmtests/tm25/tm25.adb c/src/ada-tests/tmtests/tm25/tmtest.adb c/src/ada-tests/tmtests/tm25/tmtest.ads c/src/ada-tests/tmtests/tm26/README c/src/ada-tests/tmtests/tm26/config.h c/src/ada-tests/tmtests/tm26/tm26.adb c/src/ada-tests/tmtests/tm26/tmtest.adp c/src/ada-tests/tmtests/tm26/tmtest.ads c/src/ada-tests/tmtests/tm27/README c/src/ada-tests/tmtests/tm27/config.h c/src/ada-tests/tmtests/tm27/tm27.adb c/src/ada-tests/tmtests/tm27/tmtest.adb c/src/ada-tests/tmtests/tm27/tmtest.ads c/src/ada-tests/tmtests/tm28/config.h c/src/ada-tests/tmtests/tm28/tm28.adb c/src/ada-tests/tmtests/tm28/tmtest.adb c/src/ada-tests/tmtests/tm28/tmtest.ads c/src/ada-tests/tmtests/tm29/config.h c/src/ada-tests/tmtests/tm29/tm29.adb c/src/ada-tests/tmtests/tm29/tmtest.adb c/src/ada-tests/tmtests/tm29/tmtest.ads c/src/ada-tests/tmtests/tmck/config.h c/src/ada-tests/tmtests/tmck/tmck.adb c/src/ada-tests/tmtests/tmck/tmtest.adb c/src/ada-tests/tmtests/tmck/tmtest.ads c/src/ada-tests/tmtests/tmoverhd/README c/src/ada-tests/tmtests/tmoverhd/config.h c/src/ada-tests/tmtests/tmoverhd/dummy_rtems.adb c/src/ada-tests/tmtests/tmoverhd/dummy_rtems.ads c/src/ada-tests/tmtests/tmoverhd/tmoverhd.adb c/src/ada-tests/tmtests/tmoverhd/tmtest.adb c/src/ada-tests/tmtests/tmoverhd/tmtest.ads c/src/ada/rtems.adb c/src/ada/rtems.ads c/src/exec/include/rtems/libio_.h c/src/exec/libcsupport/Makefile.am c/src/exec/libcsupport/include/chain.h c/src/exec/libcsupport/include/clockdrv.h c/src/exec/libcsupport/include/console.h c/src/exec/libcsupport/include/iosupp.h c/src/exec/libcsupport/include/motorola/mc68230.h c/src/exec/libcsupport/include/motorola/mc68681.h c/src/exec/libcsupport/include/ringbuf.h c/src/exec/libcsupport/include/rtems/assoc.h c/src/exec/libcsupport/include/rtems/error.h c/src/exec/libcsupport/include/rtems/libcsupport.h c/src/exec/libcsupport/include/rtems/libio.h c/src/exec/libcsupport/include/rtems/libio_.h c/src/exec/libcsupport/include/spurious.h c/src/exec/libcsupport/include/sys/filio.h c/src/exec/libcsupport/include/sys/ioctl.h c/src/exec/libcsupport/include/sys/sockio.h c/src/exec/libcsupport/include/sys/termios.h c/src/exec/libcsupport/include/sys/utime.h c/src/exec/libcsupport/include/sys/utsname.h c/src/exec/libcsupport/include/timerdrv.h c/src/exec/libcsupport/include/vmeintr.h c/src/exec/libcsupport/include/zilog/z8036.h c/src/exec/libcsupport/include/zilog/z8530.h c/src/exec/libcsupport/include/zilog/z8536.h c/src/exec/libcsupport/src/CASES c/src/exec/libcsupport/src/Makefile.am c/src/exec/libcsupport/src/README c/src/exec/libcsupport/src/TODO c/src/exec/libcsupport/src/__brk.c c/src/exec/libcsupport/src/__getpid.c c/src/exec/libcsupport/src/__gettod.c c/src/exec/libcsupport/src/__sbrk.c c/src/exec/libcsupport/src/__times.c c/src/exec/libcsupport/src/access.c c/src/exec/libcsupport/src/assoc.c c/src/exec/libcsupport/src/assocnamebad.c c/src/exec/libcsupport/src/base_fs.c c/src/exec/libcsupport/src/cfgetispeed.c c/src/exec/libcsupport/src/cfgetospeed.c c/src/exec/libcsupport/src/cfsetispeed.c c/src/exec/libcsupport/src/cfsetospeed.c c/src/exec/libcsupport/src/chdir.c c/src/exec/libcsupport/src/chmod.c c/src/exec/libcsupport/src/chown.c c/src/exec/libcsupport/src/close.c c/src/exec/libcsupport/src/closedir.c c/src/exec/libcsupport/src/creat.c c/src/exec/libcsupport/src/ctermid.c c/src/exec/libcsupport/src/dup.c c/src/exec/libcsupport/src/dup2.c c/src/exec/libcsupport/src/error.c c/src/exec/libcsupport/src/eval.c c/src/exec/libcsupport/src/fchmod.c c/src/exec/libcsupport/src/fcntl.c c/src/exec/libcsupport/src/fdatasync.c c/src/exec/libcsupport/src/fpathconf.c c/src/exec/libcsupport/src/fs_null_handlers.c c/src/exec/libcsupport/src/fstat.c c/src/exec/libcsupport/src/fsync.c c/src/exec/libcsupport/src/ftruncate.c c/src/exec/libcsupport/src/getcwd.c c/src/exec/libcsupport/src/getdents.c c/src/exec/libcsupport/src/getgrent.c c/src/exec/libcsupport/src/getpwent.c c/src/exec/libcsupport/src/hosterr.c c/src/exec/libcsupport/src/ioctl.c c/src/exec/libcsupport/src/isatty.c c/src/exec/libcsupport/src/libio.c c/src/exec/libcsupport/src/libio_sockets.c c/src/exec/libcsupport/src/link.c c/src/exec/libcsupport/src/lseek.c c/src/exec/libcsupport/src/lstat.c c/src/exec/libcsupport/src/malloc.c c/src/exec/libcsupport/src/mkdir.c c/src/exec/libcsupport/src/mkfifo.c c/src/exec/libcsupport/src/mknod.c c/src/exec/libcsupport/src/mount.c c/src/exec/libcsupport/src/newlibc.c c/src/exec/libcsupport/src/no_libc.c c/src/exec/libcsupport/src/no_posix.c c/src/exec/libcsupport/src/open.c c/src/exec/libcsupport/src/opendir.c c/src/exec/libcsupport/src/pathconf.c c/src/exec/libcsupport/src/pipe.c c/src/exec/libcsupport/src/read.c c/src/exec/libcsupport/src/readdir.c c/src/exec/libcsupport/src/readlink.c c/src/exec/libcsupport/src/rewinddir.c c/src/exec/libcsupport/src/rmdir.c c/src/exec/libcsupport/src/scandir.c c/src/exec/libcsupport/src/seekdir.c c/src/exec/libcsupport/src/stat.c c/src/exec/libcsupport/src/symlink.c c/src/exec/libcsupport/src/tcdrain.c c/src/exec/libcsupport/src/tcflow.c c/src/exec/libcsupport/src/tcflush.c c/src/exec/libcsupport/src/tcgetattr.c c/src/exec/libcsupport/src/tcgetprgrp.c c/src/exec/libcsupport/src/tcsendbreak.c c/src/exec/libcsupport/src/tcsetattr.c c/src/exec/libcsupport/src/tcsetpgrp.c c/src/exec/libcsupport/src/telldir.c c/src/exec/libcsupport/src/termios.c c/src/exec/libcsupport/src/termiosinitialize.c c/src/exec/libcsupport/src/termiosreserveresources.c c/src/exec/libcsupport/src/truncate.c c/src/exec/libcsupport/src/ttyname.c c/src/exec/libcsupport/src/ttyname_r.c c/src/exec/libcsupport/src/umask.c c/src/exec/libcsupport/src/unixlibc.c c/src/exec/libcsupport/src/unlink.c c/src/exec/libcsupport/src/unmount.c c/src/exec/libcsupport/src/utime.c c/src/exec/libcsupport/src/utsname.c c/src/exec/libcsupport/src/write.c c/src/exec/libfs/src/imfs/deviceio.c c/src/exec/libfs/src/imfs/imfs.h c/src/exec/libfs/src/imfs/imfs_chown.c c/src/exec/libfs/src/imfs/imfs_creat.c c/src/exec/libfs/src/imfs/imfs_debug.c c/src/exec/libfs/src/imfs/imfs_directory.c c/src/exec/libfs/src/imfs/imfs_eval.c c/src/exec/libfs/src/imfs/imfs_fchmod.c c/src/exec/libfs/src/imfs/imfs_fcntl.c c/src/exec/libfs/src/imfs/imfs_fdatasync.c c/src/exec/libfs/src/imfs/imfs_free.c c/src/exec/libfs/src/imfs/imfs_fsunmount.c c/src/exec/libfs/src/imfs/imfs_getchild.c c/src/exec/libfs/src/imfs/imfs_gtkn.c c/src/exec/libfs/src/imfs/imfs_handlers_device.c c/src/exec/libfs/src/imfs/imfs_handlers_directory.c c/src/exec/libfs/src/imfs/imfs_handlers_link.c c/src/exec/libfs/src/imfs/imfs_handlers_memfile.c c/src/exec/libfs/src/imfs/imfs_init.c c/src/exec/libfs/src/imfs/imfs_initsupp.c c/src/exec/libfs/src/imfs/imfs_link.c c/src/exec/libfs/src/imfs/imfs_mknod.c c/src/exec/libfs/src/imfs/imfs_mount.c c/src/exec/libfs/src/imfs/imfs_ntype.c c/src/exec/libfs/src/imfs/imfs_readlink.c c/src/exec/libfs/src/imfs/imfs_rmnod.c c/src/exec/libfs/src/imfs/imfs_stat.c c/src/exec/libfs/src/imfs/imfs_symlink.c c/src/exec/libfs/src/imfs/imfs_unixstub.c c/src/exec/libfs/src/imfs/imfs_unlink.c c/src/exec/libfs/src/imfs/imfs_unmount.c c/src/exec/libfs/src/imfs/imfs_utime.c c/src/exec/libfs/src/imfs/ioman.c c/src/exec/libfs/src/imfs/memfile.c c/src/exec/libfs/src/imfs/miniimfs_init.c c/src/exec/libnetworking/Makefile.am c/src/exec/libnetworking/README c/src/exec/libnetworking/arpa/Makefile.am c/src/exec/libnetworking/arpa/ftp.h c/src/exec/libnetworking/arpa/inet.h c/src/exec/libnetworking/arpa/nameser.h c/src/exec/libnetworking/arpa/nameser_compat.h c/src/exec/libnetworking/arpa/telnet.h c/src/exec/libnetworking/bpfilter.h c/src/exec/libnetworking/kern/Makefile.am c/src/exec/libnetworking/kern/kern_subr.c c/src/exec/libnetworking/kern/uipc_domain.c c/src/exec/libnetworking/kern/uipc_mbuf.c c/src/exec/libnetworking/kern/uipc_socket.c c/src/exec/libnetworking/kern/uipc_socket2.c c/src/exec/libnetworking/lib/Makefile.am c/src/exec/libnetworking/lib/README c/src/exec/libnetworking/lib/getprotoby.c c/src/exec/libnetworking/lib/rtems_bsdnet_ntp.c c/src/exec/libnetworking/lib/syslog.c c/src/exec/libnetworking/lib/tftpDriver.c c/src/exec/libnetworking/libc/Makefile.am c/src/exec/libnetworking/libc/addr2ascii.3 c/src/exec/libnetworking/libc/addr2ascii.c c/src/exec/libnetworking/libc/ascii2addr.c c/src/exec/libnetworking/libc/base64.c c/src/exec/libnetworking/libc/byteorder.3 c/src/exec/libnetworking/libc/ether_addr.c c/src/exec/libnetworking/libc/ethers.3 c/src/exec/libnetworking/libc/gethostbydns.c c/src/exec/libnetworking/libc/gethostbyht.c c/src/exec/libnetworking/libc/gethostbyname.3 c/src/exec/libnetworking/libc/gethostbynis.c c/src/exec/libnetworking/libc/gethostnamadr.c c/src/exec/libnetworking/libc/gethostname.c c/src/exec/libnetworking/libc/getnetbydns.c c/src/exec/libnetworking/libc/getnetbyht.c c/src/exec/libnetworking/libc/getnetbynis.c c/src/exec/libnetworking/libc/getnetent.3 c/src/exec/libnetworking/libc/getnetnamadr.c c/src/exec/libnetworking/libc/getproto.c c/src/exec/libnetworking/libc/getprotoent.3 c/src/exec/libnetworking/libc/getprotoent.c c/src/exec/libnetworking/libc/getprotoname.c c/src/exec/libnetworking/libc/getservbyname.c c/src/exec/libnetworking/libc/getservbyport.c c/src/exec/libnetworking/libc/getservent.3 c/src/exec/libnetworking/libc/getservent.c c/src/exec/libnetworking/libc/herror.c c/src/exec/libnetworking/libc/inet.3 c/src/exec/libnetworking/libc/inet_addr.c c/src/exec/libnetworking/libc/inet_lnaof.c c/src/exec/libnetworking/libc/inet_makeaddr.c c/src/exec/libnetworking/libc/inet_net_ntop.c c/src/exec/libnetworking/libc/inet_net_pton.c c/src/exec/libnetworking/libc/inet_neta.c c/src/exec/libnetworking/libc/inet_netof.c c/src/exec/libnetworking/libc/inet_network.c c/src/exec/libnetworking/libc/inet_ntoa.c c/src/exec/libnetworking/libc/inet_ntop.c c/src/exec/libnetworking/libc/inet_pton.c c/src/exec/libnetworking/libc/iso_addr.3 c/src/exec/libnetworking/libc/iso_addr.c c/src/exec/libnetworking/libc/linkaddr.3 c/src/exec/libnetworking/libc/linkaddr.c c/src/exec/libnetworking/libc/map_v4v6.c c/src/exec/libnetworking/libc/ns.3 c/src/exec/libnetworking/libc/ns_addr.c c/src/exec/libnetworking/libc/ns_name.c c/src/exec/libnetworking/libc/ns_netint.c c/src/exec/libnetworking/libc/ns_ntoa.c c/src/exec/libnetworking/libc/ns_parse.c c/src/exec/libnetworking/libc/ns_print.c c/src/exec/libnetworking/libc/ns_ttl.c c/src/exec/libnetworking/libc/nsap_addr.c c/src/exec/libnetworking/libc/rcmd.3 c/src/exec/libnetworking/libc/rcmd.c c/src/exec/libnetworking/libc/recv.c c/src/exec/libnetworking/libc/res_comp.c c/src/exec/libnetworking/libc/res_config.h c/src/exec/libnetworking/libc/res_data.c c/src/exec/libnetworking/libc/res_debug.c c/src/exec/libnetworking/libc/res_init.c c/src/exec/libnetworking/libc/res_mkquery.c c/src/exec/libnetworking/libc/res_mkupdate.c c/src/exec/libnetworking/libc/res_query.c c/src/exec/libnetworking/libc/res_send.c c/src/exec/libnetworking/libc/res_stubs.c c/src/exec/libnetworking/libc/res_update.c c/src/exec/libnetworking/libc/resolver.3 c/src/exec/libnetworking/libc/send.c c/src/exec/libnetworking/libc/strsep.c c/src/exec/libnetworking/loop.h c/src/exec/libnetworking/machine/Makefile.am c/src/exec/libnetworking/machine/conf.h c/src/exec/libnetworking/machine/cpu.h c/src/exec/libnetworking/machine/cpufunc.h c/src/exec/libnetworking/machine/endian.h c/src/exec/libnetworking/machine/in_cksum.h c/src/exec/libnetworking/machine/limits.h c/src/exec/libnetworking/machine/param.h c/src/exec/libnetworking/machine/types.h c/src/exec/libnetworking/machine/vmparam.h c/src/exec/libnetworking/net/Makefile.am c/src/exec/libnetworking/net/bpf.h c/src/exec/libnetworking/net/ethernet.h c/src/exec/libnetworking/net/if.c c/src/exec/libnetworking/net/if.h c/src/exec/libnetworking/net/if_arp.h c/src/exec/libnetworking/net/if_dl.h c/src/exec/libnetworking/net/if_ethersubr.c c/src/exec/libnetworking/net/if_llc.h c/src/exec/libnetworking/net/if_loop.c c/src/exec/libnetworking/net/if_ppp.h c/src/exec/libnetworking/net/if_types.h c/src/exec/libnetworking/net/netisr.h c/src/exec/libnetworking/net/ppp-comp.h c/src/exec/libnetworking/net/ppp_defs.h c/src/exec/libnetworking/net/radix.c c/src/exec/libnetworking/net/radix.h c/src/exec/libnetworking/net/raw_cb.c c/src/exec/libnetworking/net/raw_cb.h c/src/exec/libnetworking/net/raw_usrreq.c c/src/exec/libnetworking/net/route.c c/src/exec/libnetworking/net/route.h c/src/exec/libnetworking/net/rtsock.c c/src/exec/libnetworking/netdb.h c/src/exec/libnetworking/netinet/Makefile.am c/src/exec/libnetworking/netinet/icmp_var.h c/src/exec/libnetworking/netinet/if_ether.c c/src/exec/libnetworking/netinet/if_ether.h c/src/exec/libnetworking/netinet/igmp.c c/src/exec/libnetworking/netinet/igmp.h c/src/exec/libnetworking/netinet/igmp_var.h c/src/exec/libnetworking/netinet/in.c c/src/exec/libnetworking/netinet/in.h c/src/exec/libnetworking/netinet/in_cksum.c c/src/exec/libnetworking/netinet/in_cksum_i386.c c/src/exec/libnetworking/netinet/in_cksum_m68k.c c/src/exec/libnetworking/netinet/in_cksum_powerpc.c c/src/exec/libnetworking/netinet/in_pcb.c c/src/exec/libnetworking/netinet/in_pcb.h c/src/exec/libnetworking/netinet/in_proto.c c/src/exec/libnetworking/netinet/in_rmx.c c/src/exec/libnetworking/netinet/in_systm.h c/src/exec/libnetworking/netinet/in_var.h c/src/exec/libnetworking/netinet/ip.h c/src/exec/libnetworking/netinet/ip_divert.c c/src/exec/libnetworking/netinet/ip_fw.c c/src/exec/libnetworking/netinet/ip_fw.h c/src/exec/libnetworking/netinet/ip_icmp.c c/src/exec/libnetworking/netinet/ip_icmp.h c/src/exec/libnetworking/netinet/ip_input.c c/src/exec/libnetworking/netinet/ip_mroute.c c/src/exec/libnetworking/netinet/ip_mroute.h c/src/exec/libnetworking/netinet/ip_output.c c/src/exec/libnetworking/netinet/ip_var.h c/src/exec/libnetworking/netinet/raw_ip.c c/src/exec/libnetworking/netinet/tcp.h c/src/exec/libnetworking/netinet/tcp_debug.c c/src/exec/libnetworking/netinet/tcp_debug.h c/src/exec/libnetworking/netinet/tcp_fsm.h c/src/exec/libnetworking/netinet/tcp_input.c c/src/exec/libnetworking/netinet/tcp_output.c c/src/exec/libnetworking/netinet/tcp_seq.h c/src/exec/libnetworking/netinet/tcp_subr.c c/src/exec/libnetworking/netinet/tcp_timer.c c/src/exec/libnetworking/netinet/tcp_timer.h c/src/exec/libnetworking/netinet/tcp_usrreq.c c/src/exec/libnetworking/netinet/tcp_var.h c/src/exec/libnetworking/netinet/tcpip.h c/src/exec/libnetworking/netinet/udp.h c/src/exec/libnetworking/netinet/udp_usrreq.c c/src/exec/libnetworking/netinet/udp_var.h c/src/exec/libnetworking/nfs/Makefile.am c/src/exec/libnetworking/nfs/bootp_subr.c c/src/exec/libnetworking/nfs/krpc.h c/src/exec/libnetworking/nfs/nfs.h c/src/exec/libnetworking/nfs/nfsdiskless.h c/src/exec/libnetworking/nfs/nfsproto.h c/src/exec/libnetworking/nfs/rpcv2.h c/src/exec/libnetworking/nfs/xdr_subs.h c/src/exec/libnetworking/opt_ipfw.h c/src/exec/libnetworking/opt_mrouting.h c/src/exec/libnetworking/opt_tcpdebug.h c/src/exec/libnetworking/poll.h c/src/exec/libnetworking/resolv.h c/src/exec/libnetworking/rtems/Makefile.am c/src/exec/libnetworking/rtems/issetugid.c c/src/exec/libnetworking/rtems/rtems_bootp.c c/src/exec/libnetworking/rtems/rtems_bsdnet.h c/src/exec/libnetworking/rtems/rtems_bsdnet_internal.h c/src/exec/libnetworking/rtems/rtems_glue.c c/src/exec/libnetworking/rtems/rtems_select.c c/src/exec/libnetworking/rtems/rtems_showicmpstat.c c/src/exec/libnetworking/rtems/rtems_showifstat.c c/src/exec/libnetworking/rtems/rtems_showipstat.c c/src/exec/libnetworking/rtems/rtems_showmbuf.c c/src/exec/libnetworking/rtems/rtems_showroute.c c/src/exec/libnetworking/rtems/rtems_showtcpstat.c c/src/exec/libnetworking/rtems/rtems_showudpstat.c c/src/exec/libnetworking/rtems/rtems_syscall.c c/src/exec/libnetworking/rtems/sghostname.c c/src/exec/libnetworking/rtems/tftp.h c/src/exec/libnetworking/sys/Makefile.am c/src/exec/libnetworking/sys/buf.h c/src/exec/libnetworking/sys/callout.h c/src/exec/libnetworking/sys/conf.h c/src/exec/libnetworking/sys/domain.h c/src/exec/libnetworking/sys/kernel.h c/src/exec/libnetworking/sys/libkern.h c/src/exec/libnetworking/sys/malloc.h c/src/exec/libnetworking/sys/mbuf.h c/src/exec/libnetworking/sys/mount.h c/src/exec/libnetworking/sys/param.h c/src/exec/libnetworking/sys/proc.h c/src/exec/libnetworking/sys/protosw.h c/src/exec/libnetworking/sys/queue.h c/src/exec/libnetworking/sys/reboot.h c/src/exec/libnetworking/sys/resourcevar.h c/src/exec/libnetworking/sys/rtprio.h c/src/exec/libnetworking/sys/select.h c/src/exec/libnetworking/sys/signalvar.h c/src/exec/libnetworking/sys/socket.h c/src/exec/libnetworking/sys/socketvar.h c/src/exec/libnetworking/sys/sysctl.h c/src/exec/libnetworking/sys/syslimits.h c/src/exec/libnetworking/sys/syslog.h c/src/exec/libnetworking/sys/systm.h c/src/exec/libnetworking/sys/ttydefaults.h c/src/exec/libnetworking/sys/ucred.h c/src/exec/libnetworking/sys/uio.h c/src/exec/libnetworking/syslog.h c/src/exec/libnetworking/vm/Makefile.am c/src/exec/libnetworking/vm/vm.h c/src/exec/libnetworking/vm/vm_extern.h c/src/exec/libnetworking/vm/vm_kern.h c/src/exec/libnetworking/vm/vm_param.h c/src/exec/libnetworking/wrapup/Makefile.am c/src/exec/librpc/Makefile.am c/src/exec/librpc/include/Makefile.am c/src/exec/librpc/include/rpc/Makefile.am c/src/exec/librpc/include/rpc/auth.h c/src/exec/librpc/include/rpc/clnt.h c/src/exec/librpc/include/rpc/rpc.h c/src/exec/librpc/include/rpc/rpc_msg.h c/src/exec/librpc/include/rpc/svc.h c/src/exec/librpc/include/rpc/svc_auth.h c/src/exec/librpc/include/rpc/types.h c/src/exec/librpc/include/rpc/xdr.h c/src/exec/librpc/src/Makefile.am c/src/exec/score/cpu/a29k/rtems/score/types.h c/src/exec/score/cpu/hppa1.1/rtems/score/types.h c/src/exec/score/cpu/i386/rtems/score/types.h c/src/exec/score/cpu/i960/rtems/score/types.h c/src/exec/score/cpu/m68k/rtems/score/types.h c/src/exec/score/cpu/mips/Makefile.am c/src/exec/score/cpu/mips/asm.h c/src/exec/score/cpu/mips/configure.in c/src/exec/score/cpu/mips/cpu.c c/src/exec/score/cpu/mips/cpu_asm.S c/src/exec/score/cpu/mips/cpu_asm.h c/src/exec/score/cpu/mips/idtcpu.h c/src/exec/score/cpu/mips/idtmon.h c/src/exec/score/cpu/mips/iregdef.h c/src/exec/score/cpu/mips/rtems.c c/src/exec/score/cpu/mips/rtems/Makefile.am c/src/exec/score/cpu/mips/rtems/score/Makefile.am c/src/exec/score/cpu/mips/rtems/score/cpu.h c/src/exec/score/cpu/mips/rtems/score/mips.h c/src/exec/score/cpu/mips/rtems/score/mips64orion.h c/src/exec/score/cpu/mips/rtems/score/mipstypes.h c/src/exec/score/cpu/mips/rtems/score/types.h c/src/exec/score/cpu/mips64orion/rtems/score/types.h c/src/exec/score/cpu/no_cpu/rtems/score/types.h c/src/exec/score/cpu/powerpc/asm.h c/src/exec/score/cpu/powerpc/rtems/score/ppc.h c/src/exec/score/cpu/powerpc/rtems/score/ppctypes.h c/src/exec/score/cpu/powerpc/rtems/score/types.h c/src/exec/score/cpu/sh/rtems/score/types.h c/src/exec/score/cpu/sparc/rtems/score/types.h c/src/exec/score/cpu/unix/rtems/score/types.h c/src/lib/include/rtems/assoc.h c/src/lib/include/rtems/error.h c/src/lib/include/rtems/libcsupport.h c/src/lib/include/rtems/libio.h c/src/lib/include/rtems/libio_.h c/src/lib/include/sys/filio.h c/src/lib/include/sys/ioctl.h c/src/lib/include/sys/sockio.h c/src/lib/include/sys/utsname.h c/src/lib/libbsp/i386/shared/irq/idt.c c/src/lib/libbsp/m68k/ods68302/startup/cpuboot.c c/src/lib/libbsp/mips/Makefile.am c/src/lib/libbsp/mips/README c/src/lib/libbsp/mips/configure.in c/src/lib/libbsp/mips/p4000/Makefile.am c/src/lib/libbsp/mips/p4000/README c/src/lib/libbsp/mips/p4000/bsp_specs c/src/lib/libbsp/mips/p4000/configure.in c/src/lib/libbsp/mips/p4000/console/Makefile.am c/src/lib/libbsp/mips/p4000/console/console.c c/src/lib/libbsp/mips/p4000/console/led.S c/src/lib/libbsp/mips/p4000/include/Makefile.am c/src/lib/libbsp/mips/p4000/include/bsp.h c/src/lib/libbsp/mips/p4000/include/coverhd.h c/src/lib/libbsp/mips/p4000/liblnk/Makefile.am c/src/lib/libbsp/mips/p4000/liblnk/lnklib.S c/src/lib/libbsp/mips/p4000/start/Makefile.am c/src/lib/libbsp/mips/p4000/start/start.S c/src/lib/libbsp/mips/p4000/startup/Makefile.am c/src/lib/libbsp/mips/p4000/startup/bspclean.c c/src/lib/libbsp/mips/p4000/startup/bspstart.c c/src/lib/libbsp/mips/p4000/startup/ghlinkcmds c/src/lib/libbsp/mips/p4000/startup/idtmem.S c/src/lib/libbsp/mips/p4000/startup/idttlb.S c/src/lib/libbsp/mips/p4000/startup/inittlb.c c/src/lib/libbsp/mips/p4000/startup/linkcmds c/src/lib/libbsp/mips/p4000/startup/setvec.c c/src/lib/libbsp/mips/p4000/times c/src/lib/libbsp/mips/p4000/wrapup/Makefile.am c/src/lib/libbsp/powerpc/support/new_exception_processing/Makefile.am c/src/lib/libbsp/powerpc/support/new_exception_processing/c_isr.inl c/src/lib/libbsp/powerpc/support/new_exception_processing/cpu.c c/src/lib/libbsp/powerpc/support/new_exception_processing/cpu.h c/src/lib/libbsp/powerpc/support/new_exception_processing/cpu_asm.S c/src/lib/libbsp/powerpc/support/old_exception_processing/Makefile.am c/src/lib/libbsp/powerpc/support/old_exception_processing/README c/src/lib/libbsp/powerpc/support/old_exception_processing/TODO c/src/lib/libbsp/powerpc/support/old_exception_processing/c_isr.inl c/src/lib/libbsp/powerpc/support/old_exception_processing/cpu.c c/src/lib/libbsp/powerpc/support/old_exception_processing/cpu.h c/src/lib/libbsp/powerpc/support/old_exception_processing/cpu_asm.S c/src/lib/libbsp/powerpc/support/old_exception_processing/irq_stub.S c/src/lib/libbsp/powerpc/support/old_exception_processing/ppccache.c c/src/lib/libbsp/powerpc/support/old_exception_processing/rtems.S c/src/lib/libc/utsname.c c/src/lib/libcpu/i386/idt.c c/src/lib/libcpu/m68k/shared/misc/memcpy.c c/src/lib/libcpu/mips/Makefile.am c/src/lib/libcpu/mips/clock/Makefile.am c/src/lib/libcpu/mips/clock/ckinit.c c/src/lib/libcpu/mips/clock/clock.S c/src/lib/libcpu/mips/clock/clock.h c/src/lib/libcpu/mips/configure.in c/src/lib/libcpu/mips/timer/Makefile.am c/src/lib/libcpu/mips/timer/gettime.S c/src/lib/libcpu/mips/timer/timer.c c/src/lib/libcpu/powerpc/new-exceptions/cpu.c c/src/lib/libcpu/powerpc/new-exceptions/cpu_asm.S c/src/lib/libcpu/powerpc/new_exception_processing/Makefile.am c/src/lib/libcpu/powerpc/new_exception_processing/c_isr.inl c/src/lib/libcpu/powerpc/new_exception_processing/cpu.c c/src/lib/libcpu/powerpc/new_exception_processing/cpu.h c/src/lib/libcpu/powerpc/new_exception_processing/cpu_asm.S c/src/lib/libcpu/powerpc/old-exceptions/README c/src/lib/libcpu/powerpc/old-exceptions/TODO c/src/lib/libcpu/powerpc/old-exceptions/cpu.c c/src/lib/libcpu/powerpc/old-exceptions/cpu_asm.S c/src/lib/libcpu/powerpc/old-exceptions/irq_stub.S c/src/lib/libcpu/powerpc/old-exceptions/ppccache.c c/src/lib/libcpu/powerpc/old_exception_processing/Makefile.am c/src/lib/libcpu/powerpc/old_exception_processing/README c/src/lib/libcpu/powerpc/old_exception_processing/TODO c/src/lib/libcpu/powerpc/old_exception_processing/c_isr.inl c/src/lib/libcpu/powerpc/old_exception_processing/cpu.c c/src/lib/libcpu/powerpc/old_exception_processing/cpu.h c/src/lib/libcpu/powerpc/old_exception_processing/cpu_asm.S c/src/lib/libcpu/powerpc/old_exception_processing/irq_stub.S c/src/lib/libcpu/powerpc/old_exception_processing/rtems.S c/src/lib/libcpu/sh/sh7032/include/iosh7032.h c/src/lib/libcpu/sh/sh7032/include/ispsh7032.h c/src/lib/libcpu/sh/sh7032/score/cpu_asm.c c/src/lib/libcpu/sh/sh7032/score/ispsh7032.c c/src/lib/libcpu/sh/sh7045/include/io_types.h c/src/lib/libcpu/sh/sh7045/include/iosh7045.h c/src/lib/libcpu/sh/sh7045/include/ispsh7045.h c/src/lib/libcpu/sh/sh7045/score/cpu_asm.c c/src/lib/libcpu/sh/sh7045/score/ispsh7045.c c/src/lib/libcpu/sparc/include/erc32.h c/src/libchip/shmdr/README c/src/libchip/shmdr/addlq.c c/src/libchip/shmdr/cnvpkt.c c/src/libchip/shmdr/dump.c c/src/libchip/shmdr/fatal.c c/src/libchip/shmdr/getlq.c c/src/libchip/shmdr/getpkt.c c/src/libchip/shmdr/init.c c/src/libchip/shmdr/initlq.c c/src/libchip/shmdr/intr.c c/src/libchip/shmdr/mpci.h c/src/libchip/shmdr/mpisr.c c/src/libchip/shmdr/poll.c c/src/libchip/shmdr/receive.c c/src/libchip/shmdr/retpkt.c c/src/libchip/shmdr/send.c c/src/libchip/shmdr/setckvec.c c/src/libchip/shmdr/shm_driver.h c/src/libfs/src/imfs/deviceio.c c/src/libfs/src/imfs/imfs.h c/src/libfs/src/imfs/imfs_chown.c c/src/libfs/src/imfs/imfs_creat.c c/src/libfs/src/imfs/imfs_debug.c c/src/libfs/src/imfs/imfs_directory.c c/src/libfs/src/imfs/imfs_eval.c c/src/libfs/src/imfs/imfs_fchmod.c c/src/libfs/src/imfs/imfs_fcntl.c c/src/libfs/src/imfs/imfs_fdatasync.c c/src/libfs/src/imfs/imfs_free.c c/src/libfs/src/imfs/imfs_fsunmount.c c/src/libfs/src/imfs/imfs_getchild.c c/src/libfs/src/imfs/imfs_gtkn.c c/src/libfs/src/imfs/imfs_handlers_device.c c/src/libfs/src/imfs/imfs_handlers_directory.c c/src/libfs/src/imfs/imfs_handlers_link.c c/src/libfs/src/imfs/imfs_handlers_memfile.c c/src/libfs/src/imfs/imfs_init.c c/src/libfs/src/imfs/imfs_initsupp.c c/src/libfs/src/imfs/imfs_link.c c/src/libfs/src/imfs/imfs_mknod.c c/src/libfs/src/imfs/imfs_mount.c c/src/libfs/src/imfs/imfs_ntype.c c/src/libfs/src/imfs/imfs_readlink.c c/src/libfs/src/imfs/imfs_rmnod.c c/src/libfs/src/imfs/imfs_stat.c c/src/libfs/src/imfs/imfs_symlink.c c/src/libfs/src/imfs/imfs_unixstub.c c/src/libfs/src/imfs/imfs_unlink.c c/src/libfs/src/imfs/imfs_unmount.c c/src/libfs/src/imfs/imfs_utime.c c/src/libfs/src/imfs/ioman.c c/src/libfs/src/imfs/memfile.c c/src/libfs/src/imfs/miniimfs_init.c c/src/librdbg/src/powerpc/new_exception_processing/Makefile.am c/src/librdbg/src/powerpc/new_exception_processing/remdeb.h c/src/librdbg/src/powerpc/new_exception_processing/remdeb_f.x c/src/librdbg/src/powerpc/new_exception_processing/remdeb_svc.c c/src/librdbg/src/powerpc/new_exception_processing/remdeb_xdr.c c/src/make/README c/src/make/compilers/gcc-target-default.cfg c/src/make/directory.cfg c/src/make/host.cfg.in c/src/make/lib.cfg c/src/optman/rtems/Makefile.am c/src/optman/rtems/no-dpmem.c c/src/optman/rtems/no-event.c c/src/optman/rtems/no-mp.c c/src/optman/rtems/no-msg.c c/src/optman/rtems/no-part.c c/src/optman/rtems/no-region.c c/src/optman/rtems/no-rtmon.c c/src/optman/rtems/no-sem.c c/src/optman/rtems/no-signal.c c/src/optman/rtems/no-timer.c c/src/optman/sapi/Makefile.am c/src/optman/sapi/no-ext.c c/src/optman/sapi/no-io.c cpukit/Makefile.am cpukit/ada/rtems.adb cpukit/ada/rtems.ads cpukit/ftpd/Makefile.am cpukit/ftpd/ftpd.c cpukit/ftpd/ftpd.h cpukit/httpd/Makefile.am cpukit/httpd/asp.c cpukit/httpd/balloc.c cpukit/httpd/default.c cpukit/httpd/ej.h cpukit/httpd/ejlex.c cpukit/httpd/ejparse.c cpukit/httpd/form.c cpukit/httpd/h.c cpukit/httpd/handler.c cpukit/httpd/mime.c cpukit/httpd/misc.c cpukit/httpd/ringq.c cpukit/httpd/rom.c cpukit/httpd/rtems_webserver.h cpukit/httpd/security.c cpukit/httpd/socket.c cpukit/httpd/sym.c cpukit/httpd/uemf.c cpukit/httpd/uemf.h cpukit/httpd/url.c cpukit/httpd/value.c cpukit/httpd/wbase64.c cpukit/httpd/webcomp.c cpukit/httpd/webmain.c cpukit/httpd/webpage.c cpukit/httpd/webrom.c cpukit/httpd/webs.c cpukit/httpd/webs.h cpukit/httpd/websuemf.c cpukit/httpd/wsIntrn.h cpukit/include/rtems/libio_.h cpukit/itron/Makefile.am cpukit/itron/include/Makefile.am cpukit/itron/include/itron.h cpukit/itron/include/itronsys/README cpukit/itron/include/itronsys/eventflags.h cpukit/itron/include/itronsys/fmempool.h cpukit/itron/include/itronsys/intr.h cpukit/itron/include/itronsys/mbox.h cpukit/itron/include/itronsys/msgbuffer.h cpukit/itron/include/itronsys/network.h cpukit/itron/include/itronsys/port.h cpukit/itron/include/itronsys/semaphore.h cpukit/itron/include/itronsys/status.h cpukit/itron/include/itronsys/sysmgmt.h cpukit/itron/include/itronsys/task.h cpukit/itron/include/itronsys/time.h cpukit/itron/include/itronsys/types.h cpukit/itron/include/itronsys/vmempool.h cpukit/itron/include/rtems/itron/README cpukit/itron/include/rtems/itron/config.h cpukit/itron/include/rtems/itron/eventflags.h cpukit/itron/include/rtems/itron/fmempool.h cpukit/itron/include/rtems/itron/intr.h cpukit/itron/include/rtems/itron/itronapi.h cpukit/itron/include/rtems/itron/mbox.h cpukit/itron/include/rtems/itron/msgbuffer.h cpukit/itron/include/rtems/itron/network.h cpukit/itron/include/rtems/itron/object.h cpukit/itron/include/rtems/itron/port.h cpukit/itron/include/rtems/itron/semaphore.h cpukit/itron/include/rtems/itron/sysmgmt.h cpukit/itron/include/rtems/itron/task.h cpukit/itron/include/rtems/itron/time.h cpukit/itron/include/rtems/itron/vmempool.h cpukit/itron/inline/Makefile.am cpukit/itron/inline/rtems/itron/eventflags.inl cpukit/itron/inline/rtems/itron/fmempool.inl cpukit/itron/inline/rtems/itron/intr.inl cpukit/itron/inline/rtems/itron/mbox.inl cpukit/itron/inline/rtems/itron/msgbuffer.inl cpukit/itron/inline/rtems/itron/network.inl cpukit/itron/inline/rtems/itron/port.inl cpukit/itron/inline/rtems/itron/semaphore.inl cpukit/itron/inline/rtems/itron/sysmgmt.inl cpukit/itron/inline/rtems/itron/task.inl cpukit/itron/inline/rtems/itron/time.inl cpukit/itron/inline/rtems/itron/vmempool.inl cpukit/itron/src/Makefile.am cpukit/itron/src/TODO cpukit/itron/src/can_wup.c cpukit/itron/src/chg_pri.c cpukit/itron/src/cre_mbf.c cpukit/itron/src/cre_mbx.c cpukit/itron/src/cre_sem.c cpukit/itron/src/cre_tsk.c cpukit/itron/src/del_mbf.c cpukit/itron/src/del_mbx.c cpukit/itron/src/del_sem.c cpukit/itron/src/del_tsk.c cpukit/itron/src/dis_dsp.c cpukit/itron/src/ena_dsp.c cpukit/itron/src/eventflags.c cpukit/itron/src/exd_tsk.c cpukit/itron/src/ext_tsk.c cpukit/itron/src/fmempool.c cpukit/itron/src/frsm_tsk.c cpukit/itron/src/get_tid.c cpukit/itron/src/itronintr.c cpukit/itron/src/itronsem.c cpukit/itron/src/itrontime.c cpukit/itron/src/mbox.c cpukit/itron/src/mboxtranslatereturncode.c cpukit/itron/src/msgbuffer.c cpukit/itron/src/msgbuffertranslatereturncode.c cpukit/itron/src/network.c cpukit/itron/src/port.c cpukit/itron/src/prcv_mbf.c cpukit/itron/src/prcv_mbx.c cpukit/itron/src/preq_sem.c cpukit/itron/src/psnd_mbf.c cpukit/itron/src/rcv_mbf.c cpukit/itron/src/rcv_mbx.c cpukit/itron/src/ref_mbf.c cpukit/itron/src/ref_mbx.c cpukit/itron/src/ref_sem.c cpukit/itron/src/ref_tsk.c cpukit/itron/src/rel_wai.c cpukit/itron/src/rot_rdq.c cpukit/itron/src/rsm_tsk.c cpukit/itron/src/sig_sem.c cpukit/itron/src/slp_tsk.c cpukit/itron/src/snd_mbf.c cpukit/itron/src/snd_mbx.c cpukit/itron/src/sta_tsk.c cpukit/itron/src/sus_tsk.c cpukit/itron/src/sysmgmt.c cpukit/itron/src/task.c cpukit/itron/src/ter_tsk.c cpukit/itron/src/trcv_mbf.c cpukit/itron/src/trcv_mbx.c cpukit/itron/src/tslp_tsk.c cpukit/itron/src/tsnd_mbf.c cpukit/itron/src/twai_sem.c cpukit/itron/src/vmempool.c cpukit/itron/src/wai_sem.c cpukit/itron/src/wup_tsk.c cpukit/libcsupport/Makefile.am cpukit/libcsupport/include/chain.h cpukit/libcsupport/include/clockdrv.h cpukit/libcsupport/include/console.h cpukit/libcsupport/include/iosupp.h cpukit/libcsupport/include/motorola/mc68230.h cpukit/libcsupport/include/motorola/mc68681.h cpukit/libcsupport/include/ringbuf.h cpukit/libcsupport/include/rtems/assoc.h cpukit/libcsupport/include/rtems/error.h cpukit/libcsupport/include/rtems/libcsupport.h cpukit/libcsupport/include/rtems/libio.h cpukit/libcsupport/include/rtems/libio_.h cpukit/libcsupport/include/spurious.h cpukit/libcsupport/include/sys/filio.h cpukit/libcsupport/include/sys/ioctl.h cpukit/libcsupport/include/sys/sockio.h cpukit/libcsupport/include/sys/termios.h cpukit/libcsupport/include/sys/utime.h cpukit/libcsupport/include/sys/utsname.h cpukit/libcsupport/include/timerdrv.h cpukit/libcsupport/include/vmeintr.h cpukit/libcsupport/include/zilog/z8036.h cpukit/libcsupport/include/zilog/z8530.h cpukit/libcsupport/include/zilog/z8536.h cpukit/libcsupport/src/CASES cpukit/libcsupport/src/README cpukit/libcsupport/src/TODO cpukit/libcsupport/src/__brk.c cpukit/libcsupport/src/__getpid.c cpukit/libcsupport/src/__gettod.c cpukit/libcsupport/src/__sbrk.c cpukit/libcsupport/src/__times.c cpukit/libcsupport/src/access.c cpukit/libcsupport/src/assoc.c cpukit/libcsupport/src/assocnamebad.c cpukit/libcsupport/src/base_fs.c cpukit/libcsupport/src/cfgetispeed.c cpukit/libcsupport/src/cfgetospeed.c cpukit/libcsupport/src/cfsetispeed.c cpukit/libcsupport/src/cfsetospeed.c cpukit/libcsupport/src/chdir.c cpukit/libcsupport/src/chmod.c cpukit/libcsupport/src/chown.c cpukit/libcsupport/src/close.c cpukit/libcsupport/src/closedir.c cpukit/libcsupport/src/creat.c cpukit/libcsupport/src/ctermid.c cpukit/libcsupport/src/dup.c cpukit/libcsupport/src/dup2.c cpukit/libcsupport/src/error.c cpukit/libcsupport/src/eval.c cpukit/libcsupport/src/fchmod.c cpukit/libcsupport/src/fcntl.c cpukit/libcsupport/src/fdatasync.c cpukit/libcsupport/src/fpathconf.c cpukit/libcsupport/src/fs_null_handlers.c cpukit/libcsupport/src/fstat.c cpukit/libcsupport/src/fsync.c cpukit/libcsupport/src/ftruncate.c cpukit/libcsupport/src/getcwd.c cpukit/libcsupport/src/getdents.c cpukit/libcsupport/src/getgrent.c cpukit/libcsupport/src/getpwent.c cpukit/libcsupport/src/hosterr.c cpukit/libcsupport/src/ioctl.c cpukit/libcsupport/src/isatty.c cpukit/libcsupport/src/libio.c cpukit/libcsupport/src/libio_sockets.c cpukit/libcsupport/src/link.c cpukit/libcsupport/src/lseek.c cpukit/libcsupport/src/lstat.c cpukit/libcsupport/src/malloc.c cpukit/libcsupport/src/mkdir.c cpukit/libcsupport/src/mkfifo.c cpukit/libcsupport/src/mknod.c cpukit/libcsupport/src/mount.c cpukit/libcsupport/src/newlibc.c cpukit/libcsupport/src/no_libc.c cpukit/libcsupport/src/no_posix.c cpukit/libcsupport/src/open.c cpukit/libcsupport/src/opendir.c cpukit/libcsupport/src/pathconf.c cpukit/libcsupport/src/pipe.c cpukit/libcsupport/src/read.c cpukit/libcsupport/src/readdir.c cpukit/libcsupport/src/readlink.c cpukit/libcsupport/src/rewinddir.c cpukit/libcsupport/src/rmdir.c cpukit/libcsupport/src/scandir.c cpukit/libcsupport/src/seekdir.c cpukit/libcsupport/src/stat.c cpukit/libcsupport/src/symlink.c cpukit/libcsupport/src/tcdrain.c cpukit/libcsupport/src/tcflow.c cpukit/libcsupport/src/tcflush.c cpukit/libcsupport/src/tcgetattr.c cpukit/libcsupport/src/tcgetprgrp.c cpukit/libcsupport/src/tcsendbreak.c cpukit/libcsupport/src/tcsetattr.c cpukit/libcsupport/src/tcsetpgrp.c cpukit/libcsupport/src/telldir.c cpukit/libcsupport/src/termios.c cpukit/libcsupport/src/termiosinitialize.c cpukit/libcsupport/src/termiosreserveresources.c cpukit/libcsupport/src/truncate.c cpukit/libcsupport/src/ttyname.c cpukit/libcsupport/src/ttyname_r.c cpukit/libcsupport/src/umask.c cpukit/libcsupport/src/unixlibc.c cpukit/libcsupport/src/unlink.c cpukit/libcsupport/src/unmount.c cpukit/libcsupport/src/utime.c cpukit/libcsupport/src/utsname.c cpukit/libcsupport/src/write.c cpukit/libfs/src/imfs/deviceio.c cpukit/libfs/src/imfs/imfs.h cpukit/libfs/src/imfs/imfs_chown.c cpukit/libfs/src/imfs/imfs_creat.c cpukit/libfs/src/imfs/imfs_debug.c cpukit/libfs/src/imfs/imfs_directory.c cpukit/libfs/src/imfs/imfs_eval.c cpukit/libfs/src/imfs/imfs_fchmod.c cpukit/libfs/src/imfs/imfs_fcntl.c cpukit/libfs/src/imfs/imfs_fdatasync.c cpukit/libfs/src/imfs/imfs_free.c cpukit/libfs/src/imfs/imfs_fsunmount.c cpukit/libfs/src/imfs/imfs_getchild.c cpukit/libfs/src/imfs/imfs_gtkn.c cpukit/libfs/src/imfs/imfs_handlers_device.c cpukit/libfs/src/imfs/imfs_handlers_directory.c cpukit/libfs/src/imfs/imfs_handlers_link.c cpukit/libfs/src/imfs/imfs_handlers_memfile.c cpukit/libfs/src/imfs/imfs_init.c cpukit/libfs/src/imfs/imfs_initsupp.c cpukit/libfs/src/imfs/imfs_link.c cpukit/libfs/src/imfs/imfs_mknod.c cpukit/libfs/src/imfs/imfs_mount.c cpukit/libfs/src/imfs/imfs_ntype.c cpukit/libfs/src/imfs/imfs_readlink.c cpukit/libfs/src/imfs/imfs_rmnod.c cpukit/libfs/src/imfs/imfs_stat.c cpukit/libfs/src/imfs/imfs_symlink.c cpukit/libfs/src/imfs/imfs_unixstub.c cpukit/libfs/src/imfs/imfs_unlink.c cpukit/libfs/src/imfs/imfs_unmount.c cpukit/libfs/src/imfs/imfs_utime.c cpukit/libfs/src/imfs/ioman.c cpukit/libfs/src/imfs/memfile.c cpukit/libfs/src/imfs/miniimfs_init.c cpukit/libmisc/Makefile.am cpukit/libmisc/README cpukit/libmisc/cpuuse/Makefile.am cpukit/libmisc/cpuuse/README cpukit/libmisc/cpuuse/cpuuse.c cpukit/libmisc/cpuuse/cpuuse.h cpukit/libmisc/dummy/Makefile.am cpukit/libmisc/dummy/README cpukit/libmisc/dummy/dummy.c cpukit/libmisc/dumpbuf/Makefile.am cpukit/libmisc/dumpbuf/dumpbuf.c cpukit/libmisc/dumpbuf/dumpbuf.h cpukit/libmisc/monitor/Makefile.am cpukit/libmisc/monitor/README cpukit/libmisc/monitor/mon-command.c cpukit/libmisc/monitor/mon-config.c cpukit/libmisc/monitor/mon-dname.c cpukit/libmisc/monitor/mon-driver.c cpukit/libmisc/monitor/mon-extension.c cpukit/libmisc/monitor/mon-itask.c cpukit/libmisc/monitor/mon-manager.c cpukit/libmisc/monitor/mon-monitor.c cpukit/libmisc/monitor/mon-mpci.c cpukit/libmisc/monitor/mon-object.c cpukit/libmisc/monitor/mon-prmisc.c cpukit/libmisc/monitor/mon-queue.c cpukit/libmisc/monitor/mon-server.c cpukit/libmisc/monitor/mon-symbols.c cpukit/libmisc/monitor/mon-task.c cpukit/libmisc/monitor/monitor.h cpukit/libmisc/monitor/symbols.h cpukit/libmisc/rtmonuse/Makefile.am cpukit/libmisc/rtmonuse/rtmonuse.c cpukit/libmisc/rtmonuse/rtmonuse.h cpukit/libmisc/stackchk/Makefile.am cpukit/libmisc/stackchk/README cpukit/libmisc/stackchk/check.c cpukit/libmisc/stackchk/internal.h cpukit/libmisc/stackchk/stackchk.h cpukit/libmisc/untar/Makefile.am cpukit/libmisc/untar/README cpukit/libmisc/untar/untar.c cpukit/libmisc/untar/untar.h cpukit/libmisc/wrapup/Makefile.am cpukit/libnetworking/Makefile.am cpukit/libnetworking/README cpukit/libnetworking/arpa/Makefile.am cpukit/libnetworking/arpa/ftp.h cpukit/libnetworking/arpa/inet.h cpukit/libnetworking/arpa/nameser.h cpukit/libnetworking/arpa/nameser_compat.h cpukit/libnetworking/arpa/telnet.h cpukit/libnetworking/bpfilter.h cpukit/libnetworking/kern/Makefile.am cpukit/libnetworking/kern/kern_subr.c cpukit/libnetworking/kern/uipc_domain.c cpukit/libnetworking/kern/uipc_mbuf.c cpukit/libnetworking/kern/uipc_socket.c cpukit/libnetworking/kern/uipc_socket2.c cpukit/libnetworking/lib/Makefile.am cpukit/libnetworking/lib/README cpukit/libnetworking/lib/getprotoby.c cpukit/libnetworking/lib/rtems_bsdnet_ntp.c cpukit/libnetworking/lib/syslog.c cpukit/libnetworking/lib/tftpDriver.c cpukit/libnetworking/libc/Makefile.am cpukit/libnetworking/libc/addr2ascii.3 cpukit/libnetworking/libc/addr2ascii.c cpukit/libnetworking/libc/ascii2addr.c cpukit/libnetworking/libc/base64.c cpukit/libnetworking/libc/byteorder.3 cpukit/libnetworking/libc/ether_addr.c cpukit/libnetworking/libc/ethers.3 cpukit/libnetworking/libc/gethostbydns.c cpukit/libnetworking/libc/gethostbyht.c cpukit/libnetworking/libc/gethostbyname.3 cpukit/libnetworking/libc/gethostbynis.c cpukit/libnetworking/libc/gethostnamadr.c cpukit/libnetworking/libc/gethostname.c cpukit/libnetworking/libc/getnetbydns.c cpukit/libnetworking/libc/getnetbyht.c cpukit/libnetworking/libc/getnetbynis.c cpukit/libnetworking/libc/getnetent.3 cpukit/libnetworking/libc/getnetnamadr.c cpukit/libnetworking/libc/getproto.c cpukit/libnetworking/libc/getprotoent.3 cpukit/libnetworking/libc/getprotoent.c cpukit/libnetworking/libc/getprotoname.c cpukit/libnetworking/libc/getservbyname.c cpukit/libnetworking/libc/getservbyport.c cpukit/libnetworking/libc/getservent.3 cpukit/libnetworking/libc/getservent.c cpukit/libnetworking/libc/herror.c cpukit/libnetworking/libc/inet.3 cpukit/libnetworking/libc/inet_addr.c cpukit/libnetworking/libc/inet_lnaof.c cpukit/libnetworking/libc/inet_makeaddr.c cpukit/libnetworking/libc/inet_net_ntop.c cpukit/libnetworking/libc/inet_net_pton.c cpukit/libnetworking/libc/inet_neta.c cpukit/libnetworking/libc/inet_netof.c cpukit/libnetworking/libc/inet_network.c cpukit/libnetworking/libc/inet_ntoa.c cpukit/libnetworking/libc/inet_ntop.c cpukit/libnetworking/libc/inet_pton.c cpukit/libnetworking/libc/iso_addr.3 cpukit/libnetworking/libc/iso_addr.c cpukit/libnetworking/libc/linkaddr.3 cpukit/libnetworking/libc/linkaddr.c cpukit/libnetworking/libc/map_v4v6.c cpukit/libnetworking/libc/ns.3 cpukit/libnetworking/libc/ns_addr.c cpukit/libnetworking/libc/ns_name.c cpukit/libnetworking/libc/ns_netint.c cpukit/libnetworking/libc/ns_ntoa.c cpukit/libnetworking/libc/ns_parse.c cpukit/libnetworking/libc/ns_print.c cpukit/libnetworking/libc/ns_ttl.c cpukit/libnetworking/libc/nsap_addr.c cpukit/libnetworking/libc/rcmd.3 cpukit/libnetworking/libc/rcmd.c cpukit/libnetworking/libc/recv.c cpukit/libnetworking/libc/res_comp.c cpukit/libnetworking/libc/res_config.h cpukit/libnetworking/libc/res_data.c cpukit/libnetworking/libc/res_debug.c cpukit/libnetworking/libc/res_init.c cpukit/libnetworking/libc/res_mkquery.c cpukit/libnetworking/libc/res_mkupdate.c cpukit/libnetworking/libc/res_query.c cpukit/libnetworking/libc/res_send.c cpukit/libnetworking/libc/res_stubs.c cpukit/libnetworking/libc/res_update.c cpukit/libnetworking/libc/resolver.3 cpukit/libnetworking/libc/send.c cpukit/libnetworking/libc/strsep.c cpukit/libnetworking/loop.h cpukit/libnetworking/machine/Makefile.am cpukit/libnetworking/machine/conf.h cpukit/libnetworking/machine/cpu.h cpukit/libnetworking/machine/cpufunc.h cpukit/libnetworking/machine/endian.h cpukit/libnetworking/machine/in_cksum.h cpukit/libnetworking/machine/limits.h cpukit/libnetworking/machine/param.h cpukit/libnetworking/machine/types.h cpukit/libnetworking/machine/vmparam.h cpukit/libnetworking/net/Makefile.am cpukit/libnetworking/net/bpf.h cpukit/libnetworking/net/ethernet.h cpukit/libnetworking/net/if.c cpukit/libnetworking/net/if.h cpukit/libnetworking/net/if_arp.h cpukit/libnetworking/net/if_dl.h cpukit/libnetworking/net/if_ethersubr.c cpukit/libnetworking/net/if_llc.h cpukit/libnetworking/net/if_loop.c cpukit/libnetworking/net/if_ppp.h cpukit/libnetworking/net/if_types.h cpukit/libnetworking/net/netisr.h cpukit/libnetworking/net/ppp-comp.h cpukit/libnetworking/net/ppp_defs.h cpukit/libnetworking/net/radix.c cpukit/libnetworking/net/radix.h cpukit/libnetworking/net/raw_cb.c cpukit/libnetworking/net/raw_cb.h cpukit/libnetworking/net/raw_usrreq.c cpukit/libnetworking/net/route.c cpukit/libnetworking/net/route.h cpukit/libnetworking/net/rtsock.c cpukit/libnetworking/netdb.h cpukit/libnetworking/netinet/Makefile.am cpukit/libnetworking/netinet/icmp_var.h cpukit/libnetworking/netinet/if_ether.c cpukit/libnetworking/netinet/if_ether.h cpukit/libnetworking/netinet/igmp.c cpukit/libnetworking/netinet/igmp.h cpukit/libnetworking/netinet/igmp_var.h cpukit/libnetworking/netinet/in.c cpukit/libnetworking/netinet/in.h cpukit/libnetworking/netinet/in_cksum.c cpukit/libnetworking/netinet/in_cksum_i386.c cpukit/libnetworking/netinet/in_cksum_i386.h cpukit/libnetworking/netinet/in_cksum_m68k.c cpukit/libnetworking/netinet/in_cksum_m68k.h cpukit/libnetworking/netinet/in_cksum_powerpc.c cpukit/libnetworking/netinet/in_cksum_powerpc.h cpukit/libnetworking/netinet/in_pcb.c cpukit/libnetworking/netinet/in_pcb.h cpukit/libnetworking/netinet/in_proto.c cpukit/libnetworking/netinet/in_rmx.c cpukit/libnetworking/netinet/in_systm.h cpukit/libnetworking/netinet/in_var.h cpukit/libnetworking/netinet/ip.h cpukit/libnetworking/netinet/ip_divert.c cpukit/libnetworking/netinet/ip_fw.c cpukit/libnetworking/netinet/ip_fw.h cpukit/libnetworking/netinet/ip_icmp.c cpukit/libnetworking/netinet/ip_icmp.h cpukit/libnetworking/netinet/ip_input.c cpukit/libnetworking/netinet/ip_mroute.c cpukit/libnetworking/netinet/ip_mroute.h cpukit/libnetworking/netinet/ip_output.c cpukit/libnetworking/netinet/ip_var.h cpukit/libnetworking/netinet/raw_ip.c cpukit/libnetworking/netinet/tcp.h cpukit/libnetworking/netinet/tcp_debug.c cpukit/libnetworking/netinet/tcp_debug.h cpukit/libnetworking/netinet/tcp_fsm.h cpukit/libnetworking/netinet/tcp_input.c cpukit/libnetworking/netinet/tcp_output.c cpukit/libnetworking/netinet/tcp_seq.h cpukit/libnetworking/netinet/tcp_subr.c cpukit/libnetworking/netinet/tcp_timer.c cpukit/libnetworking/netinet/tcp_timer.h cpukit/libnetworking/netinet/tcp_usrreq.c cpukit/libnetworking/netinet/tcp_var.h cpukit/libnetworking/netinet/tcpip.h cpukit/libnetworking/netinet/udp.h cpukit/libnetworking/netinet/udp_usrreq.c cpukit/libnetworking/netinet/udp_var.h cpukit/libnetworking/nfs/Makefile.am cpukit/libnetworking/nfs/bootp_subr.c cpukit/libnetworking/nfs/krpc.h cpukit/libnetworking/nfs/nfs.h cpukit/libnetworking/nfs/nfsdiskless.h cpukit/libnetworking/nfs/nfsproto.h cpukit/libnetworking/nfs/rpcv2.h cpukit/libnetworking/nfs/xdr_subs.h cpukit/libnetworking/opt_ipfw.h cpukit/libnetworking/opt_mrouting.h cpukit/libnetworking/opt_tcpdebug.h cpukit/libnetworking/poll.h cpukit/libnetworking/resolv.h cpukit/libnetworking/rtems/Makefile.am cpukit/libnetworking/rtems/issetugid.c cpukit/libnetworking/rtems/rtems_bootp.c cpukit/libnetworking/rtems/rtems_bsdnet.h cpukit/libnetworking/rtems/rtems_bsdnet_internal.h cpukit/libnetworking/rtems/rtems_glue.c cpukit/libnetworking/rtems/rtems_select.c cpukit/libnetworking/rtems/rtems_showicmpstat.c cpukit/libnetworking/rtems/rtems_showifstat.c cpukit/libnetworking/rtems/rtems_showipstat.c cpukit/libnetworking/rtems/rtems_showmbuf.c cpukit/libnetworking/rtems/rtems_showroute.c cpukit/libnetworking/rtems/rtems_showtcpstat.c cpukit/libnetworking/rtems/rtems_showudpstat.c cpukit/libnetworking/rtems/rtems_syscall.c cpukit/libnetworking/rtems/sghostname.c cpukit/libnetworking/rtems/tftp.h cpukit/libnetworking/sys/Makefile.am cpukit/libnetworking/sys/buf.h cpukit/libnetworking/sys/callout.h cpukit/libnetworking/sys/conf.h cpukit/libnetworking/sys/domain.h cpukit/libnetworking/sys/kernel.h cpukit/libnetworking/sys/libkern.h cpukit/libnetworking/sys/malloc.h cpukit/libnetworking/sys/mbuf.h cpukit/libnetworking/sys/mount.h cpukit/libnetworking/sys/param.h cpukit/libnetworking/sys/proc.h cpukit/libnetworking/sys/protosw.h cpukit/libnetworking/sys/queue.h cpukit/libnetworking/sys/reboot.h cpukit/libnetworking/sys/resourcevar.h cpukit/libnetworking/sys/rtprio.h cpukit/libnetworking/sys/select.h cpukit/libnetworking/sys/signalvar.h cpukit/libnetworking/sys/socket.h cpukit/libnetworking/sys/socketvar.h cpukit/libnetworking/sys/sysctl.h cpukit/libnetworking/sys/syslimits.h cpukit/libnetworking/sys/syslog.h cpukit/libnetworking/sys/systm.h cpukit/libnetworking/sys/ttydefaults.h cpukit/libnetworking/sys/ucred.h cpukit/libnetworking/sys/uio.h cpukit/libnetworking/syslog.h cpukit/libnetworking/vm/Makefile.am cpukit/libnetworking/vm/vm.h cpukit/libnetworking/vm/vm_extern.h cpukit/libnetworking/vm/vm_kern.h cpukit/libnetworking/vm/vm_param.h cpukit/libnetworking/wrapup/Makefile.am cpukit/librpc/Makefile.am cpukit/librpc/include/Makefile.am cpukit/librpc/include/rpc/Makefile.am cpukit/librpc/include/rpc/auth.h cpukit/librpc/include/rpc/clnt.h cpukit/librpc/include/rpc/rpc.h cpukit/librpc/include/rpc/rpc_msg.h cpukit/librpc/include/rpc/svc.h cpukit/librpc/include/rpc/svc_auth.h cpukit/librpc/include/rpc/types.h cpukit/librpc/include/rpc/xdr.h cpukit/librpc/src/Makefile.am cpukit/posix/Makefile.am cpukit/posix/include/Makefile.am cpukit/posix/include/aio.h cpukit/posix/include/devctl.h cpukit/posix/include/intr.h cpukit/posix/include/mqueue.h cpukit/posix/include/rtems/posix/cancel.h cpukit/posix/include/rtems/posix/cond.h cpukit/posix/include/rtems/posix/condmp.h cpukit/posix/include/rtems/posix/config.h cpukit/posix/include/rtems/posix/intr.h cpukit/posix/include/rtems/posix/key.h cpukit/posix/include/rtems/posix/mqueue.h cpukit/posix/include/rtems/posix/mqueuemp.h cpukit/posix/include/rtems/posix/mutex.h cpukit/posix/include/rtems/posix/mutexmp.h cpukit/posix/include/rtems/posix/posixapi.h cpukit/posix/include/rtems/posix/priority.h cpukit/posix/include/rtems/posix/psignal.h cpukit/posix/include/rtems/posix/pthread.h cpukit/posix/include/rtems/posix/pthreadmp.h cpukit/posix/include/rtems/posix/ptimer.h cpukit/posix/include/rtems/posix/semaphore.h cpukit/posix/include/rtems/posix/semaphoremp.h cpukit/posix/include/rtems/posix/threadsup.h cpukit/posix/include/rtems/posix/time.h cpukit/posix/include/rtems/posix/timer.h cpukit/posix/include/sched.h cpukit/posix/include/semaphore.h cpukit/posix/inline/Makefile.am cpukit/posix/inline/rtems/posix/cond.inl cpukit/posix/inline/rtems/posix/intr.inl cpukit/posix/inline/rtems/posix/key.inl cpukit/posix/inline/rtems/posix/mqueue.inl cpukit/posix/inline/rtems/posix/mutex.inl cpukit/posix/inline/rtems/posix/priority.inl cpukit/posix/inline/rtems/posix/pthread.inl cpukit/posix/inline/rtems/posix/semaphore.inl cpukit/posix/macros/Makefile.am cpukit/posix/src/Makefile.am cpukit/posix/src/README.mqueue cpukit/posix/src/adasupp.c cpukit/posix/src/aio.c cpukit/posix/src/alarm.c cpukit/posix/src/cancel.c cpukit/posix/src/cancelrun.c cpukit/posix/src/cleanuppop.c cpukit/posix/src/cleanuppush.c cpukit/posix/src/clockgetcpuclockid.c cpukit/posix/src/clockgetenableattr.c cpukit/posix/src/clockgetres.c cpukit/posix/src/clockgettime.c cpukit/posix/src/clocksetenableattr.c cpukit/posix/src/clocksettime.c cpukit/posix/src/cond.c cpukit/posix/src/condattrdestroy.c cpukit/posix/src/condattrgetpshared.c cpukit/posix/src/condattrinit.c cpukit/posix/src/condattrsetpshared.c cpukit/posix/src/condbroadcast.c cpukit/posix/src/conddefaultattributes.c cpukit/posix/src/conddestroy.c cpukit/posix/src/condinit.c cpukit/posix/src/condmp.c cpukit/posix/src/condsignal.c cpukit/posix/src/condsignalsupp.c cpukit/posix/src/condtimedwait.c cpukit/posix/src/condwait.c cpukit/posix/src/condwaitsupp.c cpukit/posix/src/devctl.c cpukit/posix/src/execl.c cpukit/posix/src/execle.c cpukit/posix/src/execlp.c cpukit/posix/src/execv.c cpukit/posix/src/execve.c cpukit/posix/src/execvp.c cpukit/posix/src/fork.c cpukit/posix/src/getegid.c cpukit/posix/src/geteuid.c cpukit/posix/src/getgid.c cpukit/posix/src/getgroups.c cpukit/posix/src/getlogin.c cpukit/posix/src/getpgrp.c cpukit/posix/src/getpid.c cpukit/posix/src/getppid.c cpukit/posix/src/getuid.c cpukit/posix/src/intr.c cpukit/posix/src/key.c cpukit/posix/src/keycreate.c cpukit/posix/src/keydelete.c cpukit/posix/src/keygetspecific.c cpukit/posix/src/keyrundestructors.c cpukit/posix/src/keysetspecific.c cpukit/posix/src/kill.c cpukit/posix/src/killinfo.c cpukit/posix/src/mqueue.c cpukit/posix/src/mqueueclose.c cpukit/posix/src/mqueuecreatesupp.c cpukit/posix/src/mqueuedeletesupp.c cpukit/posix/src/mqueuegetattr.c cpukit/posix/src/mqueuenametoid.c cpukit/posix/src/mqueuenotify.c cpukit/posix/src/mqueueopen.c cpukit/posix/src/mqueuereceive.c cpukit/posix/src/mqueuerecvsupp.c cpukit/posix/src/mqueuesend.c cpukit/posix/src/mqueuesendsupp.c cpukit/posix/src/mqueuesetattr.c cpukit/posix/src/mqueuetimedreceive.c cpukit/posix/src/mqueuetimedsend.c cpukit/posix/src/mqueuetranslatereturncode.c cpukit/posix/src/mqueueunlink.c cpukit/posix/src/mutex.c cpukit/posix/src/mutexattrdestroy.c cpukit/posix/src/mutexattrgetprioceiling.c cpukit/posix/src/mutexattrgetprotocol.c cpukit/posix/src/mutexattrgetpshared.c cpukit/posix/src/mutexattrinit.c cpukit/posix/src/mutexattrsetprioceiling.c cpukit/posix/src/mutexattrsetprotocol.c cpukit/posix/src/mutexattrsetpshared.c cpukit/posix/src/mutexdefaultattributes.c cpukit/posix/src/mutexdestroy.c cpukit/posix/src/mutexfromcorestatus.c cpukit/posix/src/mutexgetprioceiling.c cpukit/posix/src/mutexinit.c cpukit/posix/src/mutexlock.c cpukit/posix/src/mutexlocksupp.c cpukit/posix/src/mutexmp.c cpukit/posix/src/mutexsetprioceiling.c cpukit/posix/src/mutextimedlock.c cpukit/posix/src/mutextrylock.c cpukit/posix/src/mutexunlock.c cpukit/posix/src/nanosleep.c cpukit/posix/src/pause.c cpukit/posix/src/posixintervaltotimespec.c cpukit/posix/src/posixtimespecsubtract.c cpukit/posix/src/posixtimespectointerval.c cpukit/posix/src/psignal.c cpukit/posix/src/psignalchecksignal.c cpukit/posix/src/psignalclearprocesssignals.c cpukit/posix/src/psignalclearsignals.c cpukit/posix/src/psignalsetprocesssignals.c cpukit/posix/src/psignalunblockthread.c cpukit/posix/src/pthread.c cpukit/posix/src/pthreadatfork.c cpukit/posix/src/pthreadattrdestroy.c cpukit/posix/src/pthreadattrgetdetachstate.c cpukit/posix/src/pthreadattrgetinheritsched.c cpukit/posix/src/pthreadattrgetschedparam.c cpukit/posix/src/pthreadattrgetschedpolicy.c cpukit/posix/src/pthreadattrgetscope.c cpukit/posix/src/pthreadattrgetstackaddr.c cpukit/posix/src/pthreadattrgetstacksize.c cpukit/posix/src/pthreadattrinit.c cpukit/posix/src/pthreadattrsetdetachstate.c cpukit/posix/src/pthreadattrsetinheritsched.c cpukit/posix/src/pthreadattrsetschedparam.c cpukit/posix/src/pthreadattrsetschedpolicy.c cpukit/posix/src/pthreadattrsetscope.c cpukit/posix/src/pthreadattrsetstackaddr.c cpukit/posix/src/pthreadattrsetstacksize.c cpukit/posix/src/pthreadcreate.c cpukit/posix/src/pthreaddetach.c cpukit/posix/src/pthreadequal.c cpukit/posix/src/pthreadexit.c cpukit/posix/src/pthreadgetcpuclockid.c cpukit/posix/src/pthreadgetcputime.c cpukit/posix/src/pthreadgetschedparam.c cpukit/posix/src/pthreadjoin.c cpukit/posix/src/pthreadkill.c cpukit/posix/src/pthreadonce.c cpukit/posix/src/pthreadself.c cpukit/posix/src/pthreadsetcputime.c cpukit/posix/src/pthreadsetschedparam.c cpukit/posix/src/pthreadsigmask.c cpukit/posix/src/ptimer.c cpukit/posix/src/ptimer1.c cpukit/posix/src/sched.c cpukit/posix/src/semaphore.c cpukit/posix/src/semaphorecreatesupp.c cpukit/posix/src/semaphoredeletesupp.c cpukit/posix/src/semaphoremp.c cpukit/posix/src/semaphorenametoid.c cpukit/posix/src/semaphorewaitsupp.c cpukit/posix/src/semclose.c cpukit/posix/src/semdestroy.c cpukit/posix/src/semgetvalue.c cpukit/posix/src/seminit.c cpukit/posix/src/semopen.c cpukit/posix/src/sempost.c cpukit/posix/src/semtimedwait.c cpukit/posix/src/semtrywait.c cpukit/posix/src/semunlink.c cpukit/posix/src/semwait.c cpukit/posix/src/setcancelstate.c cpukit/posix/src/setcanceltype.c cpukit/posix/src/setpgid.c cpukit/posix/src/setsid.c cpukit/posix/src/sigaction.c cpukit/posix/src/sigaddset.c cpukit/posix/src/sigdelset.c cpukit/posix/src/sigemptyset.c cpukit/posix/src/sigfillset.c cpukit/posix/src/sigismember.c cpukit/posix/src/signal_2.c cpukit/posix/src/sigpending.c cpukit/posix/src/sigprocmask.c cpukit/posix/src/sigqueue.c cpukit/posix/src/sigsuspend.c cpukit/posix/src/sigtimedwait.c cpukit/posix/src/sigwait.c cpukit/posix/src/sigwaitinfo.c cpukit/posix/src/sleep.c cpukit/posix/src/sysconf.c cpukit/posix/src/testcancel.c cpukit/posix/src/time.c cpukit/posix/src/types.c cpukit/posix/src/wait.c cpukit/posix/src/waitpid.c cpukit/pppd/Makefile.am cpukit/pppd/README cpukit/pppd/STATUS cpukit/pppd/auth.c cpukit/pppd/cbcp.c cpukit/pppd/cbcp.h cpukit/pppd/ccp.c cpukit/pppd/ccp.h cpukit/pppd/chap.c cpukit/pppd/chap.h cpukit/pppd/chap_ms.c cpukit/pppd/chap_ms.h cpukit/pppd/chat.c cpukit/pppd/demand.c cpukit/pppd/fsm.c cpukit/pppd/fsm.h cpukit/pppd/ipcp.c cpukit/pppd/ipcp.h cpukit/pppd/ipxcp.c cpukit/pppd/ipxcp.h cpukit/pppd/lcp.c cpukit/pppd/lcp.h cpukit/pppd/magic.c cpukit/pppd/magic.h cpukit/pppd/md4.c cpukit/pppd/md4.h cpukit/pppd/md5.c cpukit/pppd/md5.h cpukit/pppd/options.c cpukit/pppd/patchlevel.h cpukit/pppd/pathnames.h cpukit/pppd/pppd.h cpukit/pppd/upap.c cpukit/pppd/upap.h cpukit/rtems/Makefile.am cpukit/rtems/include/Makefile.am cpukit/rtems/include/rtems.h cpukit/rtems/include/rtems/rtems/asr.h cpukit/rtems/include/rtems/rtems/attr.h cpukit/rtems/include/rtems/rtems/clock.h cpukit/rtems/include/rtems/rtems/config.h cpukit/rtems/include/rtems/rtems/dpmem.h cpukit/rtems/include/rtems/rtems/event.h cpukit/rtems/include/rtems/rtems/eventmp.h cpukit/rtems/include/rtems/rtems/eventset.h cpukit/rtems/include/rtems/rtems/intr.h cpukit/rtems/include/rtems/rtems/message.h cpukit/rtems/include/rtems/rtems/modes.h cpukit/rtems/include/rtems/rtems/mp.h cpukit/rtems/include/rtems/rtems/msgmp.h cpukit/rtems/include/rtems/rtems/options.h cpukit/rtems/include/rtems/rtems/part.h cpukit/rtems/include/rtems/rtems/partmp.h cpukit/rtems/include/rtems/rtems/ratemon.h cpukit/rtems/include/rtems/rtems/region.h cpukit/rtems/include/rtems/rtems/regionmp.h cpukit/rtems/include/rtems/rtems/rtemsapi.h cpukit/rtems/include/rtems/rtems/sem.h cpukit/rtems/include/rtems/rtems/semmp.h cpukit/rtems/include/rtems/rtems/signal.h cpukit/rtems/include/rtems/rtems/signalmp.h cpukit/rtems/include/rtems/rtems/status.h cpukit/rtems/include/rtems/rtems/support.h cpukit/rtems/include/rtems/rtems/taskmp.h cpukit/rtems/include/rtems/rtems/tasks.h cpukit/rtems/include/rtems/rtems/timer.h cpukit/rtems/include/rtems/rtems/types.h cpukit/rtems/inline/Makefile.am cpukit/rtems/inline/rtems/rtems/asr.inl cpukit/rtems/inline/rtems/rtems/attr.inl cpukit/rtems/inline/rtems/rtems/dpmem.inl cpukit/rtems/inline/rtems/rtems/event.inl cpukit/rtems/inline/rtems/rtems/eventset.inl cpukit/rtems/inline/rtems/rtems/message.inl cpukit/rtems/inline/rtems/rtems/modes.inl cpukit/rtems/inline/rtems/rtems/options.inl cpukit/rtems/inline/rtems/rtems/part.inl cpukit/rtems/inline/rtems/rtems/ratemon.inl cpukit/rtems/inline/rtems/rtems/region.inl cpukit/rtems/inline/rtems/rtems/sem.inl cpukit/rtems/inline/rtems/rtems/status.inl cpukit/rtems/inline/rtems/rtems/support.inl cpukit/rtems/inline/rtems/rtems/tasks.inl cpukit/rtems/inline/rtems/rtems/timer.inl cpukit/rtems/macros/Makefile.am cpukit/rtems/macros/rtems/rtems/asr.inl cpukit/rtems/macros/rtems/rtems/attr.inl cpukit/rtems/macros/rtems/rtems/dpmem.inl cpukit/rtems/macros/rtems/rtems/event.inl cpukit/rtems/macros/rtems/rtems/eventset.inl cpukit/rtems/macros/rtems/rtems/message.inl cpukit/rtems/macros/rtems/rtems/modes.inl cpukit/rtems/macros/rtems/rtems/options.inl cpukit/rtems/macros/rtems/rtems/part.inl cpukit/rtems/macros/rtems/rtems/ratemon.inl cpukit/rtems/macros/rtems/rtems/region.inl cpukit/rtems/macros/rtems/rtems/sem.inl cpukit/rtems/macros/rtems/rtems/status.inl cpukit/rtems/macros/rtems/rtems/support.inl cpukit/rtems/macros/rtems/rtems/tasks.inl cpukit/rtems/macros/rtems/rtems/timer.inl cpukit/rtems/src/Makefile.am cpukit/rtems/src/attr.c cpukit/rtems/src/clockget.c cpukit/rtems/src/clockset.c cpukit/rtems/src/clocktick.c cpukit/rtems/src/clocktodtoseconds.c cpukit/rtems/src/clocktodvalidate.c cpukit/rtems/src/dpmem.c cpukit/rtems/src/dpmemcreate.c cpukit/rtems/src/dpmemdelete.c cpukit/rtems/src/dpmemexternal2internal.c cpukit/rtems/src/dpmemident.c cpukit/rtems/src/dpmeminternal2external.c cpukit/rtems/src/event.c cpukit/rtems/src/eventmp.c cpukit/rtems/src/eventreceive.c cpukit/rtems/src/eventseize.c cpukit/rtems/src/eventsend.c cpukit/rtems/src/eventsurrender.c cpukit/rtems/src/eventtimeout.c cpukit/rtems/src/intr.c cpukit/rtems/src/intrbody.c cpukit/rtems/src/intrcatch.c cpukit/rtems/src/mp.c cpukit/rtems/src/msg.c cpukit/rtems/src/msgmp.c cpukit/rtems/src/msgqallocate.c cpukit/rtems/src/msgqbroadcast.c cpukit/rtems/src/msgqcreate.c cpukit/rtems/src/msgqdelete.c cpukit/rtems/src/msgqflush.c cpukit/rtems/src/msgqgetnumberpending.c cpukit/rtems/src/msgqident.c cpukit/rtems/src/msgqreceive.c cpukit/rtems/src/msgqsend.c cpukit/rtems/src/msgqsubmit.c cpukit/rtems/src/msgqtranslatereturncode.c cpukit/rtems/src/msgqurgent.c cpukit/rtems/src/part.c cpukit/rtems/src/partcreate.c cpukit/rtems/src/partdelete.c cpukit/rtems/src/partgetbuffer.c cpukit/rtems/src/partident.c cpukit/rtems/src/partmp.c cpukit/rtems/src/partreturnbuffer.c cpukit/rtems/src/ratemon.c cpukit/rtems/src/ratemoncancel.c cpukit/rtems/src/ratemoncreate.c cpukit/rtems/src/ratemondelete.c cpukit/rtems/src/ratemongetstatus.c cpukit/rtems/src/ratemonident.c cpukit/rtems/src/ratemonperiod.c cpukit/rtems/src/ratemontimeout.c cpukit/rtems/src/region.c cpukit/rtems/src/regioncreate.c cpukit/rtems/src/regiondelete.c cpukit/rtems/src/regionextend.c cpukit/rtems/src/regiongetsegment.c cpukit/rtems/src/regiongetsegmentsize.c cpukit/rtems/src/regionident.c cpukit/rtems/src/regionmp.c cpukit/rtems/src/regionreturnsegment.c cpukit/rtems/src/rtclock.c cpukit/rtems/src/rtemstimer.c cpukit/rtems/src/sem.c cpukit/rtems/src/semcreate.c cpukit/rtems/src/semdelete.c cpukit/rtems/src/semflush.c cpukit/rtems/src/semident.c cpukit/rtems/src/semmp.c cpukit/rtems/src/semobtain.c cpukit/rtems/src/semrelease.c cpukit/rtems/src/semtranslatereturncode.c cpukit/rtems/src/signal.c cpukit/rtems/src/signalcatch.c cpukit/rtems/src/signalmp.c cpukit/rtems/src/signalsend.c cpukit/rtems/src/taskcreate.c cpukit/rtems/src/taskdelete.c cpukit/rtems/src/taskgetnote.c cpukit/rtems/src/taskident.c cpukit/rtems/src/taskinitusers.c cpukit/rtems/src/taskissuspended.c cpukit/rtems/src/taskmode.c cpukit/rtems/src/taskmp.c cpukit/rtems/src/taskrestart.c cpukit/rtems/src/taskresume.c cpukit/rtems/src/tasks.c cpukit/rtems/src/tasksetnote.c cpukit/rtems/src/tasksetpriority.c cpukit/rtems/src/taskstart.c cpukit/rtems/src/tasksuspend.c cpukit/rtems/src/taskvariableadd.c cpukit/rtems/src/taskvariabledelete.c cpukit/rtems/src/taskvariableget.c cpukit/rtems/src/taskwakeafter.c cpukit/rtems/src/taskwakewhen.c cpukit/rtems/src/timercancel.c cpukit/rtems/src/timercreate.c cpukit/rtems/src/timerdelete.c cpukit/rtems/src/timerfireafter.c cpukit/rtems/src/timerfirewhen.c cpukit/rtems/src/timerident.c cpukit/rtems/src/timerreset.c cpukit/sapi/Makefile.am cpukit/sapi/include/Makefile.am cpukit/sapi/include/confdefs.h cpukit/sapi/include/rtems/README cpukit/sapi/include/rtems/config.h cpukit/sapi/include/rtems/extension.h cpukit/sapi/include/rtems/fatal.h cpukit/sapi/include/rtems/init.h cpukit/sapi/include/rtems/io.h cpukit/sapi/include/rtems/mptables.h cpukit/sapi/include/rtems/sptables.h.in cpukit/sapi/inline/Makefile.am cpukit/sapi/inline/rtems/extension.inl cpukit/sapi/macros/Makefile.am cpukit/sapi/macros/rtems/extension.inl cpukit/sapi/src/Makefile.am cpukit/sapi/src/debug.c cpukit/sapi/src/exinit.c cpukit/sapi/src/extension.c cpukit/sapi/src/fatal.c cpukit/sapi/src/io.c cpukit/sapi/src/itronapi.c cpukit/sapi/src/posixapi.c cpukit/sapi/src/rtemsapi.c cpukit/score/Makefile.am cpukit/score/cpu/Makefile.am cpukit/score/cpu/a29k/Makefile.am cpukit/score/cpu/a29k/amd.ah cpukit/score/cpu/a29k/asm.h cpukit/score/cpu/a29k/cpu.c cpukit/score/cpu/a29k/cpu_asm.S cpukit/score/cpu/a29k/pswmacro.ah cpukit/score/cpu/a29k/register.ah cpukit/score/cpu/a29k/rtems/score/a29k.h cpukit/score/cpu/a29k/rtems/score/cpu.h cpukit/score/cpu/a29k/rtems/score/cpu_asm.h cpukit/score/cpu/a29k/rtems/score/types.h cpukit/score/cpu/a29k/sig.S cpukit/score/cpu/hppa1.1/Makefile.am cpukit/score/cpu/hppa1.1/cpu.c cpukit/score/cpu/hppa1.1/cpu_asm.S cpukit/score/cpu/hppa1.1/rtems/score/cpu.h cpukit/score/cpu/hppa1.1/rtems/score/cpu_asm.h cpukit/score/cpu/hppa1.1/rtems/score/hppa.h cpukit/score/cpu/hppa1.1/rtems/score/types.h cpukit/score/cpu/i386/Makefile.am cpukit/score/cpu/i386/asm.h cpukit/score/cpu/i386/cpu.c cpukit/score/cpu/i386/cpu_asm.S cpukit/score/cpu/i386/rtems/asm.h cpukit/score/cpu/i386/rtems/score/cpu.h cpukit/score/cpu/i386/rtems/score/i386.h cpukit/score/cpu/i386/rtems/score/types.h cpukit/score/cpu/i960/Makefile.am cpukit/score/cpu/i960/asm.h cpukit/score/cpu/i960/cpu.c cpukit/score/cpu/i960/cpu_asm.S cpukit/score/cpu/i960/rtems/score/cpu.h cpukit/score/cpu/i960/rtems/score/i960.h cpukit/score/cpu/i960/rtems/score/types.h cpukit/score/cpu/m68k/Makefile.am cpukit/score/cpu/m68k/asm.h cpukit/score/cpu/m68k/cpu.c cpukit/score/cpu/m68k/cpu_asm.S cpukit/score/cpu/m68k/m68302.h cpukit/score/cpu/m68k/m68360.h cpukit/score/cpu/m68k/memcpy.c cpukit/score/cpu/m68k/qsm.h cpukit/score/cpu/m68k/rtems/asm.h cpukit/score/cpu/m68k/rtems/m68k/m68302.h cpukit/score/cpu/m68k/rtems/m68k/m68360.h cpukit/score/cpu/m68k/rtems/m68k/qsm.h cpukit/score/cpu/m68k/rtems/m68k/sim.h cpukit/score/cpu/m68k/rtems/score/cpu.h cpukit/score/cpu/m68k/rtems/score/m68k.h cpukit/score/cpu/m68k/rtems/score/types.h cpukit/score/cpu/m68k/sim.h cpukit/score/cpu/mips/Makefile.am cpukit/score/cpu/mips/asm.h cpukit/score/cpu/mips/cpu.c cpukit/score/cpu/mips/cpu_asm.S cpukit/score/cpu/mips/idtcpu.h cpukit/score/cpu/mips/iregdef.h cpukit/score/cpu/mips/rtems/asm.h cpukit/score/cpu/mips/rtems/mips/idtcpu.h cpukit/score/cpu/mips/rtems/mips/iregdef.h cpukit/score/cpu/mips/rtems/score/cpu.h cpukit/score/cpu/mips/rtems/score/mips.h cpukit/score/cpu/mips/rtems/score/types.h cpukit/score/cpu/mips64orion/Makefile.am cpukit/score/cpu/mips64orion/asm.h cpukit/score/cpu/mips64orion/cpu.c cpukit/score/cpu/mips64orion/cpu_asm.S cpukit/score/cpu/mips64orion/cpu_asm.h cpukit/score/cpu/mips64orion/idtcpu.h cpukit/score/cpu/mips64orion/idtmon.h cpukit/score/cpu/mips64orion/iregdef.h cpukit/score/cpu/mips64orion/rtems/score/cpu.h cpukit/score/cpu/mips64orion/rtems/score/mips64orion.h cpukit/score/cpu/mips64orion/rtems/score/types.h cpukit/score/cpu/no_cpu/Makefile.am cpukit/score/cpu/no_cpu/asm.h cpukit/score/cpu/no_cpu/cpu.c cpukit/score/cpu/no_cpu/cpu_asm.c cpukit/score/cpu/no_cpu/rtems/asm.h cpukit/score/cpu/no_cpu/rtems/score/cpu.h cpukit/score/cpu/no_cpu/rtems/score/cpu_asm.h cpukit/score/cpu/no_cpu/rtems/score/no_cpu.h cpukit/score/cpu/no_cpu/rtems/score/types.h cpukit/score/cpu/powerpc/Makefile.am cpukit/score/cpu/powerpc/asm.h cpukit/score/cpu/powerpc/rtems/asm.h cpukit/score/cpu/powerpc/rtems/score/ppc.h cpukit/score/cpu/powerpc/rtems/score/types.h cpukit/score/cpu/sh/Makefile.am cpukit/score/cpu/sh/asm.h cpukit/score/cpu/sh/cpu.c cpukit/score/cpu/sh/rtems/asm.h cpukit/score/cpu/sh/rtems/score/cpu.h cpukit/score/cpu/sh/rtems/score/sh.h cpukit/score/cpu/sh/rtems/score/sh_io.h cpukit/score/cpu/sh/rtems/score/types.h cpukit/score/cpu/sparc/Makefile.am cpukit/score/cpu/sparc/README cpukit/score/cpu/sparc/asm.h cpukit/score/cpu/sparc/cpu.c cpukit/score/cpu/sparc/cpu_asm.S cpukit/score/cpu/sparc/rtems/asm.h cpukit/score/cpu/sparc/rtems/score/cpu.h cpukit/score/cpu/sparc/rtems/score/sparc.h cpukit/score/cpu/sparc/rtems/score/types.h cpukit/score/cpu/unix/Makefile.am cpukit/score/cpu/unix/cpu.c cpukit/score/cpu/unix/rtems/score/cpu.h cpukit/score/cpu/unix/rtems/score/types.h cpukit/score/cpu/unix/rtems/score/unix.h cpukit/score/include/Makefile.am cpukit/score/include/rtems/debug.h cpukit/score/include/rtems/score/address.h cpukit/score/include/rtems/score/apiext.h cpukit/score/include/rtems/score/bitfield.h cpukit/score/include/rtems/score/chain.h cpukit/score/include/rtems/score/context.h cpukit/score/include/rtems/score/copyrt.h cpukit/score/include/rtems/score/coremsg.h cpukit/score/include/rtems/score/coremutex.h cpukit/score/include/rtems/score/coresem.h cpukit/score/include/rtems/score/heap.h cpukit/score/include/rtems/score/interr.h cpukit/score/include/rtems/score/isr.h cpukit/score/include/rtems/score/mpci.h cpukit/score/include/rtems/score/mppkt.h cpukit/score/include/rtems/score/object.h cpukit/score/include/rtems/score/objectmp.h cpukit/score/include/rtems/score/priority.h cpukit/score/include/rtems/score/stack.h cpukit/score/include/rtems/score/states.h cpukit/score/include/rtems/score/sysstate.h cpukit/score/include/rtems/score/thread.h cpukit/score/include/rtems/score/threadmp.h cpukit/score/include/rtems/score/threadq.h cpukit/score/include/rtems/score/tod.h cpukit/score/include/rtems/score/tqdata.h cpukit/score/include/rtems/score/userext.h cpukit/score/include/rtems/score/watchdog.h cpukit/score/include/rtems/score/wkspace.h cpukit/score/include/rtems/system.h cpukit/score/inline/Makefile.am cpukit/score/inline/rtems/score/address.inl cpukit/score/inline/rtems/score/chain.inl cpukit/score/inline/rtems/score/coremsg.inl cpukit/score/inline/rtems/score/coremutex.inl cpukit/score/inline/rtems/score/coresem.inl cpukit/score/inline/rtems/score/heap.inl cpukit/score/inline/rtems/score/isr.inl cpukit/score/inline/rtems/score/mppkt.inl cpukit/score/inline/rtems/score/object.inl cpukit/score/inline/rtems/score/objectmp.inl cpukit/score/inline/rtems/score/priority.inl cpukit/score/inline/rtems/score/stack.inl cpukit/score/inline/rtems/score/states.inl cpukit/score/inline/rtems/score/sysstate.inl cpukit/score/inline/rtems/score/thread.inl cpukit/score/inline/rtems/score/threadmp.inl cpukit/score/inline/rtems/score/tod.inl cpukit/score/inline/rtems/score/tqdata.inl cpukit/score/inline/rtems/score/userext.inl cpukit/score/inline/rtems/score/watchdog.inl cpukit/score/inline/rtems/score/wkspace.inl cpukit/score/macros/Makefile.am cpukit/score/macros/README cpukit/score/macros/rtems/score/README cpukit/score/macros/rtems/score/address.inl cpukit/score/macros/rtems/score/chain.inl cpukit/score/macros/rtems/score/coremsg.inl cpukit/score/macros/rtems/score/coremutex.inl cpukit/score/macros/rtems/score/coresem.inl cpukit/score/macros/rtems/score/heap.inl cpukit/score/macros/rtems/score/isr.inl cpukit/score/macros/rtems/score/mppkt.inl cpukit/score/macros/rtems/score/object.inl cpukit/score/macros/rtems/score/objectmp.inl cpukit/score/macros/rtems/score/priority.inl cpukit/score/macros/rtems/score/stack.inl cpukit/score/macros/rtems/score/states.inl cpukit/score/macros/rtems/score/sysstate.inl cpukit/score/macros/rtems/score/thread.inl cpukit/score/macros/rtems/score/threadmp.inl cpukit/score/macros/rtems/score/tod.inl cpukit/score/macros/rtems/score/tqdata.inl cpukit/score/macros/rtems/score/userext.inl cpukit/score/macros/rtems/score/watchdog.inl cpukit/score/macros/rtems/score/wkspace.inl cpukit/score/src/Makefile.am cpukit/score/src/Unlimited.txt cpukit/score/src/apiext.c cpukit/score/src/chain.c cpukit/score/src/coremsg.c cpukit/score/src/coremsgbroadcast.c cpukit/score/src/coremsgclose.c cpukit/score/src/coremsgflush.c cpukit/score/src/coremsgflushsupp.c cpukit/score/src/coremsgflushwait.c cpukit/score/src/coremsginsert.c cpukit/score/src/coremsgseize.c cpukit/score/src/coremsgsubmit.c cpukit/score/src/coremutex.c cpukit/score/src/coremutexflush.c cpukit/score/src/coremutexseize.c cpukit/score/src/coremutexsurrender.c cpukit/score/src/coresem.c cpukit/score/src/coresemflush.c cpukit/score/src/coresemseize.c cpukit/score/src/coresemsurrender.c cpukit/score/src/coretod.c cpukit/score/src/coretodset.c cpukit/score/src/coretodtickle.c cpukit/score/src/coretodtoseconds.c cpukit/score/src/coretodvalidate.c cpukit/score/src/heap.c cpukit/score/src/heapallocate.c cpukit/score/src/heapextend.c cpukit/score/src/heapfree.c cpukit/score/src/heapsizeofuserarea.c cpukit/score/src/heapwalk.c cpukit/score/src/interr.c cpukit/score/src/isr.c cpukit/score/src/mpci.c cpukit/score/src/object.c cpukit/score/src/objectallocate.c cpukit/score/src/objectallocatebyindex.c cpukit/score/src/objectclearname.c cpukit/score/src/objectcomparenameraw.c cpukit/score/src/objectcomparenamestring.c cpukit/score/src/objectcopynameraw.c cpukit/score/src/objectcopynamestring.c cpukit/score/src/objectextendinformation.c cpukit/score/src/objectfree.c cpukit/score/src/objectget.c cpukit/score/src/objectgetbyindex.c cpukit/score/src/objectgetnext.c cpukit/score/src/objectinitializeinformation.c cpukit/score/src/objectmp.c cpukit/score/src/objectnametoid.c cpukit/score/src/objectshrinkinformation.c cpukit/score/src/thread.c cpukit/score/src/threadchangepriority.c cpukit/score/src/threadclearstate.c cpukit/score/src/threadclose.c cpukit/score/src/threadcreateidle.c cpukit/score/src/threaddelayended.c cpukit/score/src/threaddispatch.c cpukit/score/src/threadevaluatemode.c cpukit/score/src/threadget.c cpukit/score/src/threadhandler.c cpukit/score/src/threadidlebody.c cpukit/score/src/threadinitialize.c cpukit/score/src/threadloadenv.c cpukit/score/src/threadmp.c cpukit/score/src/threadq.c cpukit/score/src/threadqdequeue.c cpukit/score/src/threadqdequeuefifo.c cpukit/score/src/threadqdequeuepriority.c cpukit/score/src/threadqenqueue.c cpukit/score/src/threadqenqueuefifo.c cpukit/score/src/threadqenqueuepriority.c cpukit/score/src/threadqextract.c cpukit/score/src/threadqextractfifo.c cpukit/score/src/threadqextractpriority.c cpukit/score/src/threadqextractwithproxy.c cpukit/score/src/threadqfirst.c cpukit/score/src/threadqfirstfifo.c cpukit/score/src/threadqfirstpriority.c cpukit/score/src/threadqflush.c cpukit/score/src/threadqtimeout.c cpukit/score/src/threadready.c cpukit/score/src/threadreset.c cpukit/score/src/threadresettimeslice.c cpukit/score/src/threadrestart.c cpukit/score/src/threadresume.c cpukit/score/src/threadrotatequeue.c cpukit/score/src/threadsetpriority.c cpukit/score/src/threadsetstate.c cpukit/score/src/threadsettransient.c cpukit/score/src/threadstackallocate.c cpukit/score/src/threadstackfree.c cpukit/score/src/threadstart.c cpukit/score/src/threadstartmultitasking.c cpukit/score/src/threadsuspend.c cpukit/score/src/threadtickletimeslice.c cpukit/score/src/threadyieldprocessor.c cpukit/score/src/userext.c cpukit/score/src/watchdog.c cpukit/score/src/watchdogadjust.c cpukit/score/src/watchdoginsert.c cpukit/score/src/watchdogremove.c cpukit/score/src/watchdogtickle.c cpukit/score/src/wkspace.c cpukit/wrapup/Makefile.am cpukit/zlib/doc/rfc1950.txt cpukit/zlib/doc/rfc1951.txt cpukit/zlib/doc/rfc1952.txt doc/BAD.html doc/FAQ/FAQ.texi doc/FAQ/Makefile doc/FAQ/basic.t doc/FAQ/bsp.t doc/FAQ/concepts.t doc/FAQ/debug.t doc/FAQ/embeddedinfo.t doc/FAQ/endoftime.t doc/FAQ/entry doc/FAQ/freesw.t doc/FAQ/hwdebugaids.t doc/FAQ/projects.t doc/FAQ/tools.t doc/HELP.html doc/Make.config doc/Makefile doc/README doc/TODO doc/VERSION doc/ada_user/Makefile doc/ada_user/ada_user.texi doc/ada_user/example.texi doc/archgrey.gif doc/bsp_howto/Makefile doc/bsp_howto/adaintr.t doc/bsp_howto/analog.t doc/bsp_howto/bsp_howto.texi doc/bsp_howto/clock.t doc/bsp_howto/console.t doc/bsp_howto/discrete.t doc/bsp_howto/init.t doc/bsp_howto/intro.t doc/bsp_howto/linkcmds.t doc/bsp_howto/makefiles.t doc/bsp_howto/nvmem.t doc/bsp_howto/rtc.t doc/bsp_howto/shmsupp.t doc/bsp_howto/support.t doc/bsp_howto/target.t doc/bsp_howto/timer.t doc/common/cpright.texi doc/common/dvi.gif doc/common/oaronly.jpg doc/common/pdf.gif doc/common/pdf1.gif doc/common/ps.gif doc/common/setup.texi doc/common/timemac.texi doc/common/timetbl.t doc/common/timing.t doc/common/treedef.tex doc/common/up-arrow.gif doc/common/wksheets.t doc/develenv/Makefile doc/develenv/compile.texi doc/develenv/develenv.texi doc/develenv/direct.texi doc/develenv/intro.texi doc/develenv/sample.texi doc/develenv/utils.texi doc/do_docs doc/filesystem/Makefile doc/filesystem/filesystem.texi doc/filesystem/fsrequirements.t doc/filesystem/imfs.t doc/filesystem/init.t doc/filesystem/miniimfs.t doc/filesystem/mounting.t doc/filesystem/patheval.t doc/filesystem/preface.texi doc/filesystem/syscalls.t doc/filesystem/tftp.t doc/gnu_docs/Tool_Doc_Instructions doc/gnu_docs/gen_docs doc/gnu_docs/gnu_footer.html doc/gnu_docs/gnu_header.html doc/gnu_docs/index.html doc/gnu_docs/mk_install_dir doc/gnu_docs/refcard.html doc/gnu_docs/rtems_tools_index.html doc/index.html doc/itron3.0/Makefile doc/itron3.0/config.t doc/itron3.0/eventflags.t doc/itron3.0/fixedblock.t doc/itron3.0/gen_all doc/itron3.0/gen_section doc/itron3.0/gen_status_shell doc/itron3.0/interrupt.t doc/itron3.0/itron.texi doc/itron3.0/mailbox.t doc/itron3.0/memorypool.t doc/itron3.0/msgbuffer.t doc/itron3.0/network.t doc/itron3.0/preface.texi doc/itron3.0/rendezvous.t doc/itron3.0/semaphore.t doc/itron3.0/status.t doc/itron3.0/task.t doc/itron3.0/tasksync.t doc/itron3.0/time.t doc/networking/Makefile doc/networking/PCIreg.eps doc/networking/PCIreg.jpg doc/networking/PCIreg.pdf doc/networking/decdriver.t doc/networking/driver.t doc/networking/networkapp.t doc/networking/networkflow.eps doc/networking/networkflow.jpg doc/networking/networkflow.pdf doc/networking/networkflow.png doc/networking/networking.texi doc/networking/networktasks.t doc/networking/preface.texi doc/networking/recvbd.eps doc/networking/recvbd.jpg doc/networking/recvbd.pdf doc/networking/servers.t doc/networking/testing.t doc/new_chapters/Makefile doc/new_chapters/STATUS doc/new_chapters/TODO doc/new_chapters/adminiface.t doc/new_chapters/base.t doc/new_chapters/confspace.t doc/new_chapters/cpuuse.t doc/new_chapters/dumpcontrol.t doc/new_chapters/error.t doc/new_chapters/eventlog.t doc/new_chapters/gen_section doc/new_chapters/monitor.t doc/new_chapters/new_chapters.texi doc/new_chapters/rtmonuse.t doc/new_chapters/stackchk.t doc/oaronly.jpg doc/porting/Makefile doc/porting/codetuning.t doc/porting/cpuinit.t doc/porting/cpumodels.t doc/porting/developtools.t doc/porting/idlethread.t doc/porting/interrupts.t doc/porting/miscellaneous.t doc/porting/porting.texi doc/porting/preface.texi doc/porting/prioritybitmap.t doc/porting/sourcecode.t doc/porting/taskcontext.t doc/posix1003.1/Makefile doc/posix1003.1/ch01.t doc/posix1003.1/ch02.t doc/posix1003.1/ch03.t doc/posix1003.1/ch04.t doc/posix1003.1/ch05.t doc/posix1003.1/ch06.t doc/posix1003.1/ch07.t doc/posix1003.1/ch08.t doc/posix1003.1/ch09.t doc/posix1003.1/ch10.t doc/posix1003.1/ch11.t doc/posix1003.1/ch12.t doc/posix1003.1/ch13.t doc/posix1003.1/ch14.t doc/posix1003.1/ch15.t doc/posix1003.1/ch16.t doc/posix1003.1/ch17.t doc/posix1003.1/ch18.t doc/posix1003.1/posix1003_1.texi doc/posix1003.1/preface.texi doc/posix1003.1/summarize doc/posix_users/Makefile doc/posix_users/cancel.t doc/posix_users/clock.t doc/posix_users/cond.t doc/posix_users/cspecific.t doc/posix_users/device.t doc/posix_users/files.t doc/posix_users/gen_size_report doc/posix_users/io.t doc/posix_users/key.t doc/posix_users/libc.t doc/posix_users/libm.t doc/posix_users/memorymgmt.t doc/posix_users/message.t doc/posix_users/mutex.t doc/posix_users/posix_users.texi doc/posix_users/preface.texi doc/posix_users/procenv.t doc/posix_users/process.t doc/posix_users/sched.t doc/posix_users/semaphores.t doc/posix_users/signal.t doc/posix_users/status.t doc/posix_users/systemdb.t doc/posix_users/thread.t doc/posix_users/timer.t doc/relnotes/Makefile doc/relnotes/install.texi doc/relnotes/intro.texi doc/relnotes/probrep.texi doc/relnotes/relnotes.texi doc/relnotes/status.texi doc/rgdb_specs/Makefile doc/rgdb_specs/comm.t doc/rgdb_specs/conclusion.t doc/rgdb_specs/daemon.t doc/rgdb_specs/garde.eps doc/rgdb_specs/garde.pdf doc/rgdb_specs/gdbinternals.t doc/rgdb_specs/interfacing.t doc/rgdb_specs/intro.t doc/rgdb_specs/layers.eps doc/rgdb_specs/layers.jpg doc/rgdb_specs/layers.pdf doc/rgdb_specs/objectives.t doc/rgdb_specs/process.eps doc/rgdb_specs/process.jpg doc/rgdb_specs/process.pdf doc/rgdb_specs/revision.t doc/rgdb_specs/rgdb_specs.texi doc/rgdb_specs/seqbreak.eps doc/rgdb_specs/seqbreak.jpg doc/rgdb_specs/seqbreak.pdf doc/rgdb_specs/seqdetach.eps doc/rgdb_specs/seqdetach.jpg doc/rgdb_specs/seqdetach.pdf doc/rgdb_specs/seqinit.eps doc/rgdb_specs/seqinit.jpg doc/rgdb_specs/seqinit.pdf doc/rtems_footer.html doc/rtems_gdb/Makefile doc/rtems_gdb/commands.t doc/rtems_gdb/example.t doc/rtems_gdb/intro.t doc/rtems_gdb/rtems_gdb.texi doc/rtems_gdb/started.t doc/rtems_gdb/swarch.t doc/rtems_gdb/trouble.t doc/rtems_header.html doc/rtems_support.html doc/src2html/Makefile doc/src2html/RTEMS.test doc/started/Makefile doc/started/buildc.t doc/started/buildrt.t doc/started/gdb.t doc/started/intro.t doc/started/nt.t doc/started/pictures/bit_ada.jpg doc/started/pictures/bit_ada.vsd doc/started/pictures/bit_c.jpg doc/started/pictures/bit_c.vsd doc/started/pictures/scfile10.jpg doc/started/pictures/scfile10.vsd doc/started/pictures/scfile11.jpg doc/started/pictures/scfile11.vsd doc/started/pictures/scfile12.jpg doc/started/pictures/scfile12.vsd doc/started/pictures/scfile13.jpg doc/started/pictures/scfile13.vsd doc/started/pictures/scsfile1.jpg doc/started/pictures/scsfile1.vsd doc/started/pictures/scsfile2.jpg doc/started/pictures/scsfile2.vsd doc/started/pictures/scsfile3.jpg doc/started/pictures/scsfile3.vsd doc/started/pictures/scsfile4.jpg doc/started/pictures/scsfile4.vsd doc/started/pictures/scsfile5.jpg doc/started/pictures/scsfile5.vsd doc/started/pictures/scsfile6.jpg doc/started/pictures/scsfile6.vsd doc/started/pictures/scsfile7.jpg doc/started/pictures/scsfile7.vsd doc/started/pictures/scsfile8.jpg doc/started/pictures/scsfile8.vsd doc/started/pictures/scsfile9.jpg doc/started/pictures/scsfile9.vsd doc/started/pictures/sfile12c.jpg doc/started/pictures/sfile12c.vsd doc/started/require.t doc/started/sample.t doc/started/started.texi doc/started/versions.texi doc/started_ada/Makefile doc/started_ada/buildada.t doc/started_ada/buildrt.t doc/started_ada/gdb.t doc/started_ada/intro.t doc/started_ada/require.t doc/started_ada/sample.t doc/started_ada/started_ada.texi doc/started_ada/versions.texi doc/supplements/hppa1_1/Makefile doc/supplements/hppa1_1/SIMHPPA_TIMES doc/supplements/hppa1_1/bsp.t doc/supplements/hppa1_1/callconv.t doc/supplements/hppa1_1/cpumodel.t doc/supplements/hppa1_1/cputable.t doc/supplements/hppa1_1/fatalerr.t doc/supplements/hppa1_1/hppa1_1.texi doc/supplements/hppa1_1/intr_NOTIMES.t doc/supplements/hppa1_1/memmodel.t doc/supplements/hppa1_1/preface.texi doc/supplements/hppa1_1/timeSIMHPPA.t doc/supplements/i386/FORCE386_TIMES doc/supplements/i386/Makefile doc/supplements/i386/bsp.t doc/supplements/i386/callconv.t doc/supplements/i386/cpumodel.t doc/supplements/i386/cputable.t doc/supplements/i386/fatalerr.t doc/supplements/i386/i386.texi doc/supplements/i386/intr_NOTIMES.t doc/supplements/i386/memmodel.t doc/supplements/i386/preface.texi doc/supplements/i386/timeFORCE386.t doc/supplements/i960/CVME961_TIMES doc/supplements/i960/Makefile doc/supplements/i960/bsp.t doc/supplements/i960/callconv.t doc/supplements/i960/cpumodel.t doc/supplements/i960/cputable.t doc/supplements/i960/fatalerr.t doc/supplements/i960/i960.texi doc/supplements/i960/intr_NOTIMES.t doc/supplements/i960/memmodel.t doc/supplements/i960/preface.texi doc/supplements/i960/timeCVME961.t doc/supplements/m68k/MVME136_TIMES doc/supplements/m68k/Makefile doc/supplements/m68k/bsp.t doc/supplements/m68k/callconv.t doc/supplements/m68k/cpumodel.t doc/supplements/m68k/cputable.t doc/supplements/m68k/fatalerr.t doc/supplements/m68k/intr_NOTIMES.t doc/supplements/m68k/m68k.texi doc/supplements/m68k/memmodel.t doc/supplements/m68k/preface.texi doc/supplements/m68k/timeMVME136.t doc/supplements/m68k/timedata.t doc/supplements/mips64orion/BSP_TIMES doc/supplements/mips64orion/Makefile doc/supplements/mips64orion/bsp.t doc/supplements/mips64orion/callconv.t doc/supplements/mips64orion/cpumodel.t doc/supplements/mips64orion/cputable.t doc/supplements/mips64orion/fatalerr.t doc/supplements/mips64orion/intr_NOTIMES.t doc/supplements/mips64orion/memmodel.t doc/supplements/mips64orion/mips64orion.texi doc/supplements/mips64orion/preface.texi doc/supplements/mips64orion/timeBSP.t doc/supplements/powerpc/DMV177_TIMES doc/supplements/powerpc/Makefile doc/supplements/powerpc/PSIM_TIMES doc/supplements/powerpc/bsp.t doc/supplements/powerpc/callconv.t doc/supplements/powerpc/cpumodel.t doc/supplements/powerpc/cputable.t doc/supplements/powerpc/fatalerr.t doc/supplements/powerpc/intr_NOTIMES.t doc/supplements/powerpc/memmodel.t doc/supplements/powerpc/powerpc.texi doc/supplements/powerpc/preface.texi doc/supplements/powerpc/timeDMV177.t doc/supplements/powerpc/timePSIM.t doc/supplements/sh/BSP_TIMES doc/supplements/sh/Makefile doc/supplements/sh/bsp.t doc/supplements/sh/callconv.t doc/supplements/sh/cpumodel.t doc/supplements/sh/cputable.t doc/supplements/sh/fatalerr.t doc/supplements/sh/intr_NOTIMES.t doc/supplements/sh/memmodel.t doc/supplements/sh/preface.texi doc/supplements/sh/sh.texi doc/supplements/sh/timeBSP.t doc/supplements/sparc/ERC32_TIMES doc/supplements/sparc/Makefile doc/supplements/sparc/bsp.t doc/supplements/sparc/callconv.t doc/supplements/sparc/cpumodel.t doc/supplements/sparc/cputable.t doc/supplements/sparc/fatalerr.t doc/supplements/sparc/intr_NOTIMES.t doc/supplements/sparc/memmodel.t doc/supplements/sparc/preface.texi doc/supplements/sparc/sparc.texi doc/supplements/sparc/timeERC32.t doc/supplements/template/BSP_TIMES doc/supplements/template/Makefile doc/supplements/template/bsp.t doc/supplements/template/callconv.t doc/supplements/template/cpumodel.t doc/supplements/template/cputable.t doc/supplements/template/fatalerr.t doc/supplements/template/intr_NOTIMES.t doc/supplements/template/memmodel.t doc/supplements/template/preface.texi doc/supplements/template/template.texi doc/supplements/template/timeBSP.t doc/texinfo/texinfo.tex doc/tools/bmenu/Makefile doc/tools/bmenu/address.h doc/tools/bmenu/address.inl doc/tools/bmenu/base.h doc/tools/bmenu/chain.c doc/tools/bmenu/chain.h doc/tools/bmenu/chain.inl doc/tools/bmenu/isr.h doc/tools/bmenu/main.c doc/tools/bmenu/system.h doc/tools/pdl2texi/Makefile doc/tools/pdl2texi/address.h doc/tools/pdl2texi/address.inl doc/tools/pdl2texi/base.h doc/tools/pdl2texi/chain.c doc/tools/pdl2texi/chain.h doc/tools/pdl2texi/chain.inl doc/tools/pdl2texi/isr.h doc/tools/pdl2texi/main.c doc/tools/pdl2texi/s.d doc/tools/pdl2texi/sample.d doc/tools/pdl2texi/system.h doc/tools/pdl2texi/test_cases/enum.d doc/tools/pdl2texi/test_cases/enumbad.d doc/tools/pdl2texi/test_cases/table.d doc/tools/src2html/Makefile doc/tools/src2html1.4a/Ctags/C.c doc/tools/src2html1.4a/Ctags/Makefile doc/tools/src2html1.4a/Ctags/ctags.1 doc/tools/src2html1.4a/Ctags/ctags.c doc/tools/src2html1.4a/Ctags/ctags.h doc/tools/src2html1.4a/Ctags/fortran.c doc/tools/src2html1.4a/Ctags/lisp.c doc/tools/src2html1.4a/Ctags/print.c doc/tools/src2html1.4a/Ctags/strerror.c doc/tools/src2html1.4a/Ctags/tree.c doc/tools/src2html1.4a/Ctags/yacc.c doc/tools/src2html1.4a/Ctags/z.c doc/tools/src2html1.4a/FreeBSD/FreeBSD.hdr doc/tools/src2html1.4a/FreeBSD/FreeBSD.s2h doc/tools/src2html1.4a/FreeBSD/conf.hdr doc/tools/src2html1.4a/FreeBSD/ddb.hdr doc/tools/src2html1.4a/FreeBSD/i386.i386.hdr doc/tools/src2html1.4a/FreeBSD/i386.include.hdr doc/tools/src2html1.4a/FreeBSD/i386.isa.hdr doc/tools/src2html1.4a/FreeBSD/i386.stand.hdr doc/tools/src2html1.4a/FreeBSD/kern.hdr doc/tools/src2html1.4a/FreeBSD/net.hdr doc/tools/src2html1.4a/FreeBSD/netinet.hdr doc/tools/src2html1.4a/FreeBSD/nfs.hdr doc/tools/src2html1.4a/FreeBSD/stand.hdr doc/tools/src2html1.4a/FreeBSD/sys.hdr doc/tools/src2html1.4a/FreeBSD/ufs.hdr doc/tools/src2html1.4a/FreeBSD/vm.hdr doc/tools/src2html1.4a/Readme doc/tools/src2html1.4a/ctags-emacs/README doc/tools/src2html1.4a/ctags-emacs/ctags doc/tools/src2html1.4a/ctags-emacs/etags.c-ada-patch doc/tools/src2html1.4a/ctags-wr doc/tools/src2html1.4a/src2html doc/tools/src2html1.4a/src2html.1 doc/tools/src2html1.4a/src2html.cgi doc/tools/texi2www/Makefile doc/tools/texi2www/archive/texi2www-960103.tgz doc/tools/texi2www/dir-arrow.gif doc/tools/texi2www/missing-arrow.gif doc/tools/texi2www/next-arrow.gif doc/tools/texi2www/prev-arrow.gif doc/tools/texi2www/texi2dvi doc/tools/texi2www/texi2www doc/tools/texi2www/texi2www.texi doc/tools/texi2www/up-arrow.gif doc/tools/update doc/tools/word-replace doc/user/Makefile doc/user/bsp.t doc/user/c_user.texi doc/user/clock.t doc/user/concepts.t doc/user/conf.t doc/user/dirstat.texi doc/user/dpmem.t doc/user/event.t doc/user/example.texi doc/user/fatal.t doc/user/glossary.texi doc/user/init.t doc/user/intr.t doc/user/io.t doc/user/mp.t doc/user/msg.t doc/user/overview.t doc/user/part.t doc/user/preface.texi doc/user/region.t doc/user/rtemsarc.gif doc/user/rtemsarc.png doc/user/rtemspie.eps doc/user/rtemspie.gif doc/user/rtemspie.pdf doc/user/rtemspie.png doc/user/rtmon.t doc/user/schedule.t doc/user/sem.t doc/user/signal.t doc/user/states.eps doc/user/states.gif doc/user/states.pdf doc/user/states.png doc/user/task.t doc/user/timer.t doc/user/userext.t testsuites/Makefile.am testsuites/PROBLEMS testsuites/README testsuites/itrontests/Makefile.am testsuites/itrontests/README testsuites/itrontests/itronhello/Makefile.am testsuites/itrontests/itronhello/init.c testsuites/itrontests/itronhello/itronhello.doc testsuites/itrontests/itronhello/itronhello.scn testsuites/itrontests/itronhello/system.h testsuites/itrontests/itronmbf01/Makefile.am testsuites/itrontests/itronmbf01/init.c testsuites/itrontests/itronmbf01/itronmbf01.doc testsuites/itrontests/itronmbf01/itronmbf01.scn testsuites/itrontests/itronmbf01/system.h testsuites/itrontests/itronmbox01/Makefile.am testsuites/itrontests/itronmbox01/init.c testsuites/itrontests/itronmbox01/itronmbox01.doc testsuites/itrontests/itronmbox01/itronmbox01.scn testsuites/itrontests/itronmbox01/system.h testsuites/itrontests/itronsem01/Makefile.am testsuites/itrontests/itronsem01/init.c testsuites/itrontests/itronsem01/itronsem01.doc testsuites/itrontests/itronsem01/itronsem01.scn testsuites/itrontests/itronsem01/system.h testsuites/itrontests/itrontask01/Makefile.am testsuites/itrontests/itrontask01/init.c testsuites/itrontests/itrontask01/itrontask01.doc testsuites/itrontests/itrontask01/itrontask01.scn testsuites/itrontests/itrontask01/system.h testsuites/itrontests/itrontask01/task1.c testsuites/itrontests/itrontask02/Makefile.am testsuites/itrontests/itrontask02/dormant.c testsuites/itrontests/itrontask02/init.c testsuites/itrontests/itrontask02/itrontask02.doc testsuites/itrontests/itrontask02/itrontask02.scn testsuites/itrontests/itrontask02/system.h testsuites/itrontests/itrontask03/Makefile.am testsuites/itrontests/itrontask03/init.c testsuites/itrontests/itrontask03/itrontask03.doc testsuites/itrontests/itrontask03/itrontask03.scn testsuites/itrontests/itrontask03/preempt.c testsuites/itrontests/itrontask03/system.h testsuites/itrontests/itrontask03/task1.c testsuites/itrontests/itrontask03/task2.c testsuites/itrontests/itrontask03/task3.c testsuites/itrontests/itrontask04/Makefile.am testsuites/itrontests/itrontask04/init.c testsuites/itrontests/itrontask04/itrontask04.doc testsuites/itrontests/itrontask04/itrontask04.scn testsuites/itrontests/itrontask04/system.h testsuites/itrontests/itrontask04/task1.c testsuites/itrontests/itrontask04/task2.c testsuites/itrontests/itrontask04/task3.c testsuites/itrontests/itrontests.am testsuites/itrontests/itrontime01/Makefile.am testsuites/itrontests/itrontime01/init.c testsuites/itrontests/itrontime01/itrontime01.doc testsuites/itrontests/itrontime01/itrontime01.scn testsuites/itrontests/itrontime01/system.h testsuites/libtests/Makefile.am testsuites/libtests/README testsuites/libtests/cpuuse/Makefile.am testsuites/libtests/cpuuse/cpuuse.scn testsuites/libtests/cpuuse/init.c testsuites/libtests/cpuuse/system.h testsuites/libtests/cpuuse/task1.c testsuites/libtests/cpuuse/task2.c testsuites/libtests/cpuuse/task3.c testsuites/libtests/cpuuse/tswitch.c testsuites/libtests/libtests.am testsuites/libtests/malloctest/Makefile.am testsuites/libtests/malloctest/init.c testsuites/libtests/malloctest/system.h testsuites/libtests/malloctest/task1.c testsuites/libtests/monitor/Makefile.am testsuites/libtests/monitor/init.c testsuites/libtests/monitor/system.h testsuites/libtests/putenvtest/Makefile.am testsuites/libtests/putenvtest/init.c testsuites/libtests/rtems++/Init.cc testsuites/libtests/rtems++/Makefile.am testsuites/libtests/rtems++/System.h testsuites/libtests/rtems++/Task1.cc testsuites/libtests/rtems++/Task2.cc testsuites/libtests/rtems++/Task3.cc testsuites/libtests/rtems++/rtems++.doc testsuites/libtests/rtems++/rtems++.scn testsuites/libtests/rtmonuse/Makefile.am testsuites/libtests/rtmonuse/getall.c testsuites/libtests/rtmonuse/init.c testsuites/libtests/rtmonuse/rtmonuse.scn testsuites/libtests/rtmonuse/system.h testsuites/libtests/rtmonuse/task1.c testsuites/libtests/stackchk/Makefile.am testsuites/libtests/stackchk/blow.c testsuites/libtests/stackchk/init.c testsuites/libtests/stackchk/stackchk.scn testsuites/libtests/stackchk/system.h testsuites/libtests/stackchk/task1.c testsuites/libtests/termios/Makefile.am testsuites/libtests/termios/README testsuites/libtests/termios/init.c testsuites/mptests/Makefile.am testsuites/mptests/README testsuites/mptests/mp01/Makefile.am testsuites/mptests/mp01/init.c testsuites/mptests/mp01/node1/Makefile.am testsuites/mptests/mp01/node1/mp01.doc testsuites/mptests/mp01/node1/mp01.scn testsuites/mptests/mp01/node2/Makefile.am testsuites/mptests/mp01/node2/mp01.doc testsuites/mptests/mp01/node2/mp01.scn testsuites/mptests/mp01/system.h testsuites/mptests/mp01/task1.c testsuites/mptests/mp02/Makefile.am testsuites/mptests/mp02/init.c testsuites/mptests/mp02/node1/Makefile.am testsuites/mptests/mp02/node1/mp02.doc testsuites/mptests/mp02/node1/mp02.scn testsuites/mptests/mp02/node2/Makefile.am testsuites/mptests/mp02/node2/mp02.doc testsuites/mptests/mp02/node2/mp02.scn testsuites/mptests/mp02/system.h testsuites/mptests/mp02/task1.c testsuites/mptests/mp03/Makefile.am testsuites/mptests/mp03/delay.c testsuites/mptests/mp03/init.c testsuites/mptests/mp03/node1/Makefile.am testsuites/mptests/mp03/node1/mp03.doc testsuites/mptests/mp03/node1/mp03.scn testsuites/mptests/mp03/node2/Makefile.am testsuites/mptests/mp03/node2/mp03.doc testsuites/mptests/mp03/node2/mp03.scn testsuites/mptests/mp03/system.h testsuites/mptests/mp03/task1.c testsuites/mptests/mp04/Makefile.am testsuites/mptests/mp04/init.c testsuites/mptests/mp04/node1/Makefile.am testsuites/mptests/mp04/node1/mp04.doc testsuites/mptests/mp04/node1/mp04.scn testsuites/mptests/mp04/node2/Makefile.am testsuites/mptests/mp04/node2/mp04.doc testsuites/mptests/mp04/node2/mp04.scn testsuites/mptests/mp04/system.h testsuites/mptests/mp04/task1.c testsuites/mptests/mp05/Makefile.am testsuites/mptests/mp05/asr.c testsuites/mptests/mp05/init.c testsuites/mptests/mp05/node1/Makefile.am testsuites/mptests/mp05/node1/mp05.doc testsuites/mptests/mp05/node1/mp05.scn testsuites/mptests/mp05/node2/Makefile.am testsuites/mptests/mp05/node2/mp05.doc testsuites/mptests/mp05/node2/mp05.scn testsuites/mptests/mp05/system.h testsuites/mptests/mp05/task1.c testsuites/mptests/mp06/Makefile.am testsuites/mptests/mp06/init.c testsuites/mptests/mp06/node1/Makefile.am testsuites/mptests/mp06/node1/mp06.doc testsuites/mptests/mp06/node1/mp06.scn testsuites/mptests/mp06/node2/Makefile.am testsuites/mptests/mp06/node2/mp06.doc testsuites/mptests/mp06/node2/mp06.scn testsuites/mptests/mp06/system.h testsuites/mptests/mp06/task1.c testsuites/mptests/mp07/Makefile.am testsuites/mptests/mp07/init.c testsuites/mptests/mp07/node1/Makefile.am testsuites/mptests/mp07/node1/mp07.doc testsuites/mptests/mp07/node1/mp07.scn testsuites/mptests/mp07/node2/Makefile.am testsuites/mptests/mp07/node2/mp07.doc testsuites/mptests/mp07/node2/mp07.scn testsuites/mptests/mp07/system.h testsuites/mptests/mp07/task1.c testsuites/mptests/mp08/Makefile.am testsuites/mptests/mp08/init.c testsuites/mptests/mp08/node1/Makefile.am testsuites/mptests/mp08/node1/mp08.doc testsuites/mptests/mp08/node1/mp08.scn testsuites/mptests/mp08/node2/Makefile.am testsuites/mptests/mp08/node2/mp08.doc testsuites/mptests/mp08/node2/mp08.scn testsuites/mptests/mp08/system.h testsuites/mptests/mp08/task1.c testsuites/mptests/mp09/Makefile.am testsuites/mptests/mp09/init.c testsuites/mptests/mp09/node1/Makefile.am testsuites/mptests/mp09/node1/mp09.doc testsuites/mptests/mp09/node1/mp09.scn testsuites/mptests/mp09/node2/Makefile.am testsuites/mptests/mp09/node2/mp09.doc testsuites/mptests/mp09/node2/mp09.scn testsuites/mptests/mp09/recvmsg.c testsuites/mptests/mp09/sendmsg.c testsuites/mptests/mp09/system.h testsuites/mptests/mp09/task1.c testsuites/mptests/mp10/Makefile.am testsuites/mptests/mp10/init.c testsuites/mptests/mp10/node1/Makefile.am testsuites/mptests/mp10/node1/mp10.doc testsuites/mptests/mp10/node1/mp10.scn testsuites/mptests/mp10/node2/Makefile.am testsuites/mptests/mp10/node2/mp10.doc testsuites/mptests/mp10/node2/mp10.scn testsuites/mptests/mp10/system.h testsuites/mptests/mp10/task1.c testsuites/mptests/mp10/task2.c testsuites/mptests/mp10/task3.c testsuites/mptests/mp11/Makefile.am testsuites/mptests/mp11/init.c testsuites/mptests/mp11/node1/Makefile.am testsuites/mptests/mp11/node1/mp11.doc testsuites/mptests/mp11/node1/mp11.scn testsuites/mptests/mp11/node2/Makefile.am testsuites/mptests/mp11/node2/mp11.doc testsuites/mptests/mp11/node2/mp11.scn testsuites/mptests/mp11/system.h testsuites/mptests/mp12/Makefile.am testsuites/mptests/mp12/init.c testsuites/mptests/mp12/node1/Makefile.am testsuites/mptests/mp12/node1/mp12.doc testsuites/mptests/mp12/node1/mp12.scn testsuites/mptests/mp12/node2/Makefile.am testsuites/mptests/mp12/node2/mp12.doc testsuites/mptests/mp12/node2/mp12.scn testsuites/mptests/mp12/system.h testsuites/mptests/mp13/Makefile.am testsuites/mptests/mp13/init.c testsuites/mptests/mp13/node1/Makefile.am testsuites/mptests/mp13/node1/mp13.doc testsuites/mptests/mp13/node1/mp13.scn testsuites/mptests/mp13/node2/Makefile.am testsuites/mptests/mp13/node2/mp13.doc testsuites/mptests/mp13/node2/mp13.scn testsuites/mptests/mp13/system.h testsuites/mptests/mp13/task1.c testsuites/mptests/mp13/task2.c testsuites/mptests/mp14/Makefile.am testsuites/mptests/mp14/delay.c testsuites/mptests/mp14/evtask1.c testsuites/mptests/mp14/evtmtask.c testsuites/mptests/mp14/exit.c testsuites/mptests/mp14/init.c testsuites/mptests/mp14/msgtask1.c testsuites/mptests/mp14/node1/Makefile.am testsuites/mptests/mp14/node1/mp14.doc testsuites/mptests/mp14/node1/mp14.scn testsuites/mptests/mp14/node2/Makefile.am testsuites/mptests/mp14/node2/mp14.doc testsuites/mptests/mp14/node2/mp14.scn testsuites/mptests/mp14/pttask1.c testsuites/mptests/mp14/smtask1.c testsuites/mptests/mp14/system.h testsuites/mptests/mptests.am testsuites/psxtests/Makefile.am testsuites/psxtests/include/Makefile.am testsuites/psxtests/include/pmacros.h testsuites/psxtests/psx01/Makefile.am testsuites/psxtests/psx01/init.c testsuites/psxtests/psx01/psx01.scn testsuites/psxtests/psx01/system.h testsuites/psxtests/psx01/task.c testsuites/psxtests/psx02/Makefile.am testsuites/psxtests/psx02/init.c testsuites/psxtests/psx02/psx02.scn testsuites/psxtests/psx02/system.h testsuites/psxtests/psx02/task.c testsuites/psxtests/psx03/Makefile.am testsuites/psxtests/psx03/init.c testsuites/psxtests/psx03/psx03.scn testsuites/psxtests/psx03/system.h testsuites/psxtests/psx03/task.c testsuites/psxtests/psx04/Makefile.am testsuites/psxtests/psx04/init.c testsuites/psxtests/psx04/psx04.scn testsuites/psxtests/psx04/system.h testsuites/psxtests/psx04/task1.c testsuites/psxtests/psx04/task2.c testsuites/psxtests/psx04/task3.c testsuites/psxtests/psx05/Makefile.am testsuites/psxtests/psx05/init.c testsuites/psxtests/psx05/psx05.scn testsuites/psxtests/psx05/system.h testsuites/psxtests/psx05/task.c testsuites/psxtests/psx05/task2.c testsuites/psxtests/psx05/task3.c testsuites/psxtests/psx06/Makefile.am testsuites/psxtests/psx06/init.c testsuites/psxtests/psx06/psx06.scn testsuites/psxtests/psx06/system.h testsuites/psxtests/psx06/task.c testsuites/psxtests/psx06/task2.c testsuites/psxtests/psx07/Makefile.am testsuites/psxtests/psx07/init.c testsuites/psxtests/psx07/psx07.scn testsuites/psxtests/psx07/system.h testsuites/psxtests/psx07/task.c testsuites/psxtests/psx08/Makefile.am testsuites/psxtests/psx08/init.c testsuites/psxtests/psx08/psx08.scn testsuites/psxtests/psx08/system.h testsuites/psxtests/psx08/task1.c testsuites/psxtests/psx08/task2.c testsuites/psxtests/psx08/task3.c testsuites/psxtests/psx09/Makefile.am testsuites/psxtests/psx09/init.c testsuites/psxtests/psx09/psx09.scn testsuites/psxtests/psx09/system.h testsuites/psxtests/psx10/Makefile.am testsuites/psxtests/psx10/init.c testsuites/psxtests/psx10/psx10.scn testsuites/psxtests/psx10/system.h testsuites/psxtests/psx10/task.c testsuites/psxtests/psx10/task2.c testsuites/psxtests/psx10/task3.c testsuites/psxtests/psx11/Makefile.am testsuites/psxtests/psx11/init.c testsuites/psxtests/psx11/psx11.scn testsuites/psxtests/psx11/system.h testsuites/psxtests/psx11/task.c testsuites/psxtests/psx12/Makefile.am testsuites/psxtests/psx12/init.c testsuites/psxtests/psx12/psx12.scn testsuites/psxtests/psx12/system.h testsuites/psxtests/psx12/task.c testsuites/psxtests/psx13/Makefile.am testsuites/psxtests/psx13/main.c testsuites/psxtests/psx13/psx13.scn testsuites/psxtests/psx13/test.c testsuites/psxtests/psxcancel/Makefile.am testsuites/psxtests/psxcancel/init.c testsuites/psxtests/psxcancel/psxcancel.scn testsuites/psxtests/psxfile01/Makefile.am testsuites/psxtests/psxfile01/main.c testsuites/psxtests/psxfile01/psxfile01.scn testsuites/psxtests/psxfile01/test.c testsuites/psxtests/psxfile01/test_cat.c testsuites/psxtests/psxfile01/test_extend.c testsuites/psxtests/psxfile01/test_write.c testsuites/psxtests/psxhdrs/Makefile.am testsuites/psxtests/psxhdrs/clock01.c testsuites/psxtests/psxhdrs/clock02.c testsuites/psxtests/psxhdrs/clock03.c testsuites/psxtests/psxhdrs/clock04.c testsuites/psxtests/psxhdrs/clock05.c testsuites/psxtests/psxhdrs/clock06.c testsuites/psxtests/psxhdrs/cond01.c testsuites/psxtests/psxhdrs/cond02.c testsuites/psxtests/psxhdrs/cond03.c testsuites/psxtests/psxhdrs/cond04.c testsuites/psxtests/psxhdrs/cond05.c testsuites/psxtests/psxhdrs/cond06.c testsuites/psxtests/psxhdrs/cond07.c testsuites/psxtests/psxhdrs/cond08.c testsuites/psxtests/psxhdrs/cond09.c testsuites/psxtests/psxhdrs/cond10.c testsuites/psxtests/psxhdrs/key01.c testsuites/psxtests/psxhdrs/key02.c testsuites/psxtests/psxhdrs/key03.c testsuites/psxtests/psxhdrs/key04.c testsuites/psxtests/psxhdrs/mutex01.c testsuites/psxtests/psxhdrs/mutex02.c testsuites/psxtests/psxhdrs/mutex03.c testsuites/psxtests/psxhdrs/mutex04.c testsuites/psxtests/psxhdrs/mutex05.c testsuites/psxtests/psxhdrs/mutex06.c testsuites/psxtests/psxhdrs/mutex07.c testsuites/psxtests/psxhdrs/mutex08.c testsuites/psxtests/psxhdrs/mutex09.c testsuites/psxtests/psxhdrs/mutex10.c testsuites/psxtests/psxhdrs/mutex11.c testsuites/psxtests/psxhdrs/mutex12.c testsuites/psxtests/psxhdrs/mutex13.c testsuites/psxtests/psxhdrs/mutex14.c testsuites/psxtests/psxhdrs/mutex15.c testsuites/psxtests/psxhdrs/mutex16.c testsuites/psxtests/psxhdrs/proc01.c testsuites/psxtests/psxhdrs/proc02.c testsuites/psxtests/psxhdrs/proc03.c testsuites/psxtests/psxhdrs/proc04.c testsuites/psxtests/psxhdrs/proc05.c testsuites/psxtests/psxhdrs/proc06.c testsuites/psxtests/psxhdrs/proc07.c testsuites/psxtests/psxhdrs/proc08.c testsuites/psxtests/psxhdrs/proc09.c testsuites/psxtests/psxhdrs/proc10.c testsuites/psxtests/psxhdrs/proc11.c testsuites/psxtests/psxhdrs/proc12.c testsuites/psxtests/psxhdrs/proc13.c testsuites/psxtests/psxhdrs/proc14.c testsuites/psxtests/psxhdrs/pthread01.c testsuites/psxtests/psxhdrs/pthread02.c testsuites/psxtests/psxhdrs/pthread03.c testsuites/psxtests/psxhdrs/pthread04.c testsuites/psxtests/psxhdrs/pthread05.c testsuites/psxtests/psxhdrs/pthread06.c testsuites/psxtests/psxhdrs/pthread07.c testsuites/psxtests/psxhdrs/pthread08.c testsuites/psxtests/psxhdrs/pthread09.c testsuites/psxtests/psxhdrs/pthread10.c testsuites/psxtests/psxhdrs/pthread11.c testsuites/psxtests/psxhdrs/pthread12.c testsuites/psxtests/psxhdrs/pthread13.c testsuites/psxtests/psxhdrs/pthread14.c testsuites/psxtests/psxhdrs/pthread15.c testsuites/psxtests/psxhdrs/pthread16.c testsuites/psxtests/psxhdrs/pthread17.c testsuites/psxtests/psxhdrs/pthread18.c testsuites/psxtests/psxhdrs/pthread19.c testsuites/psxtests/psxhdrs/pthread20.c testsuites/psxtests/psxhdrs/pthread21.c testsuites/psxtests/psxhdrs/pthread22.c testsuites/psxtests/psxhdrs/pthread23.c testsuites/psxtests/psxhdrs/pthread24.c testsuites/psxtests/psxhdrs/pthread25.c testsuites/psxtests/psxhdrs/pthread26.c testsuites/psxtests/psxhdrs/pthread27.c testsuites/psxtests/psxhdrs/pthread28.c testsuites/psxtests/psxhdrs/pthread29.c testsuites/psxtests/psxhdrs/pthread30.c testsuites/psxtests/psxhdrs/pthread31.c testsuites/psxtests/psxhdrs/pthread32.c testsuites/psxtests/psxhdrs/pthread33.c testsuites/psxtests/psxhdrs/pthread34.c testsuites/psxtests/psxhdrs/pthread35.c testsuites/psxtests/psxhdrs/pthread36.c testsuites/psxtests/psxhdrs/sched01.c testsuites/psxtests/psxhdrs/sched02.c testsuites/psxtests/psxhdrs/sched03.c testsuites/psxtests/psxhdrs/sched04.c testsuites/psxtests/psxhdrs/sched05.c testsuites/psxtests/psxhdrs/sched06.c testsuites/psxtests/psxhdrs/sched07.c testsuites/psxtests/psxhdrs/sched08.c testsuites/psxtests/psxhdrs/signal01.c testsuites/psxtests/psxhdrs/signal02.c testsuites/psxtests/psxhdrs/signal03.c testsuites/psxtests/psxhdrs/signal04.c testsuites/psxtests/psxhdrs/signal05.c testsuites/psxtests/psxhdrs/signal06.c testsuites/psxtests/psxhdrs/signal07.c testsuites/psxtests/psxhdrs/signal08.c testsuites/psxtests/psxhdrs/signal09.c testsuites/psxtests/psxhdrs/signal10.c testsuites/psxtests/psxhdrs/signal11.c testsuites/psxtests/psxhdrs/signal12.c testsuites/psxtests/psxhdrs/signal13.c testsuites/psxtests/psxhdrs/signal14.c testsuites/psxtests/psxhdrs/signal15.c testsuites/psxtests/psxhdrs/signal16.c testsuites/psxtests/psxhdrs/signal17.c testsuites/psxtests/psxhdrs/signal18.c testsuites/psxtests/psxhdrs/signal19.c testsuites/psxtests/psxhdrs/signal20.c testsuites/psxtests/psxhdrs/signal21.c testsuites/psxtests/psxhdrs/signal22.c testsuites/psxtests/psxhdrs/time01.c testsuites/psxtests/psxhdrs/time02.c testsuites/psxtests/psxhdrs/time03.c testsuites/psxtests/psxhdrs/time04.c testsuites/psxtests/psxhdrs/time05.c testsuites/psxtests/psxhdrs/time06.c testsuites/psxtests/psxhdrs/time07.c testsuites/psxtests/psxhdrs/time08.c testsuites/psxtests/psxhdrs/time09.c testsuites/psxtests/psxhdrs/time10.c testsuites/psxtests/psxhdrs/time11.c testsuites/psxtests/psxhdrs/time12.c testsuites/psxtests/psxhdrs/time13.c testsuites/psxtests/psxhdrs/timer01.c testsuites/psxtests/psxhdrs/timer02.c testsuites/psxtests/psxhdrs/timer03.c testsuites/psxtests/psxhdrs/timer04.c testsuites/psxtests/psxhdrs/timer05.c testsuites/psxtests/psxhdrs/timer06.c testsuites/psxtests/psxmount/Makefile.am testsuites/psxtests/psxmount/main.c testsuites/psxtests/psxmount/psxmount.scn testsuites/psxtests/psxmount/test.c testsuites/psxtests/psxmsgq01/Makefile.am testsuites/psxtests/psxmsgq01/init.c testsuites/psxtests/psxmsgq01/psxmsgq01.scn testsuites/psxtests/psxmsgq01/system.h testsuites/psxtests/psxreaddir/Makefile.am testsuites/psxtests/psxreaddir/main.c testsuites/psxtests/psxreaddir/psxreaddir.scn testsuites/psxtests/psxreaddir/test.c testsuites/psxtests/psxsem01/Makefile.am testsuites/psxtests/psxsem01/init.c testsuites/psxtests/psxsem01/psxsem01.scn testsuites/psxtests/psxsem01/system.h testsuites/psxtests/psxstat/Makefile.am testsuites/psxtests/psxstat/main.c testsuites/psxtests/psxstat/psxstat.scn testsuites/psxtests/psxstat/test.c testsuites/psxtests/psxtests.am testsuites/psxtests/psxtime/Makefile.am testsuites/psxtests/psxtime/main.c testsuites/psxtests/psxtime/psxtime.scn testsuites/psxtests/psxtime/test.c testsuites/psxtests/psxtimer/Makefile.am testsuites/psxtests/psxtimer/psxtimer.c testsuites/psxtests/psxtimer/psxtimer.scn testsuites/psxtests/psxtimer/system.h testsuites/samples/Makefile.am testsuites/samples/README testsuites/samples/base_mp/Makefile.am testsuites/samples/base_mp/apptask.c testsuites/samples/base_mp/init.c testsuites/samples/base_mp/node1/Makefile.am testsuites/samples/base_mp/node1/base_mp.doc testsuites/samples/base_mp/node1/base_mp.scn testsuites/samples/base_mp/node2/Makefile.am testsuites/samples/base_mp/node2/base_mp.doc testsuites/samples/base_mp/node2/base_mp.scn testsuites/samples/base_mp/system.h testsuites/samples/base_sp/Makefile.am testsuites/samples/base_sp/apptask.c testsuites/samples/base_sp/base_sp.doc testsuites/samples/base_sp/base_sp.scn testsuites/samples/base_sp/init.c testsuites/samples/base_sp/system.h testsuites/samples/cdtest/Makefile.am testsuites/samples/cdtest/cdtest.scn testsuites/samples/cdtest/init.c testsuites/samples/cdtest/main.cc testsuites/samples/cdtest/system.h testsuites/samples/hello/Makefile.am testsuites/samples/hello/hello.doc testsuites/samples/hello/hello.scn testsuites/samples/hello/init.c testsuites/samples/hello/system.h testsuites/samples/minimum/Makefile.am testsuites/samples/minimum/init.c testsuites/samples/minimum/minimum.doc testsuites/samples/minimum/minimum.scn testsuites/samples/paranoia/Makefile.am testsuites/samples/paranoia/init.c testsuites/samples/paranoia/paranoia.c testsuites/samples/paranoia/paranoia.doc testsuites/samples/paranoia/system.h testsuites/samples/sample.am testsuites/samples/ticker/Makefile.am testsuites/samples/ticker/init.c testsuites/samples/ticker/system.h testsuites/samples/ticker/tasks.c testsuites/samples/ticker/ticker.doc testsuites/samples/ticker/ticker.scn testsuites/samples/unlimited/Makefile.am testsuites/samples/unlimited/init.c testsuites/samples/unlimited/system.h testsuites/samples/unlimited/test1.c testsuites/samples/unlimited/test2.c testsuites/samples/unlimited/test3.c testsuites/samples/unlimited/unlimited.doc testsuites/samples/unlimited/unlimited.scn testsuites/sptests/Makefile.am testsuites/sptests/README testsuites/sptests/sp01/Makefile.am testsuites/sptests/sp01/init.c testsuites/sptests/sp01/sp01.doc testsuites/sptests/sp01/sp01.scn testsuites/sptests/sp01/system.h testsuites/sptests/sp01/task1.c testsuites/sptests/sp02/Makefile.am testsuites/sptests/sp02/init.c testsuites/sptests/sp02/preempt.c testsuites/sptests/sp02/sp02.doc testsuites/sptests/sp02/sp02.scn testsuites/sptests/sp02/system.h testsuites/sptests/sp02/task1.c testsuites/sptests/sp02/task2.c testsuites/sptests/sp02/task3.c testsuites/sptests/sp03/Makefile.am testsuites/sptests/sp03/init.c testsuites/sptests/sp03/sp03.doc testsuites/sptests/sp03/sp03.scn testsuites/sptests/sp03/system.h testsuites/sptests/sp03/task1.c testsuites/sptests/sp03/task2.c testsuites/sptests/sp04/Makefile.am testsuites/sptests/sp04/init.c testsuites/sptests/sp04/sp04.doc testsuites/sptests/sp04/sp04.scn testsuites/sptests/sp04/system.h testsuites/sptests/sp04/task1.c testsuites/sptests/sp04/task2.c testsuites/sptests/sp04/task3.c testsuites/sptests/sp04/tswitch.c testsuites/sptests/sp05/Makefile.am testsuites/sptests/sp05/init.c testsuites/sptests/sp05/sp05.doc testsuites/sptests/sp05/sp05.scn testsuites/sptests/sp05/system.h testsuites/sptests/sp05/task1.c testsuites/sptests/sp05/task2.c testsuites/sptests/sp05/task3.c testsuites/sptests/sp06/Makefile.am testsuites/sptests/sp06/init.c testsuites/sptests/sp06/sp06.doc testsuites/sptests/sp06/sp06.scn testsuites/sptests/sp06/system.h testsuites/sptests/sp06/task1.c testsuites/sptests/sp06/task2.c testsuites/sptests/sp06/task3.c testsuites/sptests/sp07/Makefile.am testsuites/sptests/sp07/init.c testsuites/sptests/sp07/sp07.doc testsuites/sptests/sp07/sp07.scn testsuites/sptests/sp07/system.h testsuites/sptests/sp07/task1.c testsuites/sptests/sp07/task2.c testsuites/sptests/sp07/task3.c testsuites/sptests/sp07/task4.c testsuites/sptests/sp07/taskexit.c testsuites/sptests/sp07/tcreate.c testsuites/sptests/sp07/tdelete.c testsuites/sptests/sp07/trestart.c testsuites/sptests/sp07/tstart.c testsuites/sptests/sp08/Makefile.am testsuites/sptests/sp08/init.c testsuites/sptests/sp08/sp08.doc testsuites/sptests/sp08/sp08.scn testsuites/sptests/sp08/system.h testsuites/sptests/sp08/task1.c testsuites/sptests/sp09/Makefile.am testsuites/sptests/sp09/delay.c testsuites/sptests/sp09/init.c testsuites/sptests/sp09/isr.c testsuites/sptests/sp09/screen01.c testsuites/sptests/sp09/screen02.c testsuites/sptests/sp09/screen03.c testsuites/sptests/sp09/screen04.c testsuites/sptests/sp09/screen05.c testsuites/sptests/sp09/screen06.c testsuites/sptests/sp09/screen07.c testsuites/sptests/sp09/screen08.c testsuites/sptests/sp09/screen09.c testsuites/sptests/sp09/screen10.c testsuites/sptests/sp09/screen11.c testsuites/sptests/sp09/screen12.c testsuites/sptests/sp09/screen13.c testsuites/sptests/sp09/screen14.c testsuites/sptests/sp09/sp09.doc testsuites/sptests/sp09/sp09.scn testsuites/sptests/sp09/system.h testsuites/sptests/sp09/task1.c testsuites/sptests/sp09/task2.c testsuites/sptests/sp09/task3.c testsuites/sptests/sp09/task4.c testsuites/sptests/sp11/Makefile.am testsuites/sptests/sp11/init.c testsuites/sptests/sp11/sp11.doc testsuites/sptests/sp11/sp11.scn testsuites/sptests/sp11/system.h testsuites/sptests/sp11/task1.c testsuites/sptests/sp11/task2.c testsuites/sptests/sp11/timer.c testsuites/sptests/sp12/Makefile.am testsuites/sptests/sp12/init.c testsuites/sptests/sp12/pridrv.c testsuites/sptests/sp12/pritask.c testsuites/sptests/sp12/sp12.doc testsuites/sptests/sp12/sp12.scn testsuites/sptests/sp12/system.h testsuites/sptests/sp12/task1.c testsuites/sptests/sp12/task2.c testsuites/sptests/sp12/task3.c testsuites/sptests/sp12/task4.c testsuites/sptests/sp12/task5.c testsuites/sptests/sp13/Makefile.am testsuites/sptests/sp13/fillbuff.c testsuites/sptests/sp13/init.c testsuites/sptests/sp13/putbuff.c testsuites/sptests/sp13/sp13.doc testsuites/sptests/sp13/sp13.scn testsuites/sptests/sp13/system.h testsuites/sptests/sp13/task1.c testsuites/sptests/sp13/task2.c testsuites/sptests/sp13/task3.c testsuites/sptests/sp14/Makefile.am testsuites/sptests/sp14/asr.c testsuites/sptests/sp14/init.c testsuites/sptests/sp14/sp14.doc testsuites/sptests/sp14/sp14.scn testsuites/sptests/sp14/system.h testsuites/sptests/sp14/task1.c testsuites/sptests/sp14/task2.c testsuites/sptests/sp15/Makefile.am testsuites/sptests/sp15/init.c testsuites/sptests/sp15/sp15.doc testsuites/sptests/sp15/sp15.scn testsuites/sptests/sp15/system.h testsuites/sptests/sp15/task1.c testsuites/sptests/sp16/Makefile.am testsuites/sptests/sp16/init.c testsuites/sptests/sp16/sp16.doc testsuites/sptests/sp16/sp16.scn testsuites/sptests/sp16/system.h testsuites/sptests/sp16/task1.c testsuites/sptests/sp16/task2.c testsuites/sptests/sp16/task3.c testsuites/sptests/sp16/task4.c testsuites/sptests/sp16/task5.c testsuites/sptests/sp17/Makefile.am testsuites/sptests/sp17/asr.c testsuites/sptests/sp17/init.c testsuites/sptests/sp17/sp17.doc testsuites/sptests/sp17/sp17.scn testsuites/sptests/sp17/system.h testsuites/sptests/sp17/task1.c testsuites/sptests/sp17/task2.c testsuites/sptests/sp19/Makefile.am testsuites/sptests/sp19/first.c testsuites/sptests/sp19/fptask.c testsuites/sptests/sp19/fptest.h testsuites/sptests/sp19/init.c testsuites/sptests/sp19/inttest.h testsuites/sptests/sp19/sp19.doc testsuites/sptests/sp19/sp19.scn testsuites/sptests/sp19/system.h testsuites/sptests/sp19/task1.c testsuites/sptests/sp20/Makefile.am testsuites/sptests/sp20/getall.c testsuites/sptests/sp20/init.c testsuites/sptests/sp20/sp20.doc testsuites/sptests/sp20/sp20.scn testsuites/sptests/sp20/system.h testsuites/sptests/sp20/task1.c testsuites/sptests/sp21/Makefile.am testsuites/sptests/sp21/init.c testsuites/sptests/sp21/sp21.doc testsuites/sptests/sp21/sp21.scn testsuites/sptests/sp21/system.h testsuites/sptests/sp21/task1.c testsuites/sptests/sp22/Makefile.am testsuites/sptests/sp22/delay.c testsuites/sptests/sp22/init.c testsuites/sptests/sp22/prtime.c testsuites/sptests/sp22/sp22.doc testsuites/sptests/sp22/sp22.scn testsuites/sptests/sp22/system.h testsuites/sptests/sp22/task1.c testsuites/sptests/sp23/Makefile.am testsuites/sptests/sp23/init.c testsuites/sptests/sp23/sp23.doc testsuites/sptests/sp23/sp23.scn testsuites/sptests/sp23/system.h testsuites/sptests/sp23/task1.c testsuites/sptests/sp24/Makefile.am testsuites/sptests/sp24/init.c testsuites/sptests/sp24/resume.c testsuites/sptests/sp24/sp24.doc testsuites/sptests/sp24/sp24.scn testsuites/sptests/sp24/system.h testsuites/sptests/sp24/task1.c testsuites/sptests/sp25/Makefile.am testsuites/sptests/sp25/init.c testsuites/sptests/sp25/sp25.doc testsuites/sptests/sp25/sp25.scn testsuites/sptests/sp25/system.h testsuites/sptests/sp25/task1.c testsuites/sptests/sp26/Makefile.am testsuites/sptests/sp26/init.c testsuites/sptests/sp26/sp26.doc testsuites/sptests/sp26/sp26.scn testsuites/sptests/sp26/system.h testsuites/sptests/sp26/task1.c testsuites/sptests/sp27/Makefile.am testsuites/sptests/sp27/init.c testsuites/sptests/sp27/sp27.doc testsuites/sptests/sp27/sp27.scn testsuites/sptests/sp28/Makefile.am testsuites/sptests/sp28/init.c testsuites/sptests/sp28/sp28.doc testsuites/sptests/sp28/sp28.scn testsuites/sptests/sp29/Makefile.am testsuites/sptests/sp29/init.c testsuites/sptests/sp29/sp29.doc testsuites/sptests/sp29/sp29.scn testsuites/sptests/spfatal/Makefile.am testsuites/sptests/spfatal/README testsuites/sptests/spfatal/fatal.c testsuites/sptests/spfatal/init.c testsuites/sptests/spfatal/puterr.c testsuites/sptests/spfatal/spfatal.doc testsuites/sptests/spfatal/spfatal.scn testsuites/sptests/spfatal/system.h testsuites/sptests/spfatal/task1.c testsuites/sptests/spsize/Makefile.am testsuites/sptests/spsize/getint.c testsuites/sptests/spsize/init.c testsuites/sptests/spsize/size.c testsuites/sptests/spsize/size.scn testsuites/sptests/spsize/system.h testsuites/sptests/sptests.am testsuites/support/Makefile.am testsuites/support/include/tmacros.h testsuites/tmitrontests/Makefile.am testsuites/tmitrontests/README testsuites/tmitrontests/include/Makefile.am testsuites/tmitrontests/include/timesys.h testsuites/tmitrontests/tmitronsem01/Makefile.am testsuites/tmitrontests/tmitronsem01/init.c testsuites/tmitrontests/tmitronsem01/system.h testsuites/tmitrontests/tmitronsem01/tmitronsem01.doc testsuites/tmitrontests/tmitrontests.am testsuites/tmtests/Makefile.am testsuites/tmtests/README testsuites/tmtests/include/Makefile.am testsuites/tmtests/include/timesys.h testsuites/tmtests/tm01/Makefile.am testsuites/tmtests/tm01/system.h testsuites/tmtests/tm01/task1.c testsuites/tmtests/tm01/tm01.doc testsuites/tmtests/tm02/Makefile.am testsuites/tmtests/tm02/system.h testsuites/tmtests/tm02/task1.c testsuites/tmtests/tm02/tm02.doc testsuites/tmtests/tm03/Makefile.am testsuites/tmtests/tm03/system.h testsuites/tmtests/tm03/task1.c testsuites/tmtests/tm03/tm03.doc testsuites/tmtests/tm04/Makefile.am testsuites/tmtests/tm04/system.h testsuites/tmtests/tm04/task1.c testsuites/tmtests/tm04/tm04.doc testsuites/tmtests/tm05/Makefile.am testsuites/tmtests/tm05/system.h testsuites/tmtests/tm05/task1.c testsuites/tmtests/tm05/tm05.doc testsuites/tmtests/tm06/Makefile.am testsuites/tmtests/tm06/system.h testsuites/tmtests/tm06/task1.c testsuites/tmtests/tm06/tm06.doc testsuites/tmtests/tm07/Makefile.am testsuites/tmtests/tm07/system.h testsuites/tmtests/tm07/task1.c testsuites/tmtests/tm07/tm07.doc testsuites/tmtests/tm08/Makefile.am testsuites/tmtests/tm08/system.h testsuites/tmtests/tm08/task1.c testsuites/tmtests/tm08/tm08.doc testsuites/tmtests/tm09/Makefile.am testsuites/tmtests/tm09/system.h testsuites/tmtests/tm09/task1.c testsuites/tmtests/tm09/tm09.doc testsuites/tmtests/tm10/Makefile.am testsuites/tmtests/tm10/system.h testsuites/tmtests/tm10/task1.c testsuites/tmtests/tm10/tm10.doc testsuites/tmtests/tm11/Makefile.am testsuites/tmtests/tm11/system.h testsuites/tmtests/tm11/task1.c testsuites/tmtests/tm11/tm11.doc testsuites/tmtests/tm12/Makefile.am testsuites/tmtests/tm12/system.h testsuites/tmtests/tm12/task1.c testsuites/tmtests/tm12/tm12.doc testsuites/tmtests/tm13/Makefile.am testsuites/tmtests/tm13/system.h testsuites/tmtests/tm13/task1.c testsuites/tmtests/tm13/tm13.doc testsuites/tmtests/tm14/Makefile.am testsuites/tmtests/tm14/system.h testsuites/tmtests/tm14/task1.c testsuites/tmtests/tm14/tm14.doc testsuites/tmtests/tm15/Makefile.am testsuites/tmtests/tm15/system.h testsuites/tmtests/tm15/task1.c testsuites/tmtests/tm15/tm15.doc testsuites/tmtests/tm16/Makefile.am testsuites/tmtests/tm16/system.h testsuites/tmtests/tm16/task1.c testsuites/tmtests/tm16/tm16.doc testsuites/tmtests/tm17/Makefile.am testsuites/tmtests/tm17/system.h testsuites/tmtests/tm17/task1.c testsuites/tmtests/tm17/tm17.doc testsuites/tmtests/tm18/Makefile.am testsuites/tmtests/tm18/system.h testsuites/tmtests/tm18/task1.c testsuites/tmtests/tm18/tm18.doc testsuites/tmtests/tm19/Makefile.am testsuites/tmtests/tm19/system.h testsuites/tmtests/tm19/task1.c testsuites/tmtests/tm19/tm19.doc testsuites/tmtests/tm20/Makefile.am testsuites/tmtests/tm20/system.h testsuites/tmtests/tm20/task1.c testsuites/tmtests/tm20/tm20.doc testsuites/tmtests/tm21/Makefile.am testsuites/tmtests/tm21/system.h testsuites/tmtests/tm21/task1.c testsuites/tmtests/tm21/tm21.doc testsuites/tmtests/tm22/Makefile.am testsuites/tmtests/tm22/system.h testsuites/tmtests/tm22/task1.c testsuites/tmtests/tm22/tm22.doc testsuites/tmtests/tm23/Makefile.am testsuites/tmtests/tm23/system.h testsuites/tmtests/tm23/task1.c testsuites/tmtests/tm23/tm23.doc testsuites/tmtests/tm24/Makefile.am testsuites/tmtests/tm24/system.h testsuites/tmtests/tm24/task1.c testsuites/tmtests/tm24/tm24.doc testsuites/tmtests/tm25/Makefile.am testsuites/tmtests/tm25/system.h testsuites/tmtests/tm25/task1.c testsuites/tmtests/tm25/tm25.doc testsuites/tmtests/tm26/Makefile.am testsuites/tmtests/tm26/fptest.h testsuites/tmtests/tm26/system.h testsuites/tmtests/tm26/task1.c testsuites/tmtests/tm26/tm26.doc testsuites/tmtests/tm27/Makefile.am testsuites/tmtests/tm27/system.h testsuites/tmtests/tm27/task1.c testsuites/tmtests/tm27/tm27.doc testsuites/tmtests/tm28/Makefile.am testsuites/tmtests/tm28/system.h testsuites/tmtests/tm28/task1.c testsuites/tmtests/tm28/tm28.doc testsuites/tmtests/tm29/Makefile.am testsuites/tmtests/tm29/system.h testsuites/tmtests/tm29/task1.c testsuites/tmtests/tm29/tm29.doc testsuites/tmtests/tmck/Makefile.am testsuites/tmtests/tmck/system.h testsuites/tmtests/tmck/task1.c testsuites/tmtests/tmck/tmck.doc testsuites/tmtests/tmoverhd/Makefile.am testsuites/tmtests/tmoverhd/dumrtems.h testsuites/tmtests/tmoverhd/empty.c testsuites/tmtests/tmoverhd/system.h testsuites/tmtests/tmoverhd/testtask.c testsuites/tmtests/tmoverhd/tmoverhd.doc testsuites/tmtests/tmtests.am testsuites/tools/Makefile.am testsuites/tools/generic/Makefile.am testsuites/tools/generic/difftest.in testsuites/tools/generic/sorttimes.in --- doc/BAD.html | 22 - doc/FAQ/FAQ.texi | 123 - doc/FAQ/Makefile | 117 - doc/FAQ/basic.t | 177 - doc/FAQ/bsp.t | 35 - doc/FAQ/concepts.t | 19 - doc/FAQ/debug.t | 100 - doc/FAQ/embeddedinfo.t | 38 - doc/FAQ/endoftime.t | 111 - doc/FAQ/entry | 57 - doc/FAQ/freesw.t | 162 - doc/FAQ/hwdebugaids.t | 110 - doc/FAQ/projects.t | 113 - doc/FAQ/tools.t | 51 - doc/HELP.html | 22 - doc/Make.config | 64 - doc/Makefile | 57 - doc/README | 36 - doc/TODO | 77 - doc/VERSION | 5 - doc/ada_user/Makefile | 73 - doc/ada_user/ada_user.texi | 169 - doc/ada_user/example.texi | 21 - doc/archgrey.gif | Bin 12160 -> 0 bytes doc/bsp_howto/Makefile | 152 - doc/bsp_howto/adaintr.t | 81 - doc/bsp_howto/analog.t | 167 - doc/bsp_howto/bsp_howto.texi | 130 - doc/bsp_howto/clock.t | 132 - doc/bsp_howto/console.t | 377 - doc/bsp_howto/discrete.t | 187 - doc/bsp_howto/init.t | 430 - doc/bsp_howto/intro.t | 57 - doc/bsp_howto/linkcmds.t | 425 - doc/bsp_howto/makefiles.t | 235 - doc/bsp_howto/nvmem.t | 235 - doc/bsp_howto/rtc.t | 188 - doc/bsp_howto/shmsupp.t | 269 - doc/bsp_howto/support.t | 257 - doc/bsp_howto/target.t | 214 - doc/bsp_howto/timer.t | 121 - doc/common/cpright.texi | 45 - doc/common/dvi.gif | Bin 156 -> 0 bytes doc/common/oaronly.jpg | Bin 1584 -> 0 bytes doc/common/pdf.gif | Bin 249 -> 0 bytes doc/common/pdf1.gif | Bin 173 -> 0 bytes doc/common/ps.gif | Bin 244 -> 0 bytes doc/common/setup.texi | 75 - doc/common/timemac.texi | 36 - doc/common/timetbl.t | 1330 -- doc/common/timing.t | 396 - doc/common/treedef.tex | 317 - doc/common/up-arrow.gif | Bin 264 -> 0 bytes doc/common/wksheets.t | 409 - doc/develenv/Makefile | 54 - doc/develenv/compile.texi | 159 - doc/develenv/develenv.texi | 122 - doc/develenv/direct.texi | 730 - doc/develenv/intro.texi | 58 - doc/develenv/sample.texi | 287 - doc/develenv/utils.texi | 312 - doc/do_docs | 53 - doc/filesystem/Makefile | 120 - doc/filesystem/filesystem.texi | 115 - doc/filesystem/fsrequirements.t | 1183 -- doc/filesystem/imfs.t | 2038 --- doc/filesystem/init.t | 113 - doc/filesystem/miniimfs.t | 16 - doc/filesystem/mounting.t | 171 - doc/filesystem/patheval.t | 109 - doc/filesystem/preface.texi | 83 - doc/filesystem/syscalls.t | 1130 -- doc/filesystem/tftp.t | 14 - doc/gnu_docs/Tool_Doc_Instructions | 32 - doc/gnu_docs/gen_docs | 125 - doc/gnu_docs/gnu_footer.html | 2 - doc/gnu_docs/gnu_header.html | 5 - doc/gnu_docs/index.html | 143 - doc/gnu_docs/mk_install_dir | 29 - doc/gnu_docs/refcard.html | 13 - doc/gnu_docs/rtems_tools_index.html | 15 - doc/index.html | 275 - doc/itron3.0/Makefile | 133 - doc/itron3.0/config.t | 187 - doc/itron3.0/eventflags.t | 860 -- doc/itron3.0/fixedblock.t | 389 - doc/itron3.0/gen_all | 4 - doc/itron3.0/gen_section | 191 - doc/itron3.0/gen_status_shell | 230 - doc/itron3.0/interrupt.t | 306 - doc/itron3.0/itron.texi | 149 - doc/itron3.0/mailbox.t | 338 - doc/itron3.0/memorypool.t | 401 - doc/itron3.0/msgbuffer.t | 826 -- doc/itron3.0/network.t | 162 - doc/itron3.0/preface.texi | 14 - doc/itron3.0/rendezvous.t | 395 - doc/itron3.0/semaphore.t | 642 - doc/itron3.0/status.t | 943 -- doc/itron3.0/task.t | 767 - doc/itron3.0/tasksync.t | 388 - doc/itron3.0/time.t | 310 - doc/networking/Makefile | 109 - doc/networking/PCIreg.eps | 319 - doc/networking/PCIreg.jpg | Bin 48116 -> 0 bytes doc/networking/PCIreg.pdf | Bin 1906 -> 0 bytes doc/networking/decdriver.t | 291 - doc/networking/driver.t | 342 - doc/networking/networkapp.t | 447 - doc/networking/networkflow.eps | 1343 -- doc/networking/networkflow.jpg | Bin 36969 -> 0 bytes doc/networking/networkflow.pdf | Bin 19170 -> 0 bytes doc/networking/networkflow.png | Bin 12933 -> 0 bytes doc/networking/networking.texi | 111 - doc/networking/networktasks.t | 62 - doc/networking/preface.texi | 52 - doc/networking/recvbd.eps | 181 - doc/networking/recvbd.jpg | Bin 11100 -> 0 bytes doc/networking/recvbd.pdf | Bin 1101 -> 0 bytes doc/networking/servers.t | 118 - doc/networking/testing.t | 220 - doc/new_chapters/Makefile | 107 - doc/new_chapters/STATUS | 9 - doc/new_chapters/TODO | 4 - doc/new_chapters/adminiface.t | 129 - doc/new_chapters/base.t | 62 - doc/new_chapters/confspace.t | 1351 -- doc/new_chapters/cpuuse.t | 142 - doc/new_chapters/dumpcontrol.t | 98 - doc/new_chapters/error.t | 164 - doc/new_chapters/eventlog.t | 1265 -- doc/new_chapters/gen_section | 238 - doc/new_chapters/monitor.t | 224 - doc/new_chapters/new_chapters.texi | 137 - doc/new_chapters/rtmonuse.t | 294 - doc/new_chapters/stackchk.t | 192 - doc/oaronly.jpg | Bin 1584 -> 0 bytes doc/porting/Makefile | 111 - doc/porting/codetuning.t | 155 - doc/porting/cpuinit.t | 150 - doc/porting/cpumodels.t | 144 - doc/porting/developtools.t | 26 - doc/porting/idlethread.t | 116 - doc/porting/interrupts.t | 402 - doc/porting/miscellaneous.t | 170 - doc/porting/porting.texi | 139 - doc/porting/preface.texi | 42 - doc/porting/prioritybitmap.t | 166 - doc/porting/sourcecode.t | 23 - doc/porting/taskcontext.t | 476 - doc/posix1003.1/Makefile | 163 - doc/posix1003.1/ch01.t | 40 - doc/posix1003.1/ch02.t | 279 - doc/posix1003.1/ch03.t | 203 - doc/posix1003.1/ch04.t | 181 - doc/posix1003.1/ch05.t | 222 - doc/posix1003.1/ch06.t | 175 - doc/posix1003.1/ch07.t | 207 - doc/posix1003.1/ch08.t | 288 - doc/posix1003.1/ch09.t | 38 - doc/posix1003.1/ch10.t | 68 - doc/posix1003.1/ch11.t | 133 - doc/posix1003.1/ch12.t | 77 - doc/posix1003.1/ch13.t | 132 - doc/posix1003.1/ch14.t | 71 - doc/posix1003.1/ch15.t | 72 - doc/posix1003.1/ch16.t | 72 - doc/posix1003.1/ch17.t | 31 - doc/posix1003.1/ch18.t | 66 - doc/posix1003.1/posix1003_1.texi | 138 - doc/posix1003.1/preface.texi | 29 - doc/posix1003.1/summarize | 199 - doc/posix_users/Makefile | 177 - doc/posix_users/cancel.t | 239 - doc/posix_users/clock.t | 313 - doc/posix_users/cond.t | 383 - doc/posix_users/cspecific.t | 749 - doc/posix_users/device.t | 540 - doc/posix_users/files.t | 2347 ---- doc/posix_users/gen_size_report | 209 - doc/posix_users/io.t | 1107 -- doc/posix_users/key.t | 152 - doc/posix_users/libc.t | 348 - doc/posix_users/libm.t | 58 - doc/posix_users/memorymgmt.t | 375 - doc/posix_users/message.t | 693 - doc/posix_users/mutex.t | 744 - doc/posix_users/posix_users.texi | 165 - doc/posix_users/preface.texi | 34 - doc/posix_users/procenv.t | 819 -- doc/posix_users/process.t | 480 - doc/posix_users/sched.t | 219 - doc/posix_users/semaphores.t | 593 - doc/posix_users/signal.t | 836 -- doc/posix_users/status.t | 61 - doc/posix_users/systemdb.t | 307 - doc/posix_users/thread.t | 1332 -- doc/posix_users/timer.t | 196 - doc/relnotes/Makefile | 53 - doc/relnotes/install.texi | 176 - doc/relnotes/intro.texi | 217 - doc/relnotes/probrep.texi | 62 - doc/relnotes/relnotes.texi | 119 - doc/relnotes/status.texi | 260 - doc/rgdb_specs/Makefile | 114 - doc/rgdb_specs/comm.t | 115 - doc/rgdb_specs/conclusion.t | 51 - doc/rgdb_specs/daemon.t | 437 - doc/rgdb_specs/garde.eps | 8168 ----------- doc/rgdb_specs/garde.pdf | Bin 272042 -> 0 bytes doc/rgdb_specs/gdbinternals.t | 309 - doc/rgdb_specs/interfacing.t | 79 - doc/rgdb_specs/intro.t | 39 - doc/rgdb_specs/layers.eps | 359 - doc/rgdb_specs/layers.jpg | Bin 31318 -> 0 bytes doc/rgdb_specs/layers.pdf | Bin 4594 -> 0 bytes doc/rgdb_specs/objectives.t | 307 - doc/rgdb_specs/process.eps | 672 - doc/rgdb_specs/process.jpg | Bin 136532 -> 0 bytes doc/rgdb_specs/process.pdf | Bin 7144 -> 0 bytes doc/rgdb_specs/revision.t | 42 - doc/rgdb_specs/rgdb_specs.texi | 115 - doc/rgdb_specs/seqbreak.eps | 311 - doc/rgdb_specs/seqbreak.jpg | Bin 79883 -> 0 bytes doc/rgdb_specs/seqbreak.pdf | Bin 2033 -> 0 bytes doc/rgdb_specs/seqdetach.eps | 167 - doc/rgdb_specs/seqdetach.jpg | Bin 24799 -> 0 bytes doc/rgdb_specs/seqdetach.pdf | Bin 1293 -> 0 bytes doc/rgdb_specs/seqinit.eps | 204 - doc/rgdb_specs/seqinit.jpg | Bin 34525 -> 0 bytes doc/rgdb_specs/seqinit.pdf | Bin 1511 -> 0 bytes doc/rtems_footer.html | 1 - doc/rtems_gdb/Makefile | 94 - doc/rtems_gdb/commands.t | 51 - doc/rtems_gdb/example.t | 88 - doc/rtems_gdb/intro.t | 22 - doc/rtems_gdb/rtems_gdb.texi | 111 - doc/rtems_gdb/started.t | 53 - doc/rtems_gdb/swarch.t | 32 - doc/rtems_gdb/trouble.t | 46 - doc/rtems_header.html | 5 - doc/rtems_support.html | 59 - doc/src2html/Makefile | 40 - doc/src2html/RTEMS.test | 62 - doc/started/Makefile | 97 - doc/started/buildc.t | 566 - doc/started/buildrt.t | 137 - doc/started/gdb.t | 222 - doc/started/intro.t | 162 - doc/started/nt.t | 345 - doc/started/pictures/bit_ada.jpg | Bin 30320 -> 0 bytes doc/started/pictures/bit_ada.vsd | Bin 15360 -> 0 bytes doc/started/pictures/bit_c.jpg | Bin 29778 -> 0 bytes doc/started/pictures/bit_c.vsd | Bin 14336 -> 0 bytes doc/started/pictures/scfile10.jpg | Bin 12972 -> 0 bytes doc/started/pictures/scfile10.vsd | Bin 26112 -> 0 bytes doc/started/pictures/scfile11.jpg | Bin 45560 -> 0 bytes doc/started/pictures/scfile11.vsd | Bin 24576 -> 0 bytes doc/started/pictures/scfile12.jpg | Bin 12972 -> 0 bytes doc/started/pictures/scfile12.vsd | Bin 11776 -> 0 bytes doc/started/pictures/scfile13.jpg | Bin 33103 -> 0 bytes doc/started/pictures/scfile13.vsd | Bin 15360 -> 0 bytes doc/started/pictures/scsfile1.jpg | Bin 88599 -> 0 bytes doc/started/pictures/scsfile1.vsd | Bin 25088 -> 0 bytes doc/started/pictures/scsfile2.jpg | Bin 175286 -> 0 bytes doc/started/pictures/scsfile2.vsd | Bin 26624 -> 0 bytes doc/started/pictures/scsfile3.jpg | Bin 87075 -> 0 bytes doc/started/pictures/scsfile3.vsd | Bin 19456 -> 0 bytes doc/started/pictures/scsfile4.jpg | Bin 97380 -> 0 bytes doc/started/pictures/scsfile4.vsd | Bin 16896 -> 0 bytes doc/started/pictures/scsfile5.jpg | Bin 22942 -> 0 bytes doc/started/pictures/scsfile5.vsd | Bin 13824 -> 0 bytes doc/started/pictures/scsfile6.jpg | Bin 34989 -> 0 bytes doc/started/pictures/scsfile6.vsd | Bin 13824 -> 0 bytes doc/started/pictures/scsfile7.jpg | Bin 99516 -> 0 bytes doc/started/pictures/scsfile7.vsd | Bin 19456 -> 0 bytes doc/started/pictures/scsfile8.jpg | Bin 52638 -> 0 bytes doc/started/pictures/scsfile8.vsd | Bin 16896 -> 0 bytes doc/started/pictures/scsfile9.jpg | Bin 62821 -> 0 bytes doc/started/pictures/scsfile9.vsd | Bin 13824 -> 0 bytes doc/started/pictures/sfile12c.jpg | Bin 11663 -> 0 bytes doc/started/pictures/sfile12c.vsd | Bin 11264 -> 0 bytes doc/started/require.t | 56 - doc/started/sample.t | 57 - doc/started/started.texi | 117 - doc/started/versions.texi | 86 - doc/started_ada/Makefile | 92 - doc/started_ada/buildada.t | 541 - doc/started_ada/buildrt.t | 141 - doc/started_ada/gdb.t | 232 - doc/started_ada/intro.t | 161 - doc/started_ada/require.t | 102 - doc/started_ada/sample.t | 54 - doc/started_ada/started_ada.texi | 115 - doc/started_ada/versions.texi | 96 - doc/supplements/hppa1_1/Makefile | 152 - doc/supplements/hppa1_1/SIMHPPA_TIMES | 247 - doc/supplements/hppa1_1/bsp.t | 53 - doc/supplements/hppa1_1/callconv.t | 143 - doc/supplements/hppa1_1/cpumodel.t | 56 - doc/supplements/hppa1_1/cputable.t | 116 - doc/supplements/hppa1_1/fatalerr.t | 32 - doc/supplements/hppa1_1/hppa1_1.texi | 121 - doc/supplements/hppa1_1/intr_NOTIMES.t | 191 - doc/supplements/hppa1_1/memmodel.t | 67 - doc/supplements/hppa1_1/preface.texi | 36 - doc/supplements/hppa1_1/timeSIMHPPA.t | 86 - doc/supplements/i386/FORCE386_TIMES | 247 - doc/supplements/i386/Makefile | 170 - doc/supplements/i386/bsp.t | 109 - doc/supplements/i386/callconv.t | 90 - doc/supplements/i386/cpumodel.t | 72 - doc/supplements/i386/cputable.t | 119 - doc/supplements/i386/fatalerr.t | 31 - doc/supplements/i386/i386.texi | 120 - doc/supplements/i386/intr_NOTIMES.t | 168 - doc/supplements/i386/memmodel.t | 72 - doc/supplements/i386/preface.texi | 41 - doc/supplements/i386/timeFORCE386.t | 101 - doc/supplements/i960/CVME961_TIMES | 247 - doc/supplements/i960/Makefile | 161 - doc/supplements/i960/bsp.t | 54 - doc/supplements/i960/callconv.t | 97 - doc/supplements/i960/cpumodel.t | 62 - doc/supplements/i960/cputable.t | 121 - doc/supplements/i960/fatalerr.t | 30 - doc/supplements/i960/i960.texi | 120 - doc/supplements/i960/intr_NOTIMES.t | 193 - doc/supplements/i960/memmodel.t | 40 - doc/supplements/i960/preface.texi | 40 - doc/supplements/i960/timeCVME961.t | 88 - doc/supplements/m68k/MVME136_TIMES | 247 - doc/supplements/m68k/Makefile | 170 - doc/supplements/m68k/bsp.t | 93 - doc/supplements/m68k/callconv.t | 92 - doc/supplements/m68k/cpumodel.t | 91 - doc/supplements/m68k/cputable.t | 109 - doc/supplements/m68k/fatalerr.t | 31 - doc/supplements/m68k/intr_NOTIMES.t | 196 - doc/supplements/m68k/m68k.texi | 121 - doc/supplements/m68k/memmodel.t | 39 - doc/supplements/m68k/preface.texi | 60 - doc/supplements/m68k/timeMVME136.t | 108 - doc/supplements/m68k/timedata.t | 150 - doc/supplements/mips64orion/BSP_TIMES | 247 - doc/supplements/mips64orion/Makefile | 161 - doc/supplements/mips64orion/bsp.t | 93 - doc/supplements/mips64orion/callconv.t | 92 - doc/supplements/mips64orion/cpumodel.t | 68 - doc/supplements/mips64orion/cputable.t | 109 - doc/supplements/mips64orion/fatalerr.t | 31 - doc/supplements/mips64orion/intr_NOTIMES.t | 196 - doc/supplements/mips64orion/memmodel.t | 39 - doc/supplements/mips64orion/mips64orion.texi | 120 - doc/supplements/mips64orion/preface.texi | 57 - doc/supplements/mips64orion/timeBSP.t | 108 - doc/supplements/powerpc/DMV177_TIMES | 248 - doc/supplements/powerpc/Makefile | 183 - doc/supplements/powerpc/PSIM_TIMES | 248 - doc/supplements/powerpc/bsp.t | 76 - doc/supplements/powerpc/callconv.t | 229 - doc/supplements/powerpc/cpumodel.t | 156 - doc/supplements/powerpc/cputable.t | 155 - doc/supplements/powerpc/fatalerr.t | 47 - doc/supplements/powerpc/intr_NOTIMES.t | 184 - doc/supplements/powerpc/memmodel.t | 110 - doc/supplements/powerpc/powerpc.texi | 121 - doc/supplements/powerpc/preface.texi | 94 - doc/supplements/powerpc/timeDMV177.t | 113 - doc/supplements/powerpc/timePSIM.t | 97 - doc/supplements/sh/BSP_TIMES | 247 - doc/supplements/sh/Makefile | 161 - doc/supplements/sh/bsp.t | 93 - doc/supplements/sh/callconv.t | 102 - doc/supplements/sh/cpumodel.t | 68 - doc/supplements/sh/cputable.t | 109 - doc/supplements/sh/fatalerr.t | 31 - doc/supplements/sh/intr_NOTIMES.t | 196 - doc/supplements/sh/memmodel.t | 39 - doc/supplements/sh/preface.texi | 55 - doc/supplements/sh/sh.texi | 120 - doc/supplements/sh/timeBSP.t | 108 - doc/supplements/sparc/ERC32_TIMES | 247 - doc/supplements/sparc/Makefile | 163 - doc/supplements/sparc/bsp.t | 87 - doc/supplements/sparc/callconv.t | 392 - doc/supplements/sparc/cpumodel.t | 128 - doc/supplements/sparc/cputable.t | 102 - doc/supplements/sparc/fatalerr.t | 32 - doc/supplements/sparc/intr_NOTIMES.t | 199 - doc/supplements/sparc/memmodel.t | 104 - doc/supplements/sparc/preface.texi | 91 - doc/supplements/sparc/sparc.texi | 119 - doc/supplements/sparc/timeERC32.t | 120 - doc/supplements/template/BSP_TIMES | 247 - doc/supplements/template/Makefile | 159 - doc/supplements/template/bsp.t | 93 - doc/supplements/template/callconv.t | 92 - doc/supplements/template/cpumodel.t | 68 - doc/supplements/template/cputable.t | 109 - doc/supplements/template/fatalerr.t | 31 - doc/supplements/template/intr_NOTIMES.t | 196 - doc/supplements/template/memmodel.t | 39 - doc/supplements/template/preface.texi | 55 - doc/supplements/template/template.texi | 121 - doc/supplements/template/timeBSP.t | 108 - doc/texinfo/texinfo.tex | 4426 ------ doc/tools/bmenu/Makefile | 45 - doc/tools/bmenu/address.h | 110 - doc/tools/bmenu/address.inl | 105 - doc/tools/bmenu/base.h | 113 - doc/tools/bmenu/chain.c | 229 - doc/tools/bmenu/chain.h | 347 - doc/tools/bmenu/chain.inl | 271 - doc/tools/bmenu/isr.h | 18 - doc/tools/bmenu/main.c | 1061 -- doc/tools/bmenu/system.h | 36 - doc/tools/pdl2texi/Makefile | 85 - doc/tools/pdl2texi/address.h | 110 - doc/tools/pdl2texi/address.inl | 104 - doc/tools/pdl2texi/base.h | 119 - doc/tools/pdl2texi/chain.c | 229 - doc/tools/pdl2texi/chain.h | 347 - doc/tools/pdl2texi/chain.inl | 270 - doc/tools/pdl2texi/isr.h | 18 - doc/tools/pdl2texi/main.c | 3616 ----- doc/tools/pdl2texi/s.d | 129 - doc/tools/pdl2texi/sample.d | 136 - doc/tools/pdl2texi/system.h | 36 - doc/tools/pdl2texi/test_cases/enum.d | 44 - doc/tools/pdl2texi/test_cases/enumbad.d | 48 - doc/tools/pdl2texi/test_cases/table.d | 27 - doc/tools/src2html/Makefile | 38 - doc/tools/src2html1.4a/Ctags/C.c | 444 - doc/tools/src2html1.4a/Ctags/Makefile | 15 - doc/tools/src2html1.4a/Ctags/ctags.1 | 225 - doc/tools/src2html1.4a/Ctags/ctags.c | 265 - doc/tools/src2html1.4a/Ctags/ctags.h | 81 - doc/tools/src2html1.4a/Ctags/fortran.c | 155 - doc/tools/src2html1.4a/Ctags/lisp.c | 97 - doc/tools/src2html1.4a/Ctags/print.c | 130 - doc/tools/src2html1.4a/Ctags/strerror.c | 6 - doc/tools/src2html1.4a/Ctags/tree.c | 138 - doc/tools/src2html1.4a/Ctags/yacc.c | 144 - doc/tools/src2html1.4a/Ctags/z.c | 20 - doc/tools/src2html1.4a/FreeBSD/FreeBSD.hdr | 25 - doc/tools/src2html1.4a/FreeBSD/FreeBSD.s2h | 68 - doc/tools/src2html1.4a/FreeBSD/conf.hdr | 9 - doc/tools/src2html1.4a/FreeBSD/ddb.hdr | 6 - doc/tools/src2html1.4a/FreeBSD/i386.i386.hdr | 5 - doc/tools/src2html1.4a/FreeBSD/i386.include.hdr | 5 - doc/tools/src2html1.4a/FreeBSD/i386.isa.hdr | 10 - doc/tools/src2html1.4a/FreeBSD/i386.stand.hdr | 14 - doc/tools/src2html1.4a/FreeBSD/kern.hdr | 18 - doc/tools/src2html1.4a/FreeBSD/net.hdr | 11 - doc/tools/src2html1.4a/FreeBSD/netinet.hdr | 10 - doc/tools/src2html1.4a/FreeBSD/nfs.hdr | 7 - doc/tools/src2html1.4a/FreeBSD/stand.hdr | 14 - doc/tools/src2html1.4a/FreeBSD/sys.hdr | 6 - doc/tools/src2html1.4a/FreeBSD/ufs.hdr | 10 - doc/tools/src2html1.4a/FreeBSD/vm.hdr | 9 - doc/tools/src2html1.4a/Readme | 65 - doc/tools/src2html1.4a/ctags-emacs/README | 20 - doc/tools/src2html1.4a/ctags-emacs/ctags | Bin 145997 -> 0 bytes .../src2html1.4a/ctags-emacs/etags.c-ada-patch | 424 - doc/tools/src2html1.4a/ctags-wr | 41 - doc/tools/src2html1.4a/src2html | 704 - doc/tools/src2html1.4a/src2html.1 | 244 - doc/tools/src2html1.4a/src2html.cgi | 100 - doc/tools/texi2www/Makefile | 50 - doc/tools/texi2www/archive/texi2www-960103.tgz | Bin 131143 -> 0 bytes doc/tools/texi2www/dir-arrow.gif | Bin 2609 -> 0 bytes doc/tools/texi2www/missing-arrow.gif | Bin 166 -> 0 bytes doc/tools/texi2www/next-arrow.gif | Bin 275 -> 0 bytes doc/tools/texi2www/prev-arrow.gif | Bin 279 -> 0 bytes doc/tools/texi2www/texi2dvi | 218 - doc/tools/texi2www/texi2www | 1284 -- doc/tools/texi2www/texi2www.texi | 707 - doc/tools/texi2www/up-arrow.gif | Bin 264 -> 0 bytes doc/tools/update | 221 - doc/tools/word-replace | 89 - doc/user/Makefile | 194 - doc/user/bsp.t | 318 - doc/user/c_user.texi | 170 - doc/user/clock.t | 420 - doc/user/concepts.t | 331 - doc/user/conf.t | 1502 -- doc/user/dirstat.texi | 42 - doc/user/dpmem.t | 360 - doc/user/event.t | 337 - doc/user/example.texi | 105 - doc/user/fatal.t | 170 - doc/user/glossary.texi | 771 -- doc/user/init.t | 416 - doc/user/intr.t | 467 - doc/user/io.t | 617 - doc/user/mp.t | 618 - doc/user/msg.t | 824 -- doc/user/overview.t | 532 - doc/user/part.t | 448 - doc/user/preface.texi | 189 - doc/user/region.t | 657 - doc/user/rtemsarc.gif | Bin 7653 -> 0 bytes doc/user/rtemsarc.png | Bin 5698 -> 0 bytes doc/user/rtemspie.eps | 2164 --- doc/user/rtemspie.gif | Bin 31070 -> 0 bytes doc/user/rtemspie.pdf | Bin 5715766 -> 0 bytes doc/user/rtemspie.png | Bin 31984 -> 0 bytes doc/user/rtmon.t | 1174 -- doc/user/schedule.t | 407 - doc/user/sem.t | 821 -- doc/user/signal.t | 383 - doc/user/states.eps | 13822 ------------------- doc/user/states.gif | Bin 31256 -> 0 bytes doc/user/states.pdf | Bin 488333 -> 0 bytes doc/user/states.png | Bin 22036 -> 0 bytes doc/user/task.t | 1729 --- doc/user/timer.t | 504 - doc/user/userext.t | 685 - 519 files changed, 128696 deletions(-) delete mode 100644 doc/BAD.html delete mode 100644 doc/FAQ/FAQ.texi delete mode 100644 doc/FAQ/Makefile delete mode 100644 doc/FAQ/basic.t delete mode 100644 doc/FAQ/bsp.t delete mode 100644 doc/FAQ/concepts.t delete mode 100644 doc/FAQ/debug.t delete mode 100644 doc/FAQ/embeddedinfo.t delete mode 100644 doc/FAQ/endoftime.t delete mode 100644 doc/FAQ/entry delete mode 100644 doc/FAQ/freesw.t delete mode 100644 doc/FAQ/hwdebugaids.t delete mode 100644 doc/FAQ/projects.t delete mode 100644 doc/FAQ/tools.t delete mode 100644 doc/HELP.html delete mode 100644 doc/Make.config delete mode 100644 doc/Makefile delete mode 100644 doc/README delete mode 100644 doc/TODO delete mode 100644 doc/VERSION delete mode 100644 doc/ada_user/Makefile delete mode 100644 doc/ada_user/ada_user.texi delete mode 100644 doc/ada_user/example.texi delete mode 100644 doc/archgrey.gif delete mode 100644 doc/bsp_howto/Makefile delete mode 100644 doc/bsp_howto/adaintr.t delete mode 100644 doc/bsp_howto/analog.t delete mode 100644 doc/bsp_howto/bsp_howto.texi delete mode 100644 doc/bsp_howto/clock.t delete mode 100644 doc/bsp_howto/console.t delete mode 100644 doc/bsp_howto/discrete.t delete mode 100644 doc/bsp_howto/init.t delete mode 100644 doc/bsp_howto/intro.t delete mode 100644 doc/bsp_howto/linkcmds.t delete mode 100644 doc/bsp_howto/makefiles.t delete mode 100644 doc/bsp_howto/nvmem.t delete mode 100644 doc/bsp_howto/rtc.t delete mode 100644 doc/bsp_howto/shmsupp.t delete mode 100644 doc/bsp_howto/support.t delete mode 100644 doc/bsp_howto/target.t delete mode 100644 doc/bsp_howto/timer.t delete mode 100644 doc/common/cpright.texi delete mode 100644 doc/common/dvi.gif delete mode 100644 doc/common/oaronly.jpg delete mode 100644 doc/common/pdf.gif delete mode 100644 doc/common/pdf1.gif delete mode 100644 doc/common/ps.gif delete mode 100644 doc/common/setup.texi delete mode 100644 doc/common/timemac.texi delete mode 100644 doc/common/timetbl.t delete mode 100644 doc/common/timing.t delete mode 100644 doc/common/treedef.tex delete mode 100644 doc/common/up-arrow.gif delete mode 100644 doc/common/wksheets.t delete mode 100644 doc/develenv/Makefile delete mode 100644 doc/develenv/compile.texi delete mode 100644 doc/develenv/develenv.texi delete mode 100644 doc/develenv/direct.texi delete mode 100644 doc/develenv/intro.texi delete mode 100644 doc/develenv/sample.texi delete mode 100644 doc/develenv/utils.texi delete mode 100755 doc/do_docs delete mode 100644 doc/filesystem/Makefile delete mode 100644 doc/filesystem/filesystem.texi delete mode 100644 doc/filesystem/fsrequirements.t delete mode 100644 doc/filesystem/imfs.t delete mode 100644 doc/filesystem/init.t delete mode 100644 doc/filesystem/miniimfs.t delete mode 100644 doc/filesystem/mounting.t delete mode 100644 doc/filesystem/patheval.t delete mode 100644 doc/filesystem/preface.texi delete mode 100644 doc/filesystem/syscalls.t delete mode 100644 doc/filesystem/tftp.t delete mode 100644 doc/gnu_docs/Tool_Doc_Instructions delete mode 100644 doc/gnu_docs/gen_docs delete mode 100644 doc/gnu_docs/gnu_footer.html delete mode 100644 doc/gnu_docs/gnu_header.html delete mode 100644 doc/gnu_docs/index.html delete mode 100644 doc/gnu_docs/mk_install_dir delete mode 100644 doc/gnu_docs/refcard.html delete mode 100644 doc/gnu_docs/rtems_tools_index.html delete mode 100644 doc/index.html delete mode 100644 doc/itron3.0/Makefile delete mode 100644 doc/itron3.0/config.t delete mode 100644 doc/itron3.0/eventflags.t delete mode 100644 doc/itron3.0/fixedblock.t delete mode 100644 doc/itron3.0/gen_all delete mode 100644 doc/itron3.0/gen_section delete mode 100644 doc/itron3.0/gen_status_shell delete mode 100644 doc/itron3.0/interrupt.t delete mode 100644 doc/itron3.0/itron.texi delete mode 100644 doc/itron3.0/mailbox.t delete mode 100644 doc/itron3.0/memorypool.t delete mode 100644 doc/itron3.0/msgbuffer.t delete mode 100644 doc/itron3.0/network.t delete mode 100644 doc/itron3.0/preface.texi delete mode 100644 doc/itron3.0/rendezvous.t delete mode 100644 doc/itron3.0/semaphore.t delete mode 100644 doc/itron3.0/status.t delete mode 100644 doc/itron3.0/task.t delete mode 100644 doc/itron3.0/tasksync.t delete mode 100644 doc/itron3.0/time.t delete mode 100644 doc/networking/Makefile delete mode 100644 doc/networking/PCIreg.eps delete mode 100644 doc/networking/PCIreg.jpg delete mode 100644 doc/networking/PCIreg.pdf delete mode 100644 doc/networking/decdriver.t delete mode 100644 doc/networking/driver.t delete mode 100644 doc/networking/networkapp.t delete mode 100644 doc/networking/networkflow.eps delete mode 100644 doc/networking/networkflow.jpg delete mode 100644 doc/networking/networkflow.pdf delete mode 100644 doc/networking/networkflow.png delete mode 100644 doc/networking/networking.texi delete mode 100644 doc/networking/networktasks.t delete mode 100644 doc/networking/preface.texi delete mode 100644 doc/networking/recvbd.eps delete mode 100644 doc/networking/recvbd.jpg delete mode 100644 doc/networking/recvbd.pdf delete mode 100644 doc/networking/servers.t delete mode 100644 doc/networking/testing.t delete mode 100644 doc/new_chapters/Makefile delete mode 100644 doc/new_chapters/STATUS delete mode 100644 doc/new_chapters/TODO delete mode 100644 doc/new_chapters/adminiface.t delete mode 100644 doc/new_chapters/base.t delete mode 100644 doc/new_chapters/confspace.t delete mode 100644 doc/new_chapters/cpuuse.t delete mode 100644 doc/new_chapters/dumpcontrol.t delete mode 100644 doc/new_chapters/error.t delete mode 100644 doc/new_chapters/eventlog.t delete mode 100644 doc/new_chapters/gen_section delete mode 100644 doc/new_chapters/monitor.t delete mode 100644 doc/new_chapters/new_chapters.texi delete mode 100644 doc/new_chapters/rtmonuse.t delete mode 100644 doc/new_chapters/stackchk.t delete mode 100644 doc/oaronly.jpg delete mode 100644 doc/porting/Makefile delete mode 100644 doc/porting/codetuning.t delete mode 100644 doc/porting/cpuinit.t delete mode 100644 doc/porting/cpumodels.t delete mode 100644 doc/porting/developtools.t delete mode 100644 doc/porting/idlethread.t delete mode 100644 doc/porting/interrupts.t delete mode 100644 doc/porting/miscellaneous.t delete mode 100644 doc/porting/porting.texi delete mode 100644 doc/porting/preface.texi delete mode 100644 doc/porting/prioritybitmap.t delete mode 100644 doc/porting/sourcecode.t delete mode 100644 doc/porting/taskcontext.t delete mode 100644 doc/posix1003.1/Makefile delete mode 100644 doc/posix1003.1/ch01.t delete mode 100644 doc/posix1003.1/ch02.t delete mode 100644 doc/posix1003.1/ch03.t delete mode 100644 doc/posix1003.1/ch04.t delete mode 100644 doc/posix1003.1/ch05.t delete mode 100644 doc/posix1003.1/ch06.t delete mode 100644 doc/posix1003.1/ch07.t delete mode 100644 doc/posix1003.1/ch08.t delete mode 100644 doc/posix1003.1/ch09.t delete mode 100644 doc/posix1003.1/ch10.t delete mode 100644 doc/posix1003.1/ch11.t delete mode 100644 doc/posix1003.1/ch12.t delete mode 100644 doc/posix1003.1/ch13.t delete mode 100644 doc/posix1003.1/ch14.t delete mode 100644 doc/posix1003.1/ch15.t delete mode 100644 doc/posix1003.1/ch16.t delete mode 100644 doc/posix1003.1/ch17.t delete mode 100644 doc/posix1003.1/ch18.t delete mode 100644 doc/posix1003.1/posix1003_1.texi delete mode 100644 doc/posix1003.1/preface.texi delete mode 100755 doc/posix1003.1/summarize delete mode 100644 doc/posix_users/Makefile delete mode 100644 doc/posix_users/cancel.t delete mode 100644 doc/posix_users/clock.t delete mode 100644 doc/posix_users/cond.t delete mode 100644 doc/posix_users/cspecific.t delete mode 100644 doc/posix_users/device.t delete mode 100644 doc/posix_users/files.t delete mode 100644 doc/posix_users/gen_size_report delete mode 100644 doc/posix_users/io.t delete mode 100644 doc/posix_users/key.t delete mode 100644 doc/posix_users/libc.t delete mode 100644 doc/posix_users/libm.t delete mode 100644 doc/posix_users/memorymgmt.t delete mode 100644 doc/posix_users/message.t delete mode 100644 doc/posix_users/mutex.t delete mode 100644 doc/posix_users/posix_users.texi delete mode 100644 doc/posix_users/preface.texi delete mode 100644 doc/posix_users/procenv.t delete mode 100644 doc/posix_users/process.t delete mode 100644 doc/posix_users/sched.t delete mode 100644 doc/posix_users/semaphores.t delete mode 100644 doc/posix_users/signal.t delete mode 100644 doc/posix_users/status.t delete mode 100644 doc/posix_users/systemdb.t delete mode 100644 doc/posix_users/thread.t delete mode 100644 doc/posix_users/timer.t delete mode 100644 doc/relnotes/Makefile delete mode 100644 doc/relnotes/install.texi delete mode 100644 doc/relnotes/intro.texi delete mode 100644 doc/relnotes/probrep.texi delete mode 100644 doc/relnotes/relnotes.texi delete mode 100644 doc/relnotes/status.texi delete mode 100644 doc/rgdb_specs/Makefile delete mode 100644 doc/rgdb_specs/comm.t delete mode 100644 doc/rgdb_specs/conclusion.t delete mode 100644 doc/rgdb_specs/daemon.t delete mode 100644 doc/rgdb_specs/garde.eps delete mode 100644 doc/rgdb_specs/garde.pdf delete mode 100644 doc/rgdb_specs/gdbinternals.t delete mode 100644 doc/rgdb_specs/interfacing.t delete mode 100644 doc/rgdb_specs/intro.t delete mode 100644 doc/rgdb_specs/layers.eps delete mode 100644 doc/rgdb_specs/layers.jpg delete mode 100644 doc/rgdb_specs/layers.pdf delete mode 100644 doc/rgdb_specs/objectives.t delete mode 100644 doc/rgdb_specs/process.eps delete mode 100644 doc/rgdb_specs/process.jpg delete mode 100644 doc/rgdb_specs/process.pdf delete mode 100644 doc/rgdb_specs/revision.t delete mode 100644 doc/rgdb_specs/rgdb_specs.texi delete mode 100644 doc/rgdb_specs/seqbreak.eps delete mode 100644 doc/rgdb_specs/seqbreak.jpg delete mode 100644 doc/rgdb_specs/seqbreak.pdf delete mode 100644 doc/rgdb_specs/seqdetach.eps delete mode 100644 doc/rgdb_specs/seqdetach.jpg delete mode 100644 doc/rgdb_specs/seqdetach.pdf delete mode 100644 doc/rgdb_specs/seqinit.eps delete mode 100644 doc/rgdb_specs/seqinit.jpg delete mode 100644 doc/rgdb_specs/seqinit.pdf delete mode 100644 doc/rtems_footer.html delete mode 100644 doc/rtems_gdb/Makefile delete mode 100644 doc/rtems_gdb/commands.t delete mode 100644 doc/rtems_gdb/example.t delete mode 100644 doc/rtems_gdb/intro.t delete mode 100644 doc/rtems_gdb/rtems_gdb.texi delete mode 100644 doc/rtems_gdb/started.t delete mode 100644 doc/rtems_gdb/swarch.t delete mode 100644 doc/rtems_gdb/trouble.t delete mode 100644 doc/rtems_header.html delete mode 100644 doc/rtems_support.html delete mode 100644 doc/src2html/Makefile delete mode 100644 doc/src2html/RTEMS.test delete mode 100644 doc/started/Makefile delete mode 100644 doc/started/buildc.t delete mode 100644 doc/started/buildrt.t delete mode 100644 doc/started/gdb.t delete mode 100644 doc/started/intro.t delete mode 100644 doc/started/nt.t delete mode 100644 doc/started/pictures/bit_ada.jpg delete mode 100644 doc/started/pictures/bit_ada.vsd delete mode 100644 doc/started/pictures/bit_c.jpg delete mode 100644 doc/started/pictures/bit_c.vsd delete mode 100644 doc/started/pictures/scfile10.jpg delete mode 100644 doc/started/pictures/scfile10.vsd delete mode 100644 doc/started/pictures/scfile11.jpg delete mode 100644 doc/started/pictures/scfile11.vsd delete mode 100644 doc/started/pictures/scfile12.jpg delete mode 100644 doc/started/pictures/scfile12.vsd delete mode 100644 doc/started/pictures/scfile13.jpg delete mode 100644 doc/started/pictures/scfile13.vsd delete mode 100644 doc/started/pictures/scsfile1.jpg delete mode 100644 doc/started/pictures/scsfile1.vsd delete mode 100644 doc/started/pictures/scsfile2.jpg delete mode 100644 doc/started/pictures/scsfile2.vsd delete mode 100644 doc/started/pictures/scsfile3.jpg delete mode 100644 doc/started/pictures/scsfile3.vsd delete mode 100644 doc/started/pictures/scsfile4.jpg delete mode 100644 doc/started/pictures/scsfile4.vsd delete mode 100644 doc/started/pictures/scsfile5.jpg delete mode 100644 doc/started/pictures/scsfile5.vsd delete mode 100644 doc/started/pictures/scsfile6.jpg delete mode 100644 doc/started/pictures/scsfile6.vsd delete mode 100644 doc/started/pictures/scsfile7.jpg delete mode 100644 doc/started/pictures/scsfile7.vsd delete mode 100644 doc/started/pictures/scsfile8.jpg delete mode 100644 doc/started/pictures/scsfile8.vsd delete mode 100644 doc/started/pictures/scsfile9.jpg delete mode 100644 doc/started/pictures/scsfile9.vsd delete mode 100644 doc/started/pictures/sfile12c.jpg delete mode 100644 doc/started/pictures/sfile12c.vsd delete mode 100644 doc/started/require.t delete mode 100644 doc/started/sample.t delete mode 100644 doc/started/started.texi delete mode 100644 doc/started/versions.texi delete mode 100644 doc/started_ada/Makefile delete mode 100644 doc/started_ada/buildada.t delete mode 100644 doc/started_ada/buildrt.t delete mode 100644 doc/started_ada/gdb.t delete mode 100644 doc/started_ada/intro.t delete mode 100644 doc/started_ada/require.t delete mode 100644 doc/started_ada/sample.t delete mode 100644 doc/started_ada/started_ada.texi delete mode 100644 doc/started_ada/versions.texi delete mode 100644 doc/supplements/hppa1_1/Makefile delete mode 100644 doc/supplements/hppa1_1/SIMHPPA_TIMES delete mode 100644 doc/supplements/hppa1_1/bsp.t delete mode 100644 doc/supplements/hppa1_1/callconv.t delete mode 100644 doc/supplements/hppa1_1/cpumodel.t delete mode 100644 doc/supplements/hppa1_1/cputable.t delete mode 100644 doc/supplements/hppa1_1/fatalerr.t delete mode 100644 doc/supplements/hppa1_1/hppa1_1.texi delete mode 100644 doc/supplements/hppa1_1/intr_NOTIMES.t delete mode 100644 doc/supplements/hppa1_1/memmodel.t delete mode 100644 doc/supplements/hppa1_1/preface.texi delete mode 100644 doc/supplements/hppa1_1/timeSIMHPPA.t delete mode 100644 doc/supplements/i386/FORCE386_TIMES delete mode 100644 doc/supplements/i386/Makefile delete mode 100644 doc/supplements/i386/bsp.t delete mode 100644 doc/supplements/i386/callconv.t delete mode 100644 doc/supplements/i386/cpumodel.t delete mode 100644 doc/supplements/i386/cputable.t delete mode 100644 doc/supplements/i386/fatalerr.t delete mode 100644 doc/supplements/i386/i386.texi delete mode 100644 doc/supplements/i386/intr_NOTIMES.t delete mode 100644 doc/supplements/i386/memmodel.t delete mode 100644 doc/supplements/i386/preface.texi delete mode 100644 doc/supplements/i386/timeFORCE386.t delete mode 100644 doc/supplements/i960/CVME961_TIMES delete mode 100644 doc/supplements/i960/Makefile delete mode 100644 doc/supplements/i960/bsp.t delete mode 100644 doc/supplements/i960/callconv.t delete mode 100644 doc/supplements/i960/cpumodel.t delete mode 100644 doc/supplements/i960/cputable.t delete mode 100644 doc/supplements/i960/fatalerr.t delete mode 100644 doc/supplements/i960/i960.texi delete mode 100644 doc/supplements/i960/intr_NOTIMES.t delete mode 100644 doc/supplements/i960/memmodel.t delete mode 100644 doc/supplements/i960/preface.texi delete mode 100644 doc/supplements/i960/timeCVME961.t delete mode 100644 doc/supplements/m68k/MVME136_TIMES delete mode 100644 doc/supplements/m68k/Makefile delete mode 100644 doc/supplements/m68k/bsp.t delete mode 100644 doc/supplements/m68k/callconv.t delete mode 100644 doc/supplements/m68k/cpumodel.t delete mode 100644 doc/supplements/m68k/cputable.t delete mode 100644 doc/supplements/m68k/fatalerr.t delete mode 100644 doc/supplements/m68k/intr_NOTIMES.t delete mode 100644 doc/supplements/m68k/m68k.texi delete mode 100644 doc/supplements/m68k/memmodel.t delete mode 100644 doc/supplements/m68k/preface.texi delete mode 100644 doc/supplements/m68k/timeMVME136.t delete mode 100644 doc/supplements/m68k/timedata.t delete mode 100644 doc/supplements/mips64orion/BSP_TIMES delete mode 100644 doc/supplements/mips64orion/Makefile delete mode 100644 doc/supplements/mips64orion/bsp.t delete mode 100644 doc/supplements/mips64orion/callconv.t delete mode 100644 doc/supplements/mips64orion/cpumodel.t delete mode 100644 doc/supplements/mips64orion/cputable.t delete mode 100644 doc/supplements/mips64orion/fatalerr.t delete mode 100644 doc/supplements/mips64orion/intr_NOTIMES.t delete mode 100644 doc/supplements/mips64orion/memmodel.t delete mode 100644 doc/supplements/mips64orion/mips64orion.texi delete mode 100644 doc/supplements/mips64orion/preface.texi delete mode 100644 doc/supplements/mips64orion/timeBSP.t delete mode 100644 doc/supplements/powerpc/DMV177_TIMES delete mode 100644 doc/supplements/powerpc/Makefile delete mode 100644 doc/supplements/powerpc/PSIM_TIMES delete mode 100644 doc/supplements/powerpc/bsp.t delete mode 100644 doc/supplements/powerpc/callconv.t delete mode 100644 doc/supplements/powerpc/cpumodel.t delete mode 100644 doc/supplements/powerpc/cputable.t delete mode 100644 doc/supplements/powerpc/fatalerr.t delete mode 100644 doc/supplements/powerpc/intr_NOTIMES.t delete mode 100644 doc/supplements/powerpc/memmodel.t delete mode 100644 doc/supplements/powerpc/powerpc.texi delete mode 100644 doc/supplements/powerpc/preface.texi delete mode 100644 doc/supplements/powerpc/timeDMV177.t delete mode 100644 doc/supplements/powerpc/timePSIM.t delete mode 100644 doc/supplements/sh/BSP_TIMES delete mode 100644 doc/supplements/sh/Makefile delete mode 100644 doc/supplements/sh/bsp.t delete mode 100644 doc/supplements/sh/callconv.t delete mode 100644 doc/supplements/sh/cpumodel.t delete mode 100644 doc/supplements/sh/cputable.t delete mode 100644 doc/supplements/sh/fatalerr.t delete mode 100644 doc/supplements/sh/intr_NOTIMES.t delete mode 100644 doc/supplements/sh/memmodel.t delete mode 100644 doc/supplements/sh/preface.texi delete mode 100644 doc/supplements/sh/sh.texi delete mode 100644 doc/supplements/sh/timeBSP.t delete mode 100644 doc/supplements/sparc/ERC32_TIMES delete mode 100644 doc/supplements/sparc/Makefile delete mode 100644 doc/supplements/sparc/bsp.t delete mode 100644 doc/supplements/sparc/callconv.t delete mode 100644 doc/supplements/sparc/cpumodel.t delete mode 100644 doc/supplements/sparc/cputable.t delete mode 100644 doc/supplements/sparc/fatalerr.t delete mode 100644 doc/supplements/sparc/intr_NOTIMES.t delete mode 100644 doc/supplements/sparc/memmodel.t delete mode 100644 doc/supplements/sparc/preface.texi delete mode 100644 doc/supplements/sparc/sparc.texi delete mode 100644 doc/supplements/sparc/timeERC32.t delete mode 100644 doc/supplements/template/BSP_TIMES delete mode 100644 doc/supplements/template/Makefile delete mode 100644 doc/supplements/template/bsp.t delete mode 100644 doc/supplements/template/callconv.t delete mode 100644 doc/supplements/template/cpumodel.t delete mode 100644 doc/supplements/template/cputable.t delete mode 100644 doc/supplements/template/fatalerr.t delete mode 100644 doc/supplements/template/intr_NOTIMES.t delete mode 100644 doc/supplements/template/memmodel.t delete mode 100644 doc/supplements/template/preface.texi delete mode 100644 doc/supplements/template/template.texi delete mode 100644 doc/supplements/template/timeBSP.t delete mode 100644 doc/texinfo/texinfo.tex delete mode 100644 doc/tools/bmenu/Makefile delete mode 100644 doc/tools/bmenu/address.h delete mode 100644 doc/tools/bmenu/address.inl delete mode 100644 doc/tools/bmenu/base.h delete mode 100644 doc/tools/bmenu/chain.c delete mode 100644 doc/tools/bmenu/chain.h delete mode 100644 doc/tools/bmenu/chain.inl delete mode 100644 doc/tools/bmenu/isr.h delete mode 100644 doc/tools/bmenu/main.c delete mode 100644 doc/tools/bmenu/system.h delete mode 100644 doc/tools/pdl2texi/Makefile delete mode 100644 doc/tools/pdl2texi/address.h delete mode 100644 doc/tools/pdl2texi/address.inl delete mode 100644 doc/tools/pdl2texi/base.h delete mode 100644 doc/tools/pdl2texi/chain.c delete mode 100644 doc/tools/pdl2texi/chain.h delete mode 100644 doc/tools/pdl2texi/chain.inl delete mode 100644 doc/tools/pdl2texi/isr.h delete mode 100644 doc/tools/pdl2texi/main.c delete mode 100644 doc/tools/pdl2texi/s.d delete mode 100644 doc/tools/pdl2texi/sample.d delete mode 100644 doc/tools/pdl2texi/system.h delete mode 100644 doc/tools/pdl2texi/test_cases/enum.d delete mode 100644 doc/tools/pdl2texi/test_cases/enumbad.d delete mode 100644 doc/tools/pdl2texi/test_cases/table.d delete mode 100644 doc/tools/src2html/Makefile delete mode 100644 doc/tools/src2html1.4a/Ctags/C.c delete mode 100644 doc/tools/src2html1.4a/Ctags/Makefile delete mode 100644 doc/tools/src2html1.4a/Ctags/ctags.1 delete mode 100644 doc/tools/src2html1.4a/Ctags/ctags.c delete mode 100644 doc/tools/src2html1.4a/Ctags/ctags.h delete mode 100644 doc/tools/src2html1.4a/Ctags/fortran.c delete mode 100644 doc/tools/src2html1.4a/Ctags/lisp.c delete mode 100644 doc/tools/src2html1.4a/Ctags/print.c delete mode 100644 doc/tools/src2html1.4a/Ctags/strerror.c delete mode 100644 doc/tools/src2html1.4a/Ctags/tree.c delete mode 100644 doc/tools/src2html1.4a/Ctags/yacc.c delete mode 100644 doc/tools/src2html1.4a/Ctags/z.c delete mode 100644 doc/tools/src2html1.4a/FreeBSD/FreeBSD.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/FreeBSD.s2h delete mode 100644 doc/tools/src2html1.4a/FreeBSD/conf.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/ddb.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/i386.i386.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/i386.include.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/i386.isa.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/i386.stand.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/kern.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/net.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/netinet.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/nfs.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/stand.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/sys.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/ufs.hdr delete mode 100644 doc/tools/src2html1.4a/FreeBSD/vm.hdr delete mode 100644 doc/tools/src2html1.4a/Readme delete mode 100644 doc/tools/src2html1.4a/ctags-emacs/README delete mode 100644 doc/tools/src2html1.4a/ctags-emacs/ctags delete mode 100644 doc/tools/src2html1.4a/ctags-emacs/etags.c-ada-patch delete mode 100644 doc/tools/src2html1.4a/ctags-wr delete mode 100644 doc/tools/src2html1.4a/src2html delete mode 100644 doc/tools/src2html1.4a/src2html.1 delete mode 100644 doc/tools/src2html1.4a/src2html.cgi delete mode 100644 doc/tools/texi2www/Makefile delete mode 100644 doc/tools/texi2www/archive/texi2www-960103.tgz delete mode 100644 doc/tools/texi2www/dir-arrow.gif delete mode 100644 doc/tools/texi2www/missing-arrow.gif delete mode 100644 doc/tools/texi2www/next-arrow.gif delete mode 100644 doc/tools/texi2www/prev-arrow.gif delete mode 100644 doc/tools/texi2www/texi2dvi delete mode 100755 doc/tools/texi2www/texi2www delete mode 100644 doc/tools/texi2www/texi2www.texi delete mode 100644 doc/tools/texi2www/up-arrow.gif delete mode 100644 doc/tools/update delete mode 100755 doc/tools/word-replace delete mode 100644 doc/user/Makefile delete mode 100644 doc/user/bsp.t delete mode 100644 doc/user/c_user.texi delete mode 100644 doc/user/clock.t delete mode 100644 doc/user/concepts.t delete mode 100644 doc/user/conf.t delete mode 100644 doc/user/dirstat.texi delete mode 100644 doc/user/dpmem.t delete mode 100644 doc/user/event.t delete mode 100644 doc/user/example.texi delete mode 100644 doc/user/fatal.t delete mode 100644 doc/user/glossary.texi delete mode 100644 doc/user/init.t delete mode 100644 doc/user/intr.t delete mode 100644 doc/user/io.t delete mode 100644 doc/user/mp.t delete mode 100644 doc/user/msg.t delete mode 100644 doc/user/overview.t delete mode 100644 doc/user/part.t delete mode 100644 doc/user/preface.texi delete mode 100644 doc/user/region.t delete mode 100644 doc/user/rtemsarc.gif delete mode 100644 doc/user/rtemsarc.png delete mode 100644 doc/user/rtemspie.eps delete mode 100644 doc/user/rtemspie.gif delete mode 100644 doc/user/rtemspie.pdf delete mode 100644 doc/user/rtemspie.png delete mode 100644 doc/user/rtmon.t delete mode 100644 doc/user/schedule.t delete mode 100644 doc/user/sem.t delete mode 100644 doc/user/signal.t delete mode 100644 doc/user/states.eps delete mode 100644 doc/user/states.gif delete mode 100644 doc/user/states.pdf delete mode 100644 doc/user/states.png delete mode 100644 doc/user/task.t delete mode 100644 doc/user/timer.t delete mode 100644 doc/user/userext.t (limited to 'doc') diff --git a/doc/BAD.html b/doc/BAD.html deleted file mode 100644 index 7be09d069a..0000000000 --- a/doc/BAD.html +++ /dev/null @@ -1,22 +0,0 @@ - -RTEMS 4.0.0 On-Line Library - - - OAR -

RTEMS On-Line Library

-
- -The following manuals do not currently exist in PDF: - -
  • Getting Started with RTEMS for C/C++ Users
    • -
  • Getting Started with GNAT/RTEMS
    • -     -These can not be generated due to a bug in the texi2pdf processor -that results in variables not being expanded in the @uref command. -This has been reported to the maintainers. If you are interested -in fixing this or have a fix for this bug, please contact -rtems@OARcorp.com. - -
    -Copyright © 1988-2000 OAR Corporation - diff --git a/doc/FAQ/FAQ.texi b/doc/FAQ/FAQ.texi deleted file mode 100644 index 45b68b1004..0000000000 --- a/doc/FAQ/FAQ.texi +++ /dev/null @@ -1,123 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c %**start of header -@setfilename FAQ -@syncodeindex vr fn -@synindex ky cp -@paragraphindent 0 -@c @smallbook -@c %**end of header - -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Master file for the RTEMS FAQ -@c - -@include ../common/setup.texi - -@ignore -@ifinfo -@format -START-INFO-DIR-ENTRY -* RTEMS Frequently Asked Questions (FAQ): -END-INFO-DIR-ENTRY -@end format -@end ifinfo -@end ignore - -@c -@c Title Page Stuff -@c - -@set edition @value{RTEMS-EDITION} -@set version @value{RTEMS-VERSION} -@set update-date @value{RTEMS-UPDATE-DATE} -@set update-month @value{RTEMS-UPDATE-MONTH} - -@c -@c I don't really like having a short title page. --joel -@c -@c @shorttitlepage RTEMS Frequently Asked Questions - -@setchapternewpage odd -@settitle RTEMS Frequently Asked Questions -@titlepage -@finalout - -@title RTEMS Frequently Asked Questions -@subtitle Edition @value{edition}, for @value{version} -@sp 1 -@subtitle @value{update-month} -@author On-Line Applications Research Corporation -@page -@include ../common/cpright.texi -@end titlepage - -@c This prevents a black box from being printed on "overflow" lines. -@c The alternative is to rework a sentence to avoid this problem. - -@include basic.texi -@include tools.texi -@include concepts.texi -@include bsp.texi -@include debug.texi -@include freesw.texi -@include embeddedinfo.texi -@include hwdebugaids.texi -@include projects.texi -@include endoftime.texi - -@ifinfo -@node Top, Basic Information, (dir), (dir) -@top FAQ - -This document is the RTEMS FAQ. FAQ is an acronym for Frequently -Asked Questions and we sincerely hope that this contains the answers -to some of the questions most frequently asked about RTEMS. - -Common questions have been divided into the following categories. - - -@menu -* Basic Information:: -* General Development Tool Hints:: -* RTEMS Concepts:: -* BSP Questions:: -* Debugging Hints:: -* Free Software that Works with RTEMS:: -* Resources for Embedded Information:: -* Hardware to Ease Debugging:: -* RTEMS Projects:: -* Date/Time Issues in Systems Using RTEMS:: -@end menu - -@c * Command and Variable Index:: -@c * Concept Index:: -@end ifinfo -@c -@c -@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here -@c - -@c @node Command and Variable Index, Concept Index, Installing EGCS AND NEWLIB, Top -@c @unnumbered Command and Variable Index - -@c There are currently no Command and Variable Index entries. - -@c @printindex fn - -@c @node Concept Index, , Command and Variable Index, Top -@c @unnumbered Concept Index - -@c There are currently no Concept Index entries. -@c @printindex cp - -@contents -@bye - diff --git a/doc/FAQ/Makefile b/doc/FAQ/Makefile deleted file mode 100644 index 4ddee5e6f1..0000000000 --- a/doc/FAQ/Makefile +++ /dev/null @@ -1,117 +0,0 @@ -# -# COPYRIGHT (c) 1988-1999. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=FAQ - -include ../Make.config - -all: html info ps pdf - -dirs: - $(make-dirs) - -COMMON_FILES=../common/cpright.texi ../common/setup.texi - -GENERATED_FILES= \ - basic.texi tools.texi concepts.texi bsp.texi debug.texi freesw.texi \ - embeddedinfo.texi hwdebugaids.texi projects.texi endoftime.texi - -FILES=$(PROJECT).texi $(GENERATED_FILES) - -INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*) - -info: dirs $(PROJECT) - #cp $(wildcard $(PROJECT) $(PROJECT)-*) $(INFO_INSTALL) - # cp $(PROJECT) $(INFO_INSTALL) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: dirs $(PROJECT).dvi -ps: dirs $(PROJECT).ps -pdf: dirs $(PROJECT).pdf - -$(PROJECT).pdf: $(FILES) - $(TEXI2PDF) $(PROJECT).texi - cp $(PROJECT).pdf $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).ps: $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - cp $(PROJECT).dvi $(WWW_INSTALL)/$(PROJECT) - -html: dirs $(FILES) - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -clean: - rm -f *.o $(PROG) *.txt core $(PROJECT).pdf - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* $(GENERATED_FILES) - rm -f *.fixed _* - - -# -# Process Automatically Generated Files -# - -basic.texi: basic.t Makefile - $(BMENU) -c -p "Top" \ - -u "Top" \ - -n "" ${*}.t - -tools.texi: tools.t Makefile - $(BMENU) -c -p "Top" \ - -u "Top" \ - -n "" ${*}.t - -concepts.texi: concepts.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - -bsp.texi: bsp.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - -debug.texi: debug.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - -freesw.texi: freesw.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - -embeddedinfo.texi: embeddedinfo.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - -hwdebugaids.texi: hwdebugaids.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - -projects.texi: projects.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - - -endoftime.texi: endoftime.t Makefile - $(BMENU) -c -p "" \ - -u "Top" \ - -n "" ${*}.t - diff --git a/doc/FAQ/basic.t b/doc/FAQ/basic.t deleted file mode 100644 index 4f653650f9..0000000000 --- a/doc/FAQ/basic.t +++ /dev/null @@ -1,177 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Basic Information - -The questions in this category are basic questions about RTEMS. Where -did it come from, why is it, what is it, when should you use it, etc.? - -@section What does RTEMS stand for? - -RTEMS is an anacronym for the Real-Time Executive for Multiprocessor -Systems. - -Initially RTEMS stood for the Real-Time Executive for Missile Systems -but as it became clear that the application domains that could use -RTEMS extended far beyond missiles, the "M" changed to mean Military. -At one point, there were both Ada and C implementations of RTEMS. The -C version changed the "M" to mean Multiprocessor while the Ada version -remained with the "M" meaning Military. - -@section What is RTEMS? - -RTEMS is a real-time executive which provides a high performance -environment for embedded military applications including many -features. The following is just a short list of the features -avilable in RTEMS. If you are interested in something that -is not on this list, please contact the RTEMS Team. Features -are being added continuously. - -@itemize @bullet - -@item Standards Compliant -@itemize @bullet -@item POSIX 1003.1b API including threads -@item RTEID/ORKID based Classic API -@end itemize - -@item TCP/IP Stack -@itemize @bullet -@item high performance port of FreeBSD TCP/IP stack -@item UDP, TCP -@item ICMP, DHCP, RARP -@item TFTP -@item RPC -@item FTPD -@item HTTPD -@item CORBA -@end itemize - -@item Debugging -@itemize @bullet -@item GNU debugger (gdb) -@item DDD GUI interface to GDB -@item thread aware -@item debug over Ethernet -@item debug over Serial Port -@end itemize - -@item Filesystem Support -@itemize @bullet -@item In-Memory Filesystem (IMFS) -@item TFTP Client Filesystem -@end itemize - -@item Basic Kernel Features -@itemize @bullet -@item multitasking capabilities -@item homogeneous and heterogeneous multiprocessor systems -@item event-driven, priority-based, preemptive scheduling -@item optional rate monotonic scheduling -@item intertask communication and synchronization -@item priority inheritance -@item responsive interrupt management -@item dynamic memory allocation -@item high level of user configurability -@end itemize - -@end itemize - - -@section What standards does RTEMS support? - -The original "Classic" RTEMS API is based on the Real-Time Executive -Interface Definition (RTEID) and the Open Real-Time Kernel Interface -Definition (ORKID). RTEMS also includes support for POSIX threads -and real-time extensions. - -With the addition of file system infrastructure, RTEMS supports -about 70% of the POSIX 1003.1b-1996 standard. This standard -defines the programming interfaces of standard UNIX. This means -that much source code that works on UNIX, also works on RTEMS. - -@section What processors is RTEMS available for? - -RTEMS is available for the following processor families: - -@itemize @bullet -@item Motorola MC68xxx -@item Motorola MC683xx -@item Motorola ColdFire -@item Hitachi SH -@item Intel i386 -@item Intel i960 -@item MIPS -@item PowerPC -@item SPARC -@item AMD A29K -@item Hewlett-Packard PA-RISC -@end itemize - -In addition, there is a port to UNIX which can be used as a prototyping -and simulation environment. - -@section Executive vs. Kernel vs. Operating System (RTOS) - -The developers of RTEMS developers use the terms executive and kernel -interchangeably. In the embedded system community, the terms executive -or kernel are generally used to refer to small operating systems. -So we consider it proper to refer to RTEMS as an executive, a kernel, -or an operating system. - -@section Where/why was it developed? - -RTEMS was developed by On-Line Applications Research Corporation (OAR) -for the U.S. Army Missile Command prior to that organizations merger -with the Aviation Command that resulted in the new command, U. S. Army -Aviation and Missile command (AMCOM). The original goal of RTEMS was -to provide a portable, standards-based real-time executive for which -source code was available and royalties were paid. - -In other words, RTEMS was open source before open source was cool. - -@section Are there no similar commercial products? - -Yes, but not all are based on standards and the open source philosophy. - -@section How can I get RTEMS? - -RTEMS is distributed by OAR Corporation via the Internet. Point your -favorite browser at the following URL and following the link: - -@c this version should work -@c @set OAR-URL http://www.OARcorp.com -@c @uref{@value{OAR-URL},@value{OAR-URL}} -@uref{http://www.OARcorp.com,http://www.OARcorp.com} - -@section What about support? - -OAR Corporation provides numerous services for RTEMS including support, -training, and custom development. - -@section Are there any mailing lists? - -The primary RTEMS mailing list is @code{rtems-list@@oarcorp.com}. You -can subscribe by sending a message with the word @b{subscribe rtems-list} -as the body to @code{majordomo@@oarcorp.com}. - -@section Are there any license restrictions? - -RTEMS is licensed under a modified version of the GNU General Public License -(GPL). The modification places no restrictions on the applications which -use RTEMS but protects the interests of those who work on RTEMS. - -The TCP/IP network stack included with RTEMS is a port of the FreeBSD -network stack and is licensed under different terms that also do not -place restrictions on the application. - -@section Are there any export restrictions? - -No. - - diff --git a/doc/FAQ/bsp.t b/doc/FAQ/bsp.t deleted file mode 100644 index 1e8488aab6..0000000000 --- a/doc/FAQ/bsp.t +++ /dev/null @@ -1,35 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter BSP Questions - -The items in this category provide answers to questions -commonly asked about BSPs. - -@section What is a BSP? - -BSP is an acronym for Board Support Package. - -A BSP is a collection of device drivers, startup code, linker scripts, -and compiler support files (specs files) that tailor RTEMS for a -particular target hardware environment. - -@section What has to be in a BSP? - -The basic set of items is the linker script, bsp_specs, and startup code. -If you want standard IO, then you need a console driver. This is needed -to run any of the RTEMS tests. If you want to measure passage of time, -you need a clock tick driver. This driver is needed for all RTEMS tests -EXCEPT hello world and the timing tests. The timer driver is a benchmark -timer and is needed for the tmtests (timing tests). Sometimes you will -see a shmsupp directory which is for shared memory multiprocessing -systems. The network driver and real-time clock drivers are optional -and not reqired by any RTEMS tests. - - - diff --git a/doc/FAQ/concepts.t b/doc/FAQ/concepts.t deleted file mode 100644 index 1ad0bdf657..0000000000 --- a/doc/FAQ/concepts.t +++ /dev/null @@ -1,19 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter RTEMS Concepts - -The questions in this category are hints that help basic understanding. - -@section RTEMS Workspace versus Program Heap - -The RTEMS Workspace is used to allocate space for objects created -by RTEMS such as tasks, semaphores, message queues, etc.. It is -primarily used during system initialization although task stacks -and message buffer areas are also allocated from here. -@ref{How do I determine how much memory is left?}. diff --git a/doc/FAQ/debug.t b/doc/FAQ/debug.t deleted file mode 100644 index c5da7d1349..0000000000 --- a/doc/FAQ/debug.t +++ /dev/null @@ -1,100 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Debugging Hints - -The questions in this category are hints that can ease debugging. - -@section Malloc - -@subsection Is malloc reentrant? - -Yes. The RTEMS Malloc implementation is reentrant. It is -implemented as calls to the Region Manager in the Classic API. - -@subsection When is malloc initialized? - -During BSP initialization, the @code{bsp_libc_init} routine -is called. This routine initializes the heap as well as -the RTEMS system call layer (open, read, write, etc.) and -the RTEMS reentrancy support for the Cygnus newlib Standard C -Library. - -The @code{bsp_libc_init} routine is passed the size and starting -address of the memory area to be used for the program heap as well -as the amount of memory to ask @code{sbrk} for when the heap is -exhausted. For most BSPs, all memory available is placed in the -program heap thus it can not be extended dynamically by calls to -@code{sbrk}. - -@section How do I determine how much memory is left? - -First there are two types of memory: RTEMS Workspace and Program Heap. -The RTEMS Workspace is the memory used by RTEMS to allocate control -structures for system objects like tasks and semaphores, task -stacks, and some system data structures like the ready chains. -The Program Heap is where "malloc'ed" memory comes from. - -Both are essentially managed as heaps based on the Heap Manager -in the RTEMS SuperCore. The RTEMS Workspace uses the Heap Manager -directly while the Program Heap is actually based on an RTEMS Region -from the Classic API. RTEMS Regions are in turn based on the Heap -Manager in the SuperCore. - -@subsection How much memory is left in the RTEMS Workspace? - -An executive workspace overage can be fairly easily spotted with a -debugger. Look at _Workspace_Area. If first == last, then there is only -one free block of memory in the workspace (very likely if no task -deletions). Then do this: - -(gdb) p *(Heap_Block *)_Workspace_Area->first -$3 = @{back_flag = 1, front_flag = 68552, next = 0x1e260, previous = 0x1e25c@} - -In this case, I had 68552 bytes left in the workspace. - -@subsection How much memory is left in the Heap? - -The C heap is a region so this should work: - -(gdb) p *((Region_Control *)_Region_Information->local_table[1])->Memory->first -$9 = @{back_flag = 1, front_flag = 8058280, next = 0x7ea5b4, - previous = 0x7ea5b0@} - -In this case, the first block on the C Heap has 8,058,280 bytes left. - -@section How do I convert an executable to IEEE-695? - -This section is based on an email from Andrew Bythell - in July 1999. - -Using Objcopy to convert m68k-coff to IEEE did not work. The new IEEE -object could not be read by tools like the XRay BDM Debugger. - -The exact nature of this problem is beyond me, but I did narrow it down to a -problem with objcopy in binutils 2-9.1. To no surprise, others have -discovered this problem as well, as it has been fixed in later releases. - -I compiled a snapshot of the development sources from 07/26/99 and -everything now works as it should. The development sources are at -@uref{http://sourceware.cygnus.com/binutils} (thanks Ian!) - -Additional notes on converting an m68k-coff object for use with XRay (and -others): - -@enumerate - - -@item The m68k-coff object must be built with the -gstabs+ flag. The -g flag -alone didn't work for me. - -@item Run Objcopy with the --debugging flag to copy debugging information. - -@end enumerate - - diff --git a/doc/FAQ/embeddedinfo.t b/doc/FAQ/embeddedinfo.t deleted file mode 100644 index 056f7c3ebc..0000000000 --- a/doc/FAQ/embeddedinfo.t +++ /dev/null @@ -1,38 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Resources for Embedded Information - -The items in this category provide pointers to other resources. - -@section General Information - -@section CrossGCC - -@uref{http://www.objsw.com} - -@section CPU Family Specific Forums - -@subsection Motorola M68xxx and ColdFire - -David Fiddes maintains a fabulous site on ColdFire and MC68xxx embedded -development. It is at @uref{http://www.calm.hw.ac.uk/davidf/coldfire/}. - -Motorola has a lot of information at @uref{http://www.mot.com/SPS/HPESD/index.html}. - -@subsection Hitach SH - -@subsection Hitach H8 - -@subsection MIPS - -@subsection PowerPC - -@subsection SPARC - -Jiri's ERC32 Site diff --git a/doc/FAQ/endoftime.t b/doc/FAQ/endoftime.t deleted file mode 100644 index 5f6d3592ca..0000000000 --- a/doc/FAQ/endoftime.t +++ /dev/null @@ -1,111 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Date/Time Issues in Systems Using RTEMS - -This section provides technical information regarding -date/time representation issues and RTEMS. The Y2K problem has -lead numerous people to ask these questions. The answer to -these questions are actually more complicated than most -people asking the question expect. RTEMS supports multiple -standards and each of these standards has its own epoch and -time representation. These standards include both programming -API and programming language standards. - -In addition to the issues inside RTEMS -itself, there is the complicating factor that the Board -Support Package or application itself may interface with hardware -or software that has its own set of date/time representation -issues. - -In conclusion, viewing date/time representation as "the Y2K problem" -is very short-sighted. Date/time representation should be viewed as -a systems level issue for the system you are building. Each software -and hardware component in the system as well as the systems being -connected to is a factor in the equation. - -@section Hardware Issues - -Numerous Real-Time Clock (RTC) controllers provide only a two-digit -Binary Coded Decimal (BCD) representation for the current year. Without -software correction, these chips are a classic example of the Y2K problem. -When the RTC rolls the year register over from 99 to 00, the device -has no idea whether the year is 1900 or 2000. It is the responsibility -of the device driver to recognize this condition and correct for it. -The most common technique used is to assume that all years prior -to either the existence of the board or RTEMS are past 2000. The -starting year (epoch) for RTEMS is 1988. Thus, - -@itemize @bullet -@item Chip year values 88-99 are interpreted as years 1988-1999. -@item Chip year values 00-87 are interpreted as years 2000-2087. -@end itemize - -Using this technique, a RTC using a -two-digit BCD representation of the current year will overflow on -January 1, 2088. - -@section RTEMS Specific Issues - -Internally, RTEMS uses an unsigned thirty-two bit integer to represent the -number of seconds since midnight January 1, 1988. This counter will -overflow on February 5, 2124. - -The time/date services in the Classic API will overflow when the -RTEMS internal date/time representation overflows. - -The POSIX API uses the type @i{time_t} to represent the number of -seconds since January 1, 1970. Many traditional UNIX systems as -well as RTEMS define @i{time_t} as a signed thirty-two bit integer. -This representation overflows on January 18, 2038. The solution -usually proposed is to define @i{time_t} as a sixty-four bit -integer. This solution is appropriate for for UNIX workstations -as many of them already support sixty-four bit integers natively. -At this time, this imposes a burden on embedded systems which are -still primarily using processors with native integers of thirty-two -bits or less. - -@section Language Specific Issues - -The Ada95 Language Reference Manual requires that the @i{Ada.Calendar} -package support years through the year 2099. However, just as the -hardware is layered on top of hardware and may inherit its limits, -the Ada tasking and run-time support is layered on top of an operating -system. Thus, if the operating system or underlying hardware fail -to correctly report dates after 2099, then it is possible for the -@i{Ada.Calendar} package to fail prior to 2099. - -@section Date/Time Conclusion - -Each embedded system could be impacted by a variety of date/time -representation issues. Even whether a particular date/time -repsentation issue impacts a system is questionable. A system -using only the RTEMS Classic API is not impacted by the -date/time representation issues in POSIX. A system not using -date/time at all is not impacted by any of these issues. Also -the planned end of life for a system may make these issues -moot. - -The following is a timeline of the date/time representation -issues presented in this section: - -@itemize @bullet - -@item 2000 - Two BCD Digit Real-Time Clock Rollover - -@item 2038 - POSIX @i{time_t} Rollover - -@item 2088 - Correction for Two BCD Digit Real-Time Clock Rollover - -@item 2099 - Ada95 @i{Ada.Calendar} Rollover - -@item 2124 - RTEMS Internal Seconds Counter Rollover - -@end itemize - - diff --git a/doc/FAQ/entry b/doc/FAQ/entry deleted file mode 100644 index 7a6be8d8ca..0000000000 --- a/doc/FAQ/entry +++ /dev/null @@ -1,57 +0,0 @@ -# -# $Id$ -# - -This is the RTEMS entry in the Crossgcc FAQ at @uref{http://www.objsw.com}. -As of 8/19/99, it has been submitted twice and the FAQ not updated. - -RTEMS is a freely available, royalty free real-time executive with -multiprocessor capabilities. RTEMS' design provides performance and -capabilities are comparable to those of the best commercial executives. -The directive execution times and other critical performance measures such -as interrupt latency are best of class. RTEMS was developed by On-Line -Applications Research Corporation (OAR) under contract to the U.S. Army -Missile Command. - - -RTEMS includes support for multiple APIs. Currently RTEMS supports a -POSIX threads API, and an RTEID based API which is similar to pSOS+. -RTEMS includes a number of advanced real-time features including optional -rate monotonic scheduling support, binary semapahores with priority -inheritance, and watchdog timer functions. - -RTEMS includes a port of the FreeBSD TCP/IP stack that has high -performance on very modest hardware. A remote debug server is supported -on some targets that allows debugging across the network. - -RTEMS provides a rich run-time environment with a reentrant C library, -POSIX 1003.1b support, and file system support. It also includes optional -debug aids like stack overflow and heap integrity checking. - -RTEMS is built using GNU autoconf and can be built on any host supporting -the GNU tools including Linux, FreeBSD, NetBSD, Solaris, and MS-Windows to -name but a few. The current RTEMS release supports a the following CPU -families: - - Motorola m680x0, m683xx, and ColdFire - Motorola and IBM PowerPC (4xx, 6xx, 7xx, and 8xx) - Hitachi SH-1 - Intel i386, i486, Pentium, and i960 - SPARC - MIPS - HP PA-RISC - AMD A29K - -There are over 35 Board Support Packages included with RTEMS including -BSPs for the SPARC and PowerPC simulators included with gdb. There are -numerous BSPs for CPUs targetting the embedded market such as the Motorola -m683xx and mpc8xx series which support the on-CPU peripherals. - -WWW: - -@uref{http://www.OARcorp.com} - -E-mail: - -@code{rtems-info@@OARcorp.com} - diff --git a/doc/FAQ/freesw.t b/doc/FAQ/freesw.t deleted file mode 100644 index 03e5c6585f..0000000000 --- a/doc/FAQ/freesw.t +++ /dev/null @@ -1,162 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Free Software that Works with RTEMS - -This section describes other free software packages that are known to work -with RTEMS. - -@section Development Tools - -@subsection Basic Development Environment - -The standard RTEMS development environment consists of the following GNU -components: - -@itemize @bullet - -@item gcc/egcs -@item binutils -@item gdb - -@end itemize - -Although not from the Free Software Foundation, the Cygnus newlib C -library integrates well with the GNU tools and is a standard part of the -RTEMS development environment. - -@subsection GNU Ada - -For those interested in using the Ada95 programming language, the GNU Ada -compiler (GNAT) is available and has excellent support for RTEMS. - -@subsection DDD - Data Display Debugger - -By far the easiest way to use DDD if you are on a Redhat Linux system is -to retrieve the RPM package for your OS version. In general, it is -easier to install a static binary since doing so avoids all problems -with dynamic library versions. - -Some versions of DDD have had trouble with Lesstif. If you -are using Lesstiff, you will need version 0.88 or newer. It -is also available as an RPM at the popular sites. Another Motif -clone is Motive and versions 1.2 and newer known to work with DDD -on popular distributions of Linux including RedHat and Slackware. - -Installed as RPMs, DDD in conjunction with either Lesstif or Motive -should work out-of-the-box. - -User comments indicate that both Lesstif and DDD can be built -from scratch without any problems. Instructions on installing -Lesstif are at @uref{http://www.cs.tu-bs.de/softech/ddd/}. They -indicate that - -@itemize @bullet -LessTif should be used in (default) Motif 1.2 compatibility mode. - -The Motif 2.0 compatibility mode of LessTif is still incomplete. -@end itemize - -So configure lesstif with --enable-default-12. - -The configure script is broken (see www.lesstif.org --> known problems) -for 0.88.1. I didn't fix the script as they show, so I just have links -in /usr/local/lib (also shown). - -Watch out: Lesstif installs its libraries in /usr/local/Lesstif. You -will need to update /etc/ld.so.conf and regenerate the cache of shared -library paths to point to the Motif 1.2 library. - -The following notes are from an RTEMS user who uses DDD in conjunction -with Lesstif. Configure DDD "--with-motif-libraries=/usr/local/lib ---with-motif-includes=/usr/local/include" DDD needs gnuplot 3.7. -@uref{ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot-3.7.tar.gz}. Build and -install from scratch. - -DDD can be started from a script that specifies the cross debugger. -This simplifies the invocation. The following example shows what -a script doing this looks like. - -@example -#!/bin/bash -ddd --debugger m68k-elf-gdb $1 -@end example - -Under many flavors of UNIX, you will likely have to relax permissions. - -On Linux, to get gdb to use the serial ports while running as a -normal user, edit /etc/security/console.perms, and create a -class (call it whatever you want). - -@example -=/dev/ttyS* /dev/cua* -@end example - -Now enable the change of ownership of these devices when users log in -from the console: - -@example - 0600 0600 root -@end example - -Users report using minicom to communicate with the target to initiate a TFTP -download. They then suspend minicom, launch DDD, and begin debugging. - -The procedure should be the same on other platforms, modulo the choice -of terminal emulator program and the scheme used to access the serial -ports. From problem reports on the cygwin mailing list, it appears that -GDB has some problems communicating over serial lines on that platform. - -NOTE: GDB does not like getting lots of input from the program under test -over the serial line. Actually, it does not care, but it looses -characters. It would appear that flow control is not re-enabled when it -resumes program execution. At times, it looked like the test were -failing, but everything was OK. We modified the MVME167 serial driver to -send test output to another serial port. Using two serial ports is -usually the easiest way to get test output while retaining a reliable debug -connection regardless of the debugger/target combination. - -Information provided by Charles-Antoine Gauthier (charles.gauthier@@iit.nrc.ca) -and Jiri Gaisler (jgais@@ws.estec.esa.nl). - - -@section omniORB - -omniORB is a GPL'ed CORBA which has been ported to RTEMS. It is -available from -(@uref{http://www.uk.research.att.com/omniORB/omniORB.html,http://www.uk.research.att.com/omniORB/omniORB.html}) -. - -For information on the RTEMS port of omniORB to RTEMS, see the following -URL -(@uref{http://www.connecttel.com/corba/rtems_omni.html,http://www.connecttel.com/corba/rtems_omni.html}). - -C++ exceptions must work properly on your target for omniORB to work. - -The port of omniORB to RTEMS was done by Rosimildo DaSilva -. - -@section TCL - -Tool Command Language. - -ditto - -@section ncurses - -Free version of curses. - -ditto - - -@section zlib - -Free compression/decompression library. - -ditto - diff --git a/doc/FAQ/hwdebugaids.t b/doc/FAQ/hwdebugaids.t deleted file mode 100644 index 765ba6d921..0000000000 --- a/doc/FAQ/hwdebugaids.t +++ /dev/null @@ -1,110 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Hardware to Ease Debugging - -The items in this category provide information on various hardware -debugging assistants that are available. - -@section MC683xx BDM Support for GDB - -Eric Norum (eric@@skatter.usask.ca) has a driver for a parallel -port interface to a BDM module. This driver has a long history -and is based on a driver by Gunter Magin (magin@@skil.camelot.de) -which in turn was based on BD32 for DOS by Scott Howard. Eric Norum -and Chris Johns (ccj@@acm.org) have put together a package containing -everything you need to use this BDM driver including software, PCB layouts, -and machining drawings. From the README: - -"This package contains everything you need to be able to run GDB on -Linux and control a Motorola CPU32+ (68360) or Coldfire (5206, 5206e, or -5207) target through a standard PC parallel port." - -Information on this BDM driver is available at the following URL: - -@example -http://www.calm.hw.ac.uk/davidf/coldfire/gdb-bdm-linux.htm -@end example - -The package is officially hosted at Eric Norum's ftp site: - -@example -ftp://skatter.usask.ca/pub/eric/BDM-Linux-gdb/ -@end example - -Peter Shoebridge (peter@@zeecube.com) has ported the Linux -parallel port BDM driver from Eric Norum to Windows NT. It is -available at http://www.zeecube.com/bdm. - -The efi332 project has a home-built BDM module and gdb backend for -Linux. See http://efi332.eng.ohio-state.edu/efi332/hardware.html) -for details. The device driver and gdb backend are based on those -by Gunter Magin (magin@@skil.camelot.de) available from -ftp.lpr.e-technik.tu-muenchen.de. - -Pavel Pisa (pisa@@cmp.felk.cvut.cz) has one available at -http://cmp.felk.cvut.cz/~pisa/m683xx/bdm_driver.html. - -Huntsville Microsystems (HMI) has GDB support for their BDM module -available upon request. It is also available from their ftp site: -ftp://ftp.hmi.com/pub/gdb - -The Macraigor OCD BDM module has a driver for Linux -written by Gunter Magin (magin@@skil.camelot.de). -No URLs yet. - -Finally, there is a overview of BDM at the following URL: -http://cmp.felk.cvut.cz/~pisa/m683xx/bdm_driver.html. - -Information in this section from: - -@itemize @bullet -@item Brendan Simon -@item W Gerald Hicks -@item Chris Johns -@item Eric Norum -@item Gunter Magin - -@end itemize - - -@section MPC8xx BDM Support for GDB - -@c "Adrian Bocaniciu" has a driver -@c for NT and is willing to share it but he needs to be emailed -@c privately since he needs to explain somethings about it. -@c It has been used for over a year as of 08/18/99. - -Christian Haan has written a driver for FreeBSD -based for"a slightly changed ICD BDM module (because of changes -in the BDM interface on the PowerPC)" that "probably will work with -the PD module too." His work is based on the M68K BDM work by -Gunter Magin (Gunter.Magin@@skil.camelot.de) and -the PPC BDM for Linux work by Sergey Drazhnikov (swd@@agua.comptek.ru). -This is not yet publicly available. - -Sergey Drazhnikov (swd@@agua.comptek.ru) has written a PPC BDM driver for -Linux. Information is available at http://cyclone.parad.ru/ppcbdm. - -Huntsville Microsystems (HMI) has GDB support for their BDM module -available upon request. It is also available from their ftp site: -ftp://ftp.hmi.com/pub/gdb - -GDB includes support for a set of primitives to support the Macraigor -Wiggler (OCD BDM). Unfortunately, this requires the use of a -proprietary interface and is supported only on Windows. This forces -one to use CYGWIN. Reports are that this results in a slow -interface. Scott Howard (http://www.objsw.com) has announced -that support for the gdb+wiggler combination under DJGPP which should -run significantly faster. - -@itemize @bullet -@item Leon Pollak -@item Christian Haan -@end itemize - diff --git a/doc/FAQ/projects.t b/doc/FAQ/projects.t deleted file mode 100644 index 5bd7043207..0000000000 --- a/doc/FAQ/projects.t +++ /dev/null @@ -1,113 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter RTEMS Projects - -The questions in this category are regarding things that people -are working on or that the RTEMS community would like to see work on. - -There are multiple ways to support the RTEMS Project. Financial support -is always welcomed. This can be via sponsorship of a specific project -such as one of the ones listed here or via volunteering in some -capacity. - -@section Other Filesystems - -This is a list of the filesystems that would be nice to have support -for in RTEMS. For each filsystem, status and contact information is -provided for those who have expressed interest in helping out or are actively -working on it. - -@itemize @bullet -@item TFTP client - read only, no write capability -@itemize @bullet -@item No Contact -@end itemize - -@item DOS Filesystem - ??? -@itemize @bullet -@item Peter Shoebridge -@item Victor V. Vengerov -@end itemize - -@item CD-ROM Filesystem - ??? -@itemize @bullet -@item Peter Shoebridge -@end itemize - -@item Flash Filesystem(s) - ??? -@itemize @bullet -@item Rod Barman -@item Victor V. Vengerov -@end itemize - -@item Remote Host Filesystem - ??? -@itemize @bullet -@item Wayne Bullaughey -@end itemize - -@item NFS client - ??? -@itemize @bullet -@item No Contact -@end itemize - -@end itemize - -@section Java - -@subsection Kaffe - -This porting effort is underway and active. - -@itemize @bullet -@item Jiri Gaisler -@item Oscar Martinez de la Torre -@end itemize - -NOTE: An older version of Kaffe was ported to a pre-4.0 version of RTEMS. -The network support in RTEMS was immature at that port and Kaffe had -portability problems. Together these resulted in an unclean port which -was never merged. - -@subsection GNU Java Compiler (gjc) - -This porting effort is underway and active. - -@itemize @bullet -@item Charles-Antoine Gauthier -@end itemize - -@section CORBA - -@subsection TAO - -This porting effort is pending testing. Erik ported the code but then -discovered that his target board did not have enough memory to run -any TAO tests. - -@itemize @bullet -@item Erik Ivanenko -@end itemize - -@section APIs - -@subsection POSIX 1003.1b - -Support for POSIX 1003.1b is mature but there are a few remaining -items including a handful of services, performance tests, and -documentation. Please refer to the Status chapter of the -@i{POSIX API User's Guide} for more details. - -@subsection ITRON 3.0 - -Support for ITRON 3.0 is in its beginning stages. There are -numerous managers left to implement, both functional and -performance tests to write, and much documentation remaining. -Please refer to the Status chapter of the @i{ITRON 3.0 API User's Guide} -for specific details. - diff --git a/doc/FAQ/tools.t b/doc/FAQ/tools.t deleted file mode 100644 index 011f4945a6..0000000000 --- a/doc/FAQ/tools.t +++ /dev/null @@ -1,51 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter General Development Tool Hints - -The questions in this category are related to the GNU development tools -in a non-language specific way. - -@section What is GNU? - -Take a look at @uref{http://www.gnu.org} for information on the GNU Project. - -@section How do I generate a patch? - -The RTEMS patches to the development tools are generated using a -command like this - -@example -diff -N -P -r -c TOOL-original-image TOOL-with-changes >PATCHFILE -@end example - -where the options are: - -@itemize @bullet - -@item -N and -P take care of adding and removing files (be careful not to -include junk files like file.mybackup) - -@item -r tells diff to recurse through subdirectories - -@item -c is a context diff (easy to read for humans) - -@end itemize - -Please look at the generated PATCHFILE and make sure it does not -contain anything you did not intend to send to the maintainers. -It is easy to accidentally leave a backup file in the modified -source tree or have a spurious change that should not be -in the PATCHFILE. - -If you end up with the entire contents of a file in the patch -and can't figure out why, you may have different CR/LF scheme -in the two source files. The GNU open-source packages usually have -UNIX style CR/LF. If you edit on a Windows platform, the line -terminators may have been transformed by the editor into Windows -style. diff --git a/doc/HELP.html b/doc/HELP.html deleted file mode 100644 index 851d083d10..0000000000 --- a/doc/HELP.html +++ /dev/null @@ -1,22 +0,0 @@ - -RTEMS 4.0.0 On-Line Library - - - OAR -

    RTEMS On-Line Library

    -
    - -The following supplement manuals do not currently exist: - -
  • RTEMS AMD 29K Applications Supplement
    • -
  • RTEMS MIPS Applications Supplement
    • -
  • RTEMS Hitachi SH Applications Supplement
    • -
  • RTEMS UNIX Port Applications Supplement
    • -     -If you have knowledge of the processors used in the above ports and -want to contribute to RTEMS, please contact -rtems@OARcorp.com - -
    -Copyright © 1988-2000 OAR Corporation - diff --git a/doc/Make.config b/doc/Make.config deleted file mode 100644 index c08a37a09d..0000000000 --- a/doc/Make.config +++ /dev/null @@ -1,64 +0,0 @@ -# -# Build information which may change -# -# $Id$ -# - -RTEMS_VERSION=20000104 -#DOC_INSTALL_BASE=/usr1/rtems/tmp/rtemsdoc-$(RTEMS_VERSION) -DOC_INSTALL_BASE=/home/httpd/html/rtems/rtemsdoc-$(RTEMS_VERSION) -# DOC_INSTALL_BASE=/home/httpd/html/rtems/doc/rtems - -SRCDIR=/usr1/rtems/rtemsdoc-work - -BMENU=$(SRCDIR)/tools/bmenu/bmenu -PDL2TEXI=$(SRCDIR)/tools/pdl2texi/pdl2texi - -SRC2HTML=$(SRCDIR)/tools/src2html/src2html -#TEXI2DVI=$(SRCDIR)/tools/texi2www/texi2dvi -TEXI2DVI=texi2dvi -TEXI2PDF=texi2pdf -TEXI2WWW=$(SRCDIR)/tools/texi2www/texi2www -MAKEINFO=makeinfo -INFO=info -XDVI=xdvi -s 4 -GHOSTVIEW=ghostview -magstep -1 - -# Account for tree organization which restricts visibility -#ifeq ($(DISTRIBUTION_LEVEL),public) -RLEVEL= -WWW_INSTALL=$(DOC_INSTALL_BASE)/html -INFO_INSTALL=$(DOC_INSTALL_BASE)/info -INDEX_FILE=../$(RLEVEL)index.html -#else -#RLEVEL=../ -#WWW_INSTALL=$(DOC_INSTALL_BASE)/html/$(DISTRIBUTION_LEVEL) -#INFO_INSTALL=$(DOC_INSTALL_BASE)/info/$(DISTRIBUTION_LEVEL) -#INDEX_FILE=../$(RLEVEL)rtems_full.html -#endif - -#TEXI2WWW_ARGS=-dirfile $(WWW_INSTALL)/index.html \ -# -header $(WWW_INSTALL)/rtems_header.html \ -# -footer $(WWW_INSTALL)/rtems_footer.html -TEXI2WWW_ARGS=-dirfile $(INDEX_FILE) \ - -header $(WWW_INSTALL)/$(RLEVEL)rtems_header.html \ - -footer $(WWW_INSTALL)/$(RLEVEL)rtems_footer.html \ - -icons $(RLEVEL).. - - -define make-dirs - @ if [ ! -d $(WWW_INSTALL) ] ; then \ - mkdir -p $(WWW_INSTALL); \ - fi - @ if [ ! -d $(INFO_INSTALL) ] ; then \ - mkdir -p $(INFO_INSTALL); \ - fi - @ - cp $(SRCDIR)/oaronly.jpg $(WWW_INSTALL) - @ - sed -e 's/RTEMS_VERSION/$(RTEMS_VERSION)/' \ - <$(SRCDIR)/rtems_footer.html >$(DOC_INSTALL_BASE)/html/rtems_footer.html - @ - cp $(SRCDIR)/HELP.html $(DOC_INSTALL_BASE)/html - @ - cp $(SRCDIR)/common/*.gif $(DOC_INSTALL_BASE)/html - @ - cp $(SRCDIR)/tools/texi2www/*.gif $(DOC_INSTALL_BASE)/html - @ - cp $(SRCDIR)/common/*.jpg $(DOC_INSTALL_BASE)/html -endef - diff --git a/doc/Makefile b/doc/Makefile deleted file mode 100644 index 39ca6a35f4..0000000000 --- a/doc/Makefile +++ /dev/null @@ -1,57 +0,0 @@ -# -# $Id$ -# - -include Make.config - -BASEDIR=$(shell pwd) - -all: env info html ps pdf -# find $(WWW_INSTALL) -type f | xargs -e chmod 444 -# find $(WWW_INSTALL) -type d | xargs -e chmod 555 - -env: tools dirs headers - -dirs: - $(make-dirs) - -headers: - sed -e 's/RTEMS_VERSION/$(RTEMS_VERSION)/' \ - <$(SRCDIR)/index.html >$(WWW_INSTALL)/index.html - sed -e 's/RTEMS_VERSION/$(RTEMS_VERSION)/' \ - <$(SRCDIR)/rtems_support.html >$(WWW_INSTALL)/rtems_support.html - sed -e 's/RTEMS_VERSION/$(RTEMS_VERSION)/' \ - <$(SRCDIR)/rtems_header.html >$(WWW_INSTALL)/rtems_header.html - sed -e 's/RTEMS_VERSION/$(RTEMS_VERSION)/' \ - <$(SRCDIR)/rtems_footer.html >$(WWW_INSTALL)/rtems_footer.html - cp common/*.gif $(WWW_INSTALL) - cp BAD.html $(WWW_INSTALL) - -info: env - ./do_docs $(BASEDIR) info - -html: env - ./do_docs $(BASEDIR) html - -dvi: dirs env - ./do_docs $(BASEDIR) dvi - -ps: dirs env - ./do_docs $(BASEDIR) ps - -pdf: dirs env - ./do_docs $(BASEDIR) pdf - -clean: - ./do_docs $(BASEDIR) clean - cd tools/bmenu ; gmake clean - cd tools/pdl2texi ; gmake clean - cd tools/src2html ; gmake clean - - -.PHONY: tools - -tools: - cd tools/bmenu ; gmake - cd tools/pdl2texi ; gmake - cd tools/src2html ; gmake diff --git a/doc/README b/doc/README deleted file mode 100644 index 225dfa23b8..0000000000 --- a/doc/README +++ /dev/null @@ -1,36 +0,0 @@ -# -# $Id$ -# - -Tools Required -============== -The following tools are used in the production of this documentation: - -TeX -texinfo 3.7 -texi2www-960103 - -This was used by the authors to generate the directory tree figure -in the texinfo printed version: - -tree (from the CTAN Archives -- see http://jasper.ora.com/ctan.html) - -Installation -============ -1. Edit replace-word so it references perl in the correct location. - -2. Edit Make.config and localize it. - -3. Edit do_docs and fix basedir - -4. Create the installation point for the html and info files. - -5. Copy texi2www gif files into the main rtems html install directory. - - -Use do_docs to: - -do_docs info -do_docs html -do_docs clean - diff --git a/doc/TODO b/doc/TODO deleted file mode 100644 index 0aa41ce461..0000000000 --- a/doc/TODO +++ /dev/null @@ -1,77 +0,0 @@ -# -# $Id$ -# - -This is a collection of things which need to be done to the various -manuals. - -POSIX User Notes -================ - -Add pages for network services. - -Add timer() services if we have any. - - -Development Environment Guide -============================= -Either rename to "A Tour of the RTEMS Source Tree" or include -more information on the GNU tools. - -The "C Suites" section is oddly named and the directory -tree included is wrong in that make is no longer under -the c directory. I think the build-tools make have -moved as well. - -All the paths should be provided as relative paths -from the top of the RTEMS source tree. It wastes -valuable screen space to do otherwise. - -The last paragraph of "C Suites" is vague and could -be written better. It should include the subdirectory -names as part of the textual description. - - -Should this documentation even use the phrase "C Implementation" -any longer? - -Directory names should be in @code -- not "quoted". - -In "Support Library Source Directory", look for "which installed" - -In the latter part of the "libbsp" paragraph in "Support -Library Source Directory", there is reference to the -stubdr directory which is no longer there. - -Update this section to include discussion of the shared -subdirectory and its relationship to the BSPs. Write this -in such a way that it can be passed on to Geoffroy Montel. - -Include a better discussion of the subdirectories -under each BSP. This can be a starting point for -Geoffroy Montel. The sample tests also deserve mention -in a BSP development guide. - -In the section, "Test Suite Source Directory", there is a -numeric count of the number of tests in each suite. This -should be eliminated for maintenance purposes. - -The psxtest directory is not mentioned. Check that no others -have been forgotten. - -There should probably be no reference to the Ada sample -applications. This document used to cover both implementations. -This now seems inappropriate. - -The hello world sample test discussion mentions that it provides -a rudiementary test of the BSP startup code and the "RTEMS -C Library". This should be rewritten to tell mroe about what -this test shows (actually a lot). It should mention that this -test tries to avoid using interrupts. - -The ticker test should mention that in contrast to hello, it -does use interrupts. :) It can be used to tune the clock -tick. - -The ticker test documentation says it calls "tm_get" -- jeez -how old is this manual. diff --git a/doc/VERSION b/doc/VERSION deleted file mode 100644 index 824201fb48..0000000000 --- a/doc/VERSION +++ /dev/null @@ -1,5 +0,0 @@ -# -# $Id$ -# - -RTEMS Version 19991117 diff --git a/doc/ada_user/Makefile b/doc/ada_user/Makefile deleted file mode 100644 index fedd0ea011..0000000000 --- a/doc/ada_user/Makefile +++ /dev/null @@ -1,73 +0,0 @@ -# -# COPYRIGHT (c) 1988-1999. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=ada_user - -include ../Make.config - -all: html info ps pdf - -COMMON_FILES=../common/cpright.texi ../user/bsp.texi ../user/clock.texi \ - ../user/concepts.texi ../user/conf.texi ../user/dirstat.texi \ - ../user/dpmem.texi ../user/event.texi \ - ../user/fatal.texi ../user/glossary.texi ../user/init.texi \ - ../user/intr.texi ../user/io.texi ../user/mp.texi ../user/msg.texi \ - ../user/overview.texi ../user/part.texi ../user/preface.texi \ - ../user/region.texi ../user/rtmon.texi ../user/schedule.texi \ - ../user/sem.texi ../user/signal.texi ../user/task.texi \ - ../user/timer.texi ../user/userext.texi -FILES= ada_user.texi example.texi $(COMMON_FILES) - -LINKFILES=../user/rtemspie.eps ../user/rtemspie.pdf \ - ../user/states.eps ../user/states.pdf - -dirs: links - $(make-dirs) - -links: - cp $(LINKFILES) . - -INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*) - -info: dirs $(PROJECT) - cp $(shell ls -1 $(PROJECT) $(PROJECT)-* 2>/dev/null) $(INFO_INSTALL) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: dirs $(PROJECT).dvi -ps: dirs $(PROJECT).ps -pdf: dirs $(PROJECT).pdf - -$(PROJECT).pdf: $(FILES) - $(TEXI2PDF) $(PROJECT).texi - cp $(PROJECT).pdf $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).ps: dirs $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - cp $(PROJECT).dvi $(WWW_INSTALL)/$(PROJECT) - -html: dirs $(FILES) - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - cp ../user/rtemsarc.gif ../user/rtemspie.gif ../user/states.gif \ - $(WWW_INSTALL)/$(PROJECT) - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -# This is one of the few document directories without its own eps and pdf -# files. Thus it can safely remove *.pdf and *.eps. -clean: - rm -f *.o $(PROG) *.txt core *.html *.pdf *.eps - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* _* - rm -f *.cps *.cpss *.fns *.jkys *.pgs *.tps *.vrs - diff --git a/doc/ada_user/ada_user.texi b/doc/ada_user/ada_user.texi deleted file mode 100644 index fd7917f73e..0000000000 --- a/doc/ada_user/ada_user.texi +++ /dev/null @@ -1,169 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c %**start of header -@setfilename ada_user -@syncodeindex vr fn -@synindex ky cp -@paragraphindent 0 -@c @smallbook -@c %**end of header - -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Master file for the Ada User's Guide -@c - -@c Joel's Questions -@c -@c 1. Why does paragraphindent only impact makeinfo? -@c 2. Why does paragraphindent show up in HTML? -@c - -@include ../common/setup.texi - -@ignore -@ifinfo -@format -START-INFO-DIR-ENTRY -* RTEMS Ada User: (ada_user). The Ada User's Guide -END-INFO-DIR-ENTRY -@end format -@end ifinfo -@end ignore - -@c variable substitution info: -@c -@clear is-C -@set is-Ada -@set LANGUAGE Ada -@set STRUCTURE record -@set ROUTINE subprogram -@set OR or -@set RPREFIX RTEMS. -@set DIRPREFIX rtems. -@c the language is @value{LANGUAGE} -@c NOTE: don't use underscore in the name -@c - -@c -@c Title Page Stuff -@c - -@set edition @value{RTEMS-EDITION} -@set version @value{RTEMS-VERSION} -@set update-date @value{RTEMS-UPDATE-DATE} -@set update-month @value{RTEMS-UPDATE-MONTH} - -@c -@c I don't really like having a short title page. --joel -@c -@c @shorttitlepage RTEMS Applications Ada User's Guide - -@setchapternewpage odd -@settitle RTEMS Ada User's Guide -@titlepage -@finalout - -@title RTEMS Applications Ada User's Guide -@subtitle Edition @value{edition}, for RTEMS @value{version} -@sp 1 -@subtitle @value{update-month} -@author On-Line Applications Research Corporation -@page -@include ../common/cpright.texi -@end titlepage - -@c This prevents a black box from being printed on "overflow" lines. -@c The alternative is to rework a sentence to avoid this problem. - -@include ../user/preface.texi -@include ../user/overview.texi -@include ../user/concepts.texi -@include ../user/init.texi -@include ../user/task.texi -@include ../user/intr.texi -@include ../user/clock.texi -@include ../user/timer.texi -@include ../user/sem.texi -@include ../user/msg.texi -@include ../user/event.texi -@include ../user/signal.texi -@include ../user/part.texi -@include ../user/region.texi -@include ../user/dpmem.texi -@include ../user/io.texi -@include ../user/fatal.texi -@include ../user/schedule.texi -@include ../user/rtmon.texi -@include ../user/bsp.texi -@include ../user/userext.texi -@include ../user/conf.texi -@include ../user/mp.texi -@include ../user/dirstat.texi -@include example.texi -@include ../user/glossary.texi -@ifinfo -@node Top, Preface, (dir), (dir) -@top ada_user - -This is the online version of the RTEMS Ada User's Guide. - -@menu -* Preface:: -* Overview:: -* Key Concepts:: -* Initialization Manager:: -* Task Manager:: -* Interrupt Manager:: -* Clock Manager:: -* Timer Manager:: -* Semaphore Manager:: -* Message Manager:: -* Event Manager:: -* Signal Manager:: -* Partition Manager:: -* Region Manager:: -* Dual-Ported Memory Manager:: -* I/O Manager:: -* Fatal Error Manager:: -* Scheduling Concepts:: -* Rate Monotonic Manager:: -* Board Support Packages:: -* User Extensions Manager:: -* Configuring a System:: -* Multiprocessing Manager:: -* Directive Status Codes:: -* Example Application:: -* Glossary:: -* Command and Variable Index:: -* Concept Index:: -@end menu - -@end ifinfo -@c -@c -@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here -@c - -@node Command and Variable Index, Concept Index, Glossary, Top -@unnumbered Command and Variable Index - -@c There are currently no Command and Variable Index entries. - -@printindex fn - -@node Concept Index, , Command and Variable Index, Top -@unnumbered Concept Index - -@c There are currently no Concept Index entries. -@printindex cp - -@contents -@bye - diff --git a/doc/ada_user/example.texi b/doc/ada_user/example.texi deleted file mode 100644 index 8aa9a80899..0000000000 --- a/doc/ada_user/example.texi +++ /dev/null @@ -1,21 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node Example Application, Glossary, Directive Status Codes, Top -@end ifinfo -@chapter Example Application - -@example - -Currently there is no example Ada application provided. - -@end example - - - diff --git a/doc/archgrey.gif b/doc/archgrey.gif deleted file mode 100644 index d315b028f2..0000000000 Binary files a/doc/archgrey.gif and /dev/null differ diff --git a/doc/bsp_howto/Makefile b/doc/bsp_howto/Makefile deleted file mode 100644 index 0e12e674b3..0000000000 --- a/doc/bsp_howto/Makefile +++ /dev/null @@ -1,152 +0,0 @@ -# -# COPYRIGHT (c) 1988-1999. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=bsp_howto - -include ../Make.config - -all: html info ps pdf - -dirs: - $(make-dirs) - -COMMON_FILES=../common/cpright.texi ../common/setup.texi - -GENERATED_FILES= \ - intro.texi target.texi makefiles.texi linkcmds.texi support.texi \ - adaintr.texi init.texi console.texi clock.texi timer.texi rtc.texi \ - nvmem.texi network.texi shmsupp.texi analog.texi discrete.texi - -FILES=$(PROJECT).texi $(GENERATED_FILES) - -INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*) - -info: dirs $(PROJECT) - #cp $(wildcard $(PROJECT) $(PROJECT)-*) $(INFO_INSTALL) - # cp $(PROJECT) $(INFO_INSTALL) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: dirs $(PROJECT).dvi -ps: dirs $(PROJECT).ps -pdf: dirs $(PROJECT).pdf - -$(PROJECT).pdf: $(FILES) - $(TEXI2PDF) $(PROJECT).texi - cp $(PROJECT).pdf $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).ps: $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - cp $(PROJECT).dvi $(WWW_INSTALL)/$(PROJECT) - -html: dirs $(FILES) - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -clean: - rm -f *.o $(PROG) *.txt core $(PROJECT).pdf - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* $(GENERATED_FILES) - rm -f *.fixed _* network.t - -# -# Grab the chapter on writing a network device driver. -# -network.t: - ln -s ../networking/driver.t network.t - - -# -# Process Automatically Generated Files -# - -intro.texi: intro.t Makefile - $(BMENU) -p "Top" \ - -u "Top" \ - -n "Target Dependent Files" ${*}.t - -target.texi: target.t Makefile - $(BMENU) -p "Introduction" \ - -u "Top" \ - -n "Makefiles" ${*}.t - -makefiles.texi: makefiles.t Makefile - $(BMENU) -p "Target Dependent Files Board Support Package Structure" \ - -u "Top" \ - -n "Linker Script" ${*}.t - -linkcmds.texi: linkcmds.t Makefile - $(BMENU) -p "Makefiles Creating a New BSP Make Customization File" \ - -u "Top" \ - -n "Ada95 Interrupt Support" ${*}.t - -adaintr.texi: adaintr.t Makefile - $(BMENU) -p "Linker Script Initialized Data" \ - -u "Top" \ - -n "Miscellaneous Support Files" ${*}.t - -support.texi: support.t Makefile - $(BMENU) -p "Ada95 Interrupt Support Version Requirements" \ - -u "Top" \ - -n "" ${*}.t - -init.texi: init.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -console.texi: console.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -clock.texi: clock.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -timer.texi: timer.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -rtc.texi: rtc.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -nvmem.texi: nvmem.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -network.texi: network.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -shmsupp.texi: shmsupp.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -analog.texi: analog.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -discrete.texi: discrete.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t diff --git a/doc/bsp_howto/adaintr.t b/doc/bsp_howto/adaintr.t deleted file mode 100644 index 7ca60da21e..0000000000 --- a/doc/bsp_howto/adaintr.t +++ /dev/null @@ -1,81 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Ada95 Interrupt Support - -@section Introduction - -This chapter describes what is required to enable Ada interrupt -and error exception handling when using GNAT over RTEMS. - -The GNAT Ada95 interrupt support RTEMS was developed by -Jiri Gaisler who also wrote this -chapter. - -@section Mapping Interrupts to POSIX Signals - -In Ada95, interrupts can be attached with the interrupt_attach pragma. -For most systems, the gnat run-time will use POSIX signal to implement -the interrupt handling, mapping one signal per interrupt. For interrupts -to be propagated to the attached Ada handler, the corresponding signal -must be raised when the interrupt occurs. - -The same mechanism is used to generate Ada error exceptions. -Three error exceptions are defined: program, constraint and storage -error. These are generated by raising the predefined signals: SIGILL, -SIGFPE and SIGSEGV. These signals should be raised when a spurious -or erroneous trap occurs. - -To enable gnat interrupt and error exception support for a particular -bsp, the following has to be done: - -@enumerate - -@item Write an interrupt/trap handler that will raise the corresponding -signal depending on the interrupt/trap number. - -@item Install the interrupt handler for all interrupts/traps that will be -handled by gnat (including spurious). - -@item At startup, gnat calls @code{__gnat_install_handler()}. The bsp -must provide this function which installs the interrupt/trap handlers. - -@end enumerate - -Which cpu-interrupt will generate which signal is implementation -defined. There are 32 POSIX signals (1 - 32), and all except the -three error signals (SIGILL, SIGFPE and SIGSEGV) can be used. I -would suggest to use the upper 16 (17 - 32) which do not -have an assigned POSIX name. - -Note that the pragma interrupt_attach will only bind a signal -to a particular Ada handler - it will not unmask the -interrupt or do any other things to enable it. This have to be -done separately, typically by writing various device register. - -@section Example Ada95 Interrupt Program - -An example program (@code{irq_test}) is included in the -Ada examples package to show how interrupts can be handled -in Ada95. Note that generation of the test interrupt -(@code{irqforce.c}) is bsp specific and must be edited. - -NOTE: The @code{irq_test} example was written for the SPARC/ERC32 -BSP. - -@section Version Requirements - -With RTEMS 4.0, a patch was required to psignal.c in RTEMS -sources (to correct a bug associated to the default action of -signals 15-32). The SPARC/ERC32 RTEMS BSP includes the -@code{gnatsupp} subdirectory that can be used as an example -for other BSPs. - -With GNAT 3.11p, a patch is required for @code{a-init.c} to invoke -the BSP specific routine that installs the exception handlers. - diff --git a/doc/bsp_howto/analog.t b/doc/bsp_howto/analog.t deleted file mode 100644 index 45c3a538da..0000000000 --- a/doc/bsp_howto/analog.t +++ /dev/null @@ -1,167 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Analog Driver - -The Analog driver is responsible for providing an -interface to Digital to Analog Converters (DACs) and -Analog to Digital Converters (ADCs). The capabilities provided -by this class of device driver are: - -@itemize @bullet -@item Initialize an Analog Board -@item Open a Particular Analog -@item Close a Particular Analog -@item Read from a Particular Analog -@item Write to a Particular Analog -@item Reset DACs -@item Reinitialize DACS -@end itemize - -Most analog devices are found on I/O cards that support multiple -DACs or ADCs on a single card. - -There are currently no analog device drivers included in the -RTEMS source tree. The information provided in this chapter -is based on drivers developed by OAR Corporation personnel -for applications using RTEMS. It is hoped that this -driver model information can form the basis for a standard -analog driver model that can be supported in future RTEMS -distribution. - -@section Major and Minor Numbers - -The @b{major} number of a device driver is its index in the -RTEMS Device Address Table. - -A @b{minor} number is associated with each device instance -managed by a particular device driver. An RTEMS minor number -is an @code{unsigned32} entity. Convention calls -dividing the bits in the minor number down into categories -like the following: - -@itemize @bullet - -@item @b{board} - indicates the board a particular device is located on -@item @b{port} - indicates the particular device on a board. - -@end itemize - -From the above, it should be clear that a single device driver -can support multiple copies of the same board in a single system. -The minor number is used to distinguish the devices. - -@section Analog Driver Configuration - -There is not a standard analog driver configuration table but some -fields are common across different drivers. The analog driver -configuration table is typically an array of structures with each -structure containing the information for a particular board. -The following is a list of the type of information normally required -to configure an analog board: - -@table @b -@item board_offset -is the base address of a board. - -@item DAC_initial_values -is an array of the voltages that should be written to each DAC -during initialization. This allows the driver to start the board -in a known state. - -@end table - -@section Initialize an Analog Board - -At system initialization, the analog driver's initialization entry point -will be invoked. As part of initialization, the driver will perform -whatever board initialization is required and then set all -outputs to their configured initial state. - -The analog driver may register a device name for each DAC and ADC in -the system. - -@section Open a Particular Analog - -This is the driver open call. Usually this call does nothing other than -validate the minor number. - -With some drivers, it may be necessary to allocate memory when a particular -device is opened. If that is the case, then this is often the place -to do this operation. - -@section Close a Particular Analog - -This is the driver close call. Usually this call does nothing. - -With some drivers, it may be necessary to allocate memory when a particular -device is opened. If that is the case, then this is the place -where that memory should be deallocated. - -@section Read from a Particular Analog - -This corresponds to the driver read call. After validating the minor -number and arguments, this call reads the indicated device. Most analog -devices store the last value written to a DAC. Since DACs are output -only devices, saving the last written value gives the appearance that -DACs can be read from also. If the device is an ADC, then it is sampled. - -@b{NOTE:} Many boards have multiple analog inputs but only one ADC. On -these boards, it will be necessary to provide some type of mutual exclusion -during reads. On these boards, there is a MUX which must be switched -before sampling the ADC. After the MUX is switched, the driver must -delay some short period of time (usually microseconds) before the -signal is stable and can be sampled. To make matters worse, some ADCs -cannot respond to wide voltage swings in a single sample. On these -ADCs, one must do two samples when the voltage swing is too large. -On a practical basis, this means that the driver usually ends up -double sampling the ADC on these systems. - -The value returned is a single precision floating point number -representing the voltage read. This value is stored in the -@code{argument_block} passed in to the call. By returning the -voltage, the caller is freed from having to know the number of -bits in the analog and board dependent conversion algorithm. - -@section Write to a Particular Analog - -This corresponds to the driver write call. After validating the minor -number and arguments, this call writes the indicated device. If the -specified device is an ADC, then an error is usually returned. - -The value written is a single precision floating point number -representing the voltage to be written to the specified DAC. -This value is stored in the @code{argument_block} passed in to the -call. By passing the voltage to the device driver, the caller is -freed from having to know the number of bits in the analog -and board dependent conversion algorithm. - -@section Reset DACs - -This is one of the IOCTL functions supported by the I/O control -device driver entry point. When this IOCTL function is invoked, -all of the DACs are written to 0.0 volts. - -@section Reinitialize DACS - -This is one of the IOCTL functions supported by the I/O control -device driver entry point. When this IOCTL function is invoked, -all of the DACs are written with the initial value configured -for this device. - -@section Get Last Written Values - -This is one of the IOCTL functions supported by the I/O control -device driver entry point. When this IOCTL function is invoked, -the following information is returned to the caller: - -@itemize @bullet -@item last value written to the specified DAC -@item timestamp of when the last write was performed -@end itemize - diff --git a/doc/bsp_howto/bsp_howto.texi b/doc/bsp_howto/bsp_howto.texi deleted file mode 100644 index 7980143011..0000000000 --- a/doc/bsp_howto/bsp_howto.texi +++ /dev/null @@ -1,130 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c %**start of header -@setfilename bsp_howto -@syncodeindex vr fn -@synindex ky cp -@paragraphindent 0 -@c @smallbook -@c %**end of header - -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Master file for the Getting Started (C) Guide -@c - -@include ../common/setup.texi - -@ignore -@ifinfo -@format -START-INFO-DIR-ENTRY -* BSP and Device Driver Development Guide (bsp_howto): -END-INFO-DIR-ENTRY -@end format -@end ifinfo -@end ignore - -@c -@c Title Page Stuff -@c - -@set edition @value{RTEMS-EDITION} -@set version @value{RTEMS-VERSION} -@set update-date @value{RTEMS-UPDATE-DATE} -@set update-month @value{RTEMS-UPDATE-MONTH} - -@c -@c I don't really like having a short title page. --joel -@c -@c @shorttitlepage BSP and Device Driver Development Guide - -@setchapternewpage odd -@settitle BSP and Device Driver Development Guide -@titlepage -@finalout - -@title BSP and Device Driver Development Guide -@subtitle Edition @value{edition}, for @value{version} -@sp 1 -@subtitle @value{update-month} -@author On-Line Applications Research Corporation -@page -@include ../common/cpright.texi -@end titlepage - -@c This prevents a black box from being printed on "overflow" lines. -@c The alternative is to rework a sentence to avoid this problem. - -@include intro.texi -@include target.texi -@include makefiles.texi -@include linkcmds.texi -@include support.texi -@include adaintr.texi -@include init.texi -@include console.texi -@include clock.texi -@include timer.texi -@include rtc.texi -@include nvmem.texi -@include network.texi -@include shmsupp.texi -@include analog.texi -@include discrete.texi - -@ifinfo -@node Top, Introduction, (dir), (dir) -@top bsp_howto - -This is the online version of the RTEMS BSP and Device Driver Development Guide. - -@menu -* Introduction:: -* Target Dependent Files:: -* Makefiles:: -* Linker Script:: -* Miscellaneous Support Files:: -* Ada95 Interrupt Support:: -* Initialization Code:: -* Console Driver:: -* Clock Driver:: -* Timer Driver:: -* Real-Time Clock Driver:: -* Networking Driver:: -* Non-Volatile Memory Driver:: -* Shared Memory Support Driver:: -* Analog Driver:: -* Discrete Driver:: -* Command and Variable Index:: -* Concept Index:: -@end menu - -@end ifinfo -@c -@c -@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here -@c - -@node Command and Variable Index, Concept Index, , Top -@unnumbered Command and Variable Index - -There are currently no Command and Variable Index entries. - -@c @printindex fn - -@node Concept Index, , Command and Variable Index, Top -@unnumbered Concept Index - -There are currently no Concept Index entries. -@c @printindex cp - -@contents -@bye - diff --git a/doc/bsp_howto/clock.t b/doc/bsp_howto/clock.t deleted file mode 100644 index e4e24cfade..0000000000 --- a/doc/bsp_howto/clock.t +++ /dev/null @@ -1,132 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Clock Driver - -@section Introduction - -The purpose of the clock driver is to provide a steady time -basis to the kernel, so that the RTEMS primitives that need -a clock tick work properly. See the @code{Clock Manager} chapter -of the @b{RTEMS Application C User's Guide} for more details. - -The clock driver is located in the @code{clock} directory of the BSP. - -@section Clock Driver Global Variables - -This section describes the global variables expected to be provided by -this driver. - -@subsection Major and Minor Number - -The major and minor numbers of the clock driver are made available via -the following variables. - -@itemize @bullet -@item rtems_device_major_number rtems_clock_major; -@item rtems_device_minor_number rtems_clock_minor; -@end itemize - -The clock device driver is responsible for declaring and -initializing these variables. These variables are used -by other RTEMS components -- notably the Shared Memory Driver. - -@b{NOTE:} In a future RTEMS version, these variables may be replaced -with the clock device driver registering @b{/dev/clock}. - -@subsection Ticks Counter - -Most of the clock device drivers provide a global variable -that is simply a count of the number of clock driver interrupt service -routines that have occured. This information is valuable when debugging -a system. This variable is declared as follows: - -@example -volatile rtems_unsigned32 Clock_driver_ticks; -@end example - -@section Initialization - -The initialization routine is responsible for -programming the hardware that will periodically -generate an interrupt. A programmable interval timer is commonly -used as the source of the clock tick. - -The device should be programmed such that an interrupt is generated -every @i{m} microseconds, where @i{m} is equal to -@code{BSP_Configuration.microseconds_per_tick}. Sometimes the periodic interval -timer can use a prescaler so you have to look carefully at your user's -manual to determine the correct value. - -You must use the RTEMS primitive @code{rtems_interrupt_catch} to install -your clock interrupt service routine: - -@example -rtems_interrupt_catch (Clock_ISR, CLOCK_VECTOR, &old_handler); -@end example - -Since there is currently not a driver entry point invoked at system -shutdown, many clock device drivers use the @code{atexit} routine -to schedule their @code{Clock_exit} routine to execute when the -system is shutdown. - -By convention, many of the clock drivers do not install the clock -tick if the @code{ticks_per_timeslice} field of the Configuration -Table is 0. - -@section System shutdown - -Many drivers provide the routine @code{Clock_exit} that is scheduled -to be run during system shutdown via the @code{atexit} routine. -The @code{Clock_exit} routine will disable the clock tick source -if it was enabled. This can be used to prevent clock ticks after the -system is shutdown. - -@section Clock Interrupt Subroutine - -It only has to inform the kernel that a ticker has elapsed, so call : - -@example -@group -rtems_isr Clock_isr( rtems_vector_number vector ) -@{ - invoke the rtems_clock_tick() directive to announce the tick - if necessary for this hardware - reload the programmable timer -@} -@end group -@end example - -@section IO Control - -The clock driver must supply a handler for the IO control device driver -entry point. This functionality is used by other components -- notably -the Shared Memory Driver to install a wrapper for the clock interrupt -service routine. The following shows the functionality required: - -@example -@group -rtems_device_driver Clock_control( - rtems_device_major_number major, - rtems_device_minor_number minor, - void *pargp -) -@{ - error check the argument pointer parameter - - if the command is "ISR" - invoke the clock interrupt service routine - else if the command is "NEW" - install the requested handler -@} -@end group -@end example - - - - diff --git a/doc/bsp_howto/console.t b/doc/bsp_howto/console.t deleted file mode 100644 index 2ffef13686..0000000000 --- a/doc/bsp_howto/console.t +++ /dev/null @@ -1,377 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Console Driver - -@section Introduction - -This chapter describes the operation of a console driver using -the RTEMS POSIX Termios support. Traditionally RTEMS has referred -to all serial device drivers as console device drivers. A -console driver can be used to do raw data processing in addition -to the "normal" standard input and output device functions required -of a console. - -The serial driver may be called as the consequence of a C Library -call such as @code{printf} or @code{scanf} or directly via the -@code{read} or @code{write} system calls. -There are two main functioning modes: - -@itemize @bullet - -@item console: formatted input/output, with special characters (end of -line, tabulations, etc.) recognition and processing, - -@item raw: permits raw data processing. - -@end itemize - -One may think that two serial drivers are needed to handle these two types -of data, but Termios permits having only one driver. - -@section Termios - -Termios is a standard for terminal management, included in the POSIX 1003.1b -standard. It is commonly provided on UNIX implementations. -Having RTEMS support for Termios is beneficial: - -@itemize @bullet - -@item from the user's side because it provides standard primitive operations -to access the terminal and change configuration settings. These operations -are the same under Unix and Rtems. - -@item from the BSP developer's side because it frees the -developer from dealing with buffer states and mutual exclusions on them. -Early RTEMS console device drivers also did their own special -character processing. - -@end itemize - -Termios support includes: - -@itemize @bullet - -@item raw and console handling, - -@item blocking or non-blocking characters receive, with or without -Timeout. - -@end itemize - -At this time, RTEMS documentation does not include a thorough discussion -of the Termios functionality. For more information on Termios, -type @code{man termios} on a Unix box or point a web browser -at -@uref{http://www.freebsd.org/cgi/man.cgi}. - -@section Driver Functioning Modes - -There are generally two main functioning modes for an UART (Universal -Asynchronous Receiver-Transmitter, i.e. the serial chip): - -@itemize @bullet - -@item polled mode -@item interrupt driven mode - -@end itemize - -In polled mode, the processor blocks on sending/receiving characters. -This mode is not the most efficient way to utilize the UART. But -polled mode is usually necessary when one wants to print an -error message in the event of a fatal error such as a fatal error -in the BSP. This is also the simplest mode to -program. Polled mode is generally preferred if the serial port is -to be used primarily as a debug console. In a simple polled driver, -the software will continuously check the status of the UART when -it is reading or writing to the UART. Termios improves on this -by delaying the caller for 1 clock tick between successive checks -of the UART on a read operation. - -In interrupt driven mode, the processor does not block on sending/receiving -characters. Data is buffered between the interrupt service routine -and application code. Two buffers are used to insulate the application -from the relative slowness of the serial device. One of the buffers is -used for incoming characters, while the other is used for outgoing characters. - -An interrupt is raised when a character is received by the UART. -The interrupt subroutine places the incoming character at the end -of the input buffer. When an application asks for input, -the characters at the front of the buffer are returned. - -When the application prints to the serial device, the outgoing characters -are placed at the end of the output buffer. The driver will place -one or more characters in the UART (the exact number depends on the UART) -An interrupt will be raised when all the characters have been transmitted. -The interrupt service routine has to send the characters -remaining in the output buffer the same way. When the transmitting side -of the UART is idle, it is typically necessary to prime the transmitter -before the first interrupt will occur. - -@section Serial Driver Functioning Overview - -The following Figure shows how a Termios driven serial driver works: - -@example -Figure not included in this draft -@end example - -The following list describes the basic flow. - -@itemize @bullet - -@item the application programmer uses standard C library call (printf, -scanf, read, write, etc.), - -@item C library (in fact that's Cygnus Newlib) calls RTEMS -system call interface. This code can be found in the -@code{c/src/lib/libc} directory. - -@item Glue code calls the serial driver entry routines. - -@end itemize - -@subsection Termios and Polled I/O - -The following functions are provided by the driver and invoked by -Termios for simple character input/output. The specific names of -these routines are not important as Termios invokes them indirectly -via function pointers. - -@subsubsection pollWrite - -The @code{pollWrite} routine is responsible for writing @code{len} characters -from @code{buf} to the serial device specified by @code{minor}. - -@example -@group -int pollWrite (int minor, const char *buf, int len) -@{ - for (i=0; i}. -In simple applications such as the tests provided with RTEMS, it is -commonly found in the main module of the application. For more complex -applications, it may be in a file by itself. - -The header file @code{} defines a constant table named -@code{Configuration}. It is common practice for the BSP to copy -this table into a modifiable copy named @code{BSP_Configuration}. -This copy of the table is modified to define the base address of the -RTEMS Executive Workspace as well as to reflect any BSP and -device driver requirements not automatically handled by the application. - -For more information on the RTEMS Configuration Table, refer to the -@b{RTEMS Application C User's Guide}. - diff --git a/doc/bsp_howto/intro.t b/doc/bsp_howto/intro.t deleted file mode 100644 index ddfd1ea956..0000000000 --- a/doc/bsp_howto/intro.t +++ /dev/null @@ -1,57 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Introduction - -Before reading this documentation, it is strongly advised to read the -RTEMS Development Environment Guide to get acquainted with the RTEMS -directory structure. This document describes how to do a RTEMS Board -Support Package, i.e. how to port RTEMS on a new target board. Discussions -are provided for the following topics: - -@itemize @bullet - -@item RTEMS Board Support Package Organization - -@item Makefiles and the Linker Command Script - -@item Board Initialization Sequence - -@item Device Drivers Including: - -@itemize @bullet - -@item Console Driver - -@item Clock Driver - -@item Timer Driver - -@item Real-Time Clock Driver - -@item Non-Volatile Memory Driver - -@item Networking Driver - -@item Shared Memory Support Driver - -@item Analog Driver - -@item Discrete Driver - -@end itemize - -@end itemize - -The original version of this manual was written by Geoffroy Montel -. When he started development of the gen68340 -BSP, this manual did not exist. He wrote the initial version of -this manual as the result of his experiences. At that time, this -document was viewed internally as the most important "missing manual" -in the RTEMS documentation set. - diff --git a/doc/bsp_howto/linkcmds.t b/doc/bsp_howto/linkcmds.t deleted file mode 100644 index 828ff23099..0000000000 --- a/doc/bsp_howto/linkcmds.t +++ /dev/null @@ -1,425 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Linker Script - -@section What is a "linkcmds" file? - -The @code{linkcmds} file is a script which is passed to the linker at linking -time. This file describes the memory configuration of the board as needed -to link the program. Specifically it specifies where the code and data -for the application will reside in memory. - -@section Program Sections - -An embedded systems programmer must be much more aware of the -placement of their executable image in memory than the average -applications programmer. A program destined to be embedded as well -as the target system have some specific properties that must be -taken into account. Embedded machines often mean average performances -and small memory usage. It is the memory usage that concerns us -when examining the linker command file. - -Two types of memories have to be distinguished: - -@itemize @bullet -@item RAM - volatile offering read and write access -@item ROM - non-volatile but read only -@end itemize - -Even though RAM and ROM can be found in every personal computer, -one generally doesn't care about them. In a personal computer, -a program is nearly always stored on disk and executed in RAM. Things -are a bit different for embedded targets: the target will execute the -program each time it is rebooted or switched on. The application -program is stored in non-volatile memory such as ROM, PROM, EEPROM, -or Flash. On the other hand, data processing occurs in RAM. - -This leads us to the structure of an embedded program. In rough terms, -an embedded program is made of sections. It is the responsibility of -the application programmer to place these sections in the appropriate -place in target memory. To make this clearer, if using the COFF -object file format on the Motorola m68k family of microprocessors, -the following sections will be present: - -@itemize @bullet - -@item @b{code (@code{.text}) section}: -is the program's code and it should not be modified. -This section may be placed in ROM. - -@item @b{non-initialized data (@code{.bss}) section}: -holds uninitialized variables of the program. It can stay in RAM. - -@item @b{initialized data (@code{.data}) section}: -holds the initialized program data which may be modified during the -program's life. This means they have to be in RAM. -On the other hand, these variables must be set to predefined values, and -those predefined values have to be stored in ROM. - -@end itemize - -@b{NOTE:} Many programs and support libraries unknowingly assume that the -@code{.bss} section and, possibly, the application heap are initialized -to zero at program start. This is not required by the ISO/ANSI C Standard -but is such a common requirement that most BSPs do this. - -That brings us up to the notion of the image of an executable: it consists -of the set of the sections that together constitute the application. - -@section Image of an Executable - -As a program executable has many sections (note that the user can define -their own, and that compilers define theirs without any notice), one has to -specify the placement of each section as well as the type of memory -(RAM or ROM) the sections will be placed into. -For instance, a program compiled for a Personal Computer will see all the -sections to go to RAM, while a program destined to be embedded will see -some of his sections going into the ROM. - -The connection between a section and where that section is loaded into -memory is made at link time. One has to let the linker know where -the different sections are to be placed once they are in memory. - -The following example shows a simple layout of program sections. With -some object formats, there are many more sections but the basic -layout is conceptually similar. - -@example -@group - +-----------------+ - | .text | RAM or ROM - +-----------------+ - | .data | RAM - +-----------------+ - | .bss | RAM - +-----------------+ -@end group -@end example - -@section Example Linker Command Script - -The GNU linker has a command language to specify the image format. This -command language can be quite complicated but most of what is required -can be learned by careful examination of a well-documented example. -The following is a heavily commented version of the linker script -used with the the @code{gen68340} BSP This file can be found at -$BSP340_ROOT/startup/linkcmds. - -@example -/* - * Specify that the output is to be coff-m68k regardless of what the - * native object format is. - */ - -OUTPUT_FORMAT(coff-m68k) - -/* - * Set the amount of RAM on the target board. - * - * NOTE: The default may be overridden by passing an argument to ld. - */ - -RamSize = DEFINED(RamSize) ? RamSize : 4M; - -/* - * Set the amount of RAM to be used for the application heap. Objects - * allocated using malloc() come from this area. Having a tight heap - * size is somewhat difficult and multiple attempts to squeeze it may - * be needed reducing memory usage is important. If all objects are - * allocated from the heap at system initialization time, this eases - * the sizing of the application heap. - * - * NOTE 1: The default may be overridden by passing an argument to ld. - * - * NOTE 2: The TCP/IP stack requires additional memory in the Heap. - * - * NOTE 3: The GNAT/RTEMS run-time requires additional memory in - * the Heap. - */ - -HeapSize = DEFINED(HeapSize) ? HeapSize : 0x10000; - -/* - * Set the size of the starting stack used during BSP initialization - * until first task switch. After that point, task stacks allocated - * by RTEMS are used. - * - * NOTE: The default may be overridden by passing an argument to ld. - */ - -StackSize = DEFINED(StackSize) ? StackSize : 0x1000; - -/* - * Starting addresses and length of RAM and ROM. - * - * The addresses must be valid addresses on the board. The - * Chip Selects should be initialized such that the code addresses - * are valid. - */ - -MEMORY @{ - ram : ORIGIN = 0x10000000, LENGTH = 4M - rom : ORIGIN = 0x01000000, LENGTH = 4M -@} - -/* - * This is for the network driver. See the Networking documentation - * for more details. - */ - -ETHERNET_ADDRESS = - DEFINED(ETHERNET_ADDRESS) ? ETHERNET_ADDRESS : 0xDEAD12; - -/* - * The following defines the order in which the sections should go. - * It also defines a number of variables which can be used by the - * application program. - * - * NOTE: Each variable appears with 1 or 2 leading underscores to - * ensure that the variable is accessible from C code with a - * single underscore. Some object formats automatically add - * a leading underscore to all C global symbols. - */ - -SECTIONS @{ - - /* - * Make the RomBase variable available to the application. - */ - - _RamSize = RamSize; - __RamSize = RamSize; - - /* - * Boot PROM - Set the RomBase variable to the start of the ROM. - */ - - rom : @{ - _RomBase = .; - __RomBase = .; - @} >rom - - /* - * Dynamic RAM - set the RamBase variable to the start of the RAM. - */ - - ram : @{ - _RamBase = .; - __RamBase = .; - @} >ram - - /* - * Text (code) goes into ROM - */ - - .text : @{ - /* - * Create a symbol for each object (.o). - */ - - CREATE_OBJECT_SYMBOLS - - /* - * Put all the object files code sections here. - */ - - *(.text) - - . = ALIGN (16); /* go to a 16-byte boundary */ - - /* - * C++ constructors and destructors - * - * NOTE: See the CROSSGCC mailing-list FAQ for - * more details about the "[......]". - */ - - __CTOR_LIST__ = .; - [......] - __DTOR_END__ = .; - - /* - * Declares where the .text section ends. - */ - - etext = .; - _etext = .; - @} >rom - - /* - * Exception Handler Frame section - */ - - .eh_fram : @{ - . = ALIGN (16); - *(.eh_fram) - @} >ram - - /* - * GCC Exception section - */ - - .gcc_exc : @{ - . = ALIGN (16); - *(.gcc_exc) - @} >ram - - /* - * Special variable to let application get to the dual-ported - * memory. - */ - - dpram : @{ - m340 = .; - _m340 = .; - . += (8 * 1024); - @} >ram - - /* - * Initialized Data section goes in RAM - */ - - .data : @{ - copy_start = .; - *(.data) - - . = ALIGN (16); - _edata = .; - copy_end = .; - @} >ram - - /* - * Uninitialized Data section goes in ROM - */ - - .bss : @{ - /* - * M68K specific: Reserve some room for the Vector Table - * (256 vectors of 4 bytes). - */ - - M68Kvec = .; - _M68Kvec = .; - . += (256 * 4); - - /* - * Start of memory to zero out at initialization time. - */ - - clear_start = .; - - /* - * Put all the object files uninitialized data sections - * here. - */ - - *(.bss) - - *(COMMON) - - . = ALIGN (16); - _end = .; - - /* - * Start of the Application Heap - */ - - _HeapStart = .; - __HeapStart = .; - . += HeapSize; - - /* - * The Starting Stack goes after the Application Heap. - * M68K stack grows down so start at high address. - */ - - . += StackSize; - . = ALIGN (16); - stack_init = .; - - clear_end = .; - - /* - * The RTEMS Executive Workspace goes here. RTEMS - * allocates tasks, stacks, semaphores, etc. from this - * memory. - */ - - _WorkspaceBase = .; - __WorkspaceBase = .; - @} >ram -@} -@end example - -@section Initialized Data - -Now there's a problem with the initialized data: the @code{.data} section -has to be in RAM as this data may be modified during the program execution. -But how will the values be initialized at boot time? - -One approach is to place the entire program image in RAM and reload -the image in its entirety each time the program is run. This is fine -for use in a debug environment where a high-speed connection is available -between the development host computer and the target. But even in this -environment, it is cumbersome. - -The solution is to place a copy of the initialized data in a separate -area of memory and copy it into the proper location each time the -program is started. It is common practice to place a copy of the initialized -@code{.data} section at the end of the code (@code{.text}) section -in ROM when building a PROM image. The GNU tool @code{objcopy} -can be used for this purpose. - -The following figure illustrates the steps a linked program goes through -to become a downloadable image. - -@example -@group -+--------------+ +--------------------+ -| .data RAM | | .data RAM | -+--------------+ +--------------------+ -| .bss RAM | | .bss RAM | -+--------------+ +--------------------+ +----------------+ -| .text ROM | | .text ROM | | .text | -+--------------+ +--------------------+ +----------------+ - | copy of .data ROM | | copy of .data | - +--------------------+ +----------------+ - - Step 1 Step 2 Step 3 -@end group -@end example - -In Step 1, the program is linked together using the BSP linker script. - -In Step 2, a copy is made of the @code{.data} section and placed -after the @code{.text} section so it can be placed in PROM. This step -is done after the linking time. There is an example -of doing this in the file $RTEMS_ROOT/make/custom/gen68340.cfg: - -@example -# make a PROM image using objcopy -m68k-rtems-objcopy \ ---adjust-section-vma .data= \ - -`m68k-rtems-objdump --section-headers \ -$(basename $@@).exe \ -| awk '[...]` \ -$(basename $@@).exe -@end example - -NOTE: The address of the "copy of @code{.data} section" is -created by extracting the last address in the @code{.text} -section with an @code{awk} script. The details of how -this is done are not relevant. - -Step 3 shows the final executable image as it logically appears in -the target's non-volatile program memory. The board initialization -code will copy the ""copy of @code{.data} section" (which are stored in -ROM) to their reserved location in RAM. - diff --git a/doc/bsp_howto/makefiles.t b/doc/bsp_howto/makefiles.t deleted file mode 100644 index 7019dc01a2..0000000000 --- a/doc/bsp_howto/makefiles.t +++ /dev/null @@ -1,235 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Makefiles - -This chapter discusses the Makefiles associated with a BSP. It does not -describe the process of configuring, building, and installing RTEMS. -This chapter will not provide detailed information about this process. -Nonetheless, it is important to remember that the general process consists -of three parts: - -@itemize @bullet -@item configure -@item build -@item install -@end itemize - -During the configure phase, a number of files are generated. These -generated files are tailored for the specific host/target combination -by the configure script. This set of files includes the Makefiles used -to actually compile and install RTEMS. - -During the build phase, the source files are compiled into object files -and libraries are built. - -During the install phase, the libraries, header files, and other support -files are copied to the BSP specific installation point. After installation -is successfully completed, the files generated by the configure and build -phases may be removed. - -@section Makefiles Used During The BSP Building Process - -There is a file named @code{Makefile.in} in each directory of a BSP. -RTEMS uses the @b{GNU autoconf} automatic configuration package. -This tool specializes the @code{Makefile.in} files at the time that RTEMS -is configured for a specific development host and target. Makefiles -are automatically generated from the @code{Makefile.in} files. It is -necessary for the BSP developer to provide these files. Most of the -time, it is possible to copy the @code{Makefile.in} from another -similar directory and edit it. - -The @code{Makefile} files generated are processed when building -RTEMS for a given BSP. - -The BSP developer is responsible for generating @code{Makefile.in} -files which properly build all the files associated with their BSP. -There are generally three types of Makefiles in a BSP source tree: - - -@itemize @bullet -@item Directory Makefiles -@item Source Directory Makefiles -@item Wrapup Makefile -@end itemize - -@subsection Directory Makefiles - -The Directory class of Makefiles directs the build process through -a set of subdirectories in a particular order. This order is usually -chosen to insure that build dependencies are properly processed. -Most BSPs only have one Directory class Makefile. The @code{Makefile.in} -in the BSP root directory (@code{c/src/lib/libbsp/CPU/BSP}) specifies -which directories are to be built for this BSP. For example, the -following Makefile fragment shows how a BSP would only build the -networking device driver if HAS_NETWORKING was defined: - -@example -NETWORKING_DRIVER_yes_V = network -NETWORKING_DRIVER = $(NETWORKING_DRIVER_$(HAS_NETWORKING)_V) - -[...] - -SUB_DIRS=include start340 startup clock console timer \ - $(NETWORKING_DRIVER) wrapup -@end example - -This fragment states that all the directories have to be processed, -except for the @code{network} directory which is included only if the -user configured networking. - -@subsection Source Directory Makefiles - -There is a @code{Makefile.in} in most of the directories in a BSP. This -class of Makefile lists the files to be built as part of the driver. -When adding new files to an existing directory, Do not forget to add -the new files to the list of files to be built in the @code{Makefile.in}. - -@b{NOTE:} The @code{Makefile.in} files are ONLY processed during the configure -process of a RTEMS build. Therefore, when developing -a BSP and adding a new file to a @code{Makefile.in}, the -already generated @code{Makefile} will not include the new references. -This results in the new file not being be taken into account! -The @code{configure} script must be run again or the @code{Makefile} -(the result of the configure process) modified by hand. This file will -be in a directory such as the following: - -@example -MY_BUILD_DIR/c/src/lib/libbsp/CPU/BSP/DRIVER -@end example - -@subsection Wrapup Makefile - -This class of Makefiles produces a library. The BSP wrapup Makefile -is responsible for producing the library @code{libbsp.a} which is later -merged into the @code{librtemsall.a} library. This Makefile specifies -which BSP components are to be placed into the library as well as which -components from the CPU dependent support code library. For example, -this component may choose to use a default exception handler from the -CPU dependent support code or provide its own. - -This Makefile makes use of the @code{foreach} construct in @b{GNU make} -to pick up the required components: - -@example -BSP_PIECES=startup clock console timer -CPU_PIECES= -GENERIC_PIECES= - -# bummer; have to use $foreach since % pattern subst -# rules only replace 1x -OBJS=$(foreach piece, $(BSP_PIECES), ../$(piece)/$(ARCH)/$(piece).o) \ - $(foreach piece, $(CPU_PIECES), \ - ../../../../libcpu/$(RTEMS_CPU)/$(piece)/$(ARCH)/$(piece).o) \ - $(wildcard \ - ../../../../libcpu/$(RTEMS_CPU)/$(RTEMS_CPU_MODEL)/fpsp/$(ARCH)/fpsp.rel) \ - $(foreach piece, \ - $(GENERIC_PIECES), ../../../$(piece)/$(ARCH)/$(piece).o) -@end example - -The variable @code{OBJS} is the list of "pieces" expanded to include -path information to the appropriate object files. The @code{wildcard} -function is used on pieces of @code{libbsp.a} which are optional and -may not be present based upon the configuration options. - -@section Makefiles Used Both During The BSP Design and its Use - -When building a BSP or an application using that BSP, it is necessary -to tailor the compilation arguments to account for compiler flags, use -custom linker scripts, include the RTEMS libraries, etc.. The BSP -must be built using this information. Later, once the BSP is installed -with the toolset, this same information must be used when building the -application. So a BSP must include a build configuration file. The -configuration file is @code{make/custom/BSP.cfg}. - -The configuration file is taken into account when building one's -application using the RTEMS template Makefiles (@code{make/templates}). -It is strongly advised to use these template Makefiles since they -encapsulate a number of build rules along with the compile and link -time options necessary to execute on the target board. - -There is a template Makefile provided for each of class of RTEMS -Makefiles. The purpose of each class of RTEMS Makefile is to: - -@itemize @bullet -@item call recursively the makefiles in the directories beneath -the current one, - -@item build a library, or - -@item build an executable. - -@end itemize - -The following is a shortened and heavily commented version of the -make customization file for the gen68340 BSP. The original source -for this file can be found in the @code{make/custom} directory. - -@example - -# The RTEMS CPU Family and Model -RTEMS_CPU=m68k -RTEMS_CPU_MODEL=mcpu32 - -include $(RTEMS_ROOT)/make/custom/default.cfg - -# The name of the BSP directory used for the actual source code. -# This allows for build variants of the same BSP source. -RTEMS_BSP_FAMILY=gen68340 - -# CPU flag to pass to GCC -CPU_CFLAGS = -mcpu32 - -# optimization flag to pass to GCC -CFLAGS_OPTIMIZE_V=-O4 -fomit-frame-pointer - -# The name of the start file to be linked with. This file is the first -# part of the BSP which executes. -START_BASE=start340 - -[...] - -# This make-exe macro is used in template makefiles to build the -# final executable. Any other commands to follow, just as using -# objcopy to build a PROM image or converting the executable to binary. - -ifeq ($(RTEMS_USE_GCC272),yes) -# This has rules to link an application if an older version of GCC is -# to be used with this BSP. It is not required for a BSP to support -# older versions of GCC. This option is supported in some of the -# BSPs which already had this support. -[...] -else -# This has rules to link an application using gcc 2.8 or newer or any -# egcs version. All BSPs should support this. This version is required -# to support GNAT/RTEMS. -define make-exe - $(CC) $(CFLAGS) $(CFLAGS_LD) -o $(basename $@@).exe $(LINK_OBJS) - $(NM) -g -n $(basename $@@).exe > $(basename $@@).num - $(SIZE) $(basename $@@).exe -endif -@end example - -@subsection Creating a New BSP Make Customization File - -The basic steps for creating a @code{make/custom} file for a new BSP -are as follows: - -@itemize @bullet - -@item copy any @code{.cfg} file to @code{BSP.cfg} - -@item modify RTEMS_CPU, RTEMS_CPU_MODEL, RTEMS_BSP_FAMILY, -RTEMS_BSP, CPU_CFLAGS, START_BASE, and make-exe rules. - -@end itemize - -It is generally easier to copy a @code{make/custom} file from a -BSP similar to the one being developed. - - diff --git a/doc/bsp_howto/nvmem.t b/doc/bsp_howto/nvmem.t deleted file mode 100644 index 97643fff4f..0000000000 --- a/doc/bsp_howto/nvmem.t +++ /dev/null @@ -1,235 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Non-Volatile Memory Driver - -The Non-Volatile driver is responsible for providing an -interface to various types of non-volatile memory. These -types of memory include, but are not limited to, Flash, EEPROM, -and battery backed RAM. The capabilities provided -by this class of device driver are: - -@itemize @bullet -@item Initialize the Non-Volatile Memory Driver -@item Optional Disable Read and Write Handlers -@item Open a Particular Memory Partition -@item Close a Particular Memory Partition -@item Read from a Particular Memory Partition -@item Write to a Particular Memory Partition -@item Erase the Non-Volatile Memory Area -@end itemize - -There is currently only one non-volatile device driver included in the -RTEMS source tree and it does not adhere to this device driver model. -The information provided in this chapter is based on drivers developed -by OAR Corporation personnel for applications using RTEMS. It is -hoped that this driver model information can form the basis for a standard -non-volatile memory driver model that can be supported in future RTEMS -distribution. - -@section Major and Minor Numbers - -The @b{major} number of a device driver is its index in the -RTEMS Device Address Table. - -A @b{minor} number is associated with each device instance -managed by a particular device driver. An RTEMS minor number -is an @code{unsigned32} entity. Convention calls -dividing the bits in the minor number down into categories -that specify an area of non-volatile memory and a partition -with that area. This results in categories -like the following: - -@itemize @bullet - -@item @b{area} - indicates a block of non-volatile memory -@item @b{partition} - indicates a particular address range with an area - -@end itemize - -From the above, it should be clear that a single device driver -can support multiple types of non-volatile memory in a single system. -The minor number is used to distinguish the types of memory and -blocks of memory used for different purposes. - -@section Non-Volatile Memory Driver Configuration - -There is not a standard non-volatile driver configuration table but some -fields are common across different drivers. The non-volatile memory driver -configuration table is typically an array of structures with each -structure containing the information for a particular area of -non-volatile memory. -The following is a list of the type of information normally required -to configure each area of non-volatile memory. - -@table @b -@item memory_type -is the type of memory device in this area. Choices are battery backed RAM, -EEPROM, Flash, or an optional user-supplied type. If the user-supplied type -is configured, then the user is responsible for providing a set of -routines to program the memory. - -@item memory -is the base address of this memory area. - -@item attributes -is a pointer to a memory type specific attribute block. Some of -the fields commonly contained in this memory type specific attribute -structure area: - -@table @b -@item use_protection_algorithm -is set to TRUE to indicate that the protection (i.e. locking) algorithm -should be used for this area of non-volatile memory. A particular -type of non-volatile memory may not have a protection algorithm. - -@item access -is an enumerated type to indicate the organization of the memory -devices in this memory area. The following is a list of the -access types supported by the current driver implementation: - -@itemize @bullet -@item simple unsigned8 -@item simple unsigned16 -@item simple unsigned32 -@item simple unsigned64 -@item single unsigned8 at offset 0 in an unsigned16 -@item single unsigned8 at offset 1 in an unsigned16 -@item single unsigned8 at offset 0 in an unsigned32 -@item single unsigned8 at offset 1 in an unsigned32 -@item single unsigned8 at offset 2 in an unsigned32 -@item single unsigned8 at offset 3 in an unsigned32 -@end itemize - -@item depth -is the depth of the progamming FIFO on this particular chip. Some -chips, particularly EEPROMs, have the same programming algorithm but -vary in the depth of the amount of data that can be programmed in a single -block. - -@end table - -@item number_of_partitions -is the number of logical partitions within this area. - -@item Partitions -is the address of the table that contains an entry to describe each -partition in this area. Fields within each element of this -table are defined as follows: - -@table @b - -@item offset -is the offset of this partition from the base address of this area. - -@item length -is the length of this partition. - -@end table -@end table - -By dividing an area of memory into multiple partitions, it is possible -to easily divide the non-volatile memory for different purposes. - -@section Initialize the Non-Volatile Memory Driver - -At system initialization, the non-volatile memory driver's -initialization entry point will be invoked. As part of -initialization, the driver will perform -whatever initializatin is required on each non-volatile memory area. - -The discrete I/O driver may register device names for memory -partitions of particular interest to the system. Normally this -will be restricted to the device "/dev/nv_memory" to indicate -the entire device driver. - -@section Disable Read and Write Handlers - -Depending on the target's non-volatile memory configuration, it may be -possible to write to a status register and make the memory area completely -inaccessible. This is target dependent and beyond the standard capabilities -of any memory type. The user has the optional capability to provide -handlers to disable and enable access to a partiticular memory area. - -@section Open a Particular Memory Partition - -This is the driver open call. Usually this call does nothing other than -validate the minor number. - -With some drivers, it may be necessary to allocate memory when a particular -device is opened. If that is the case, then this is often the place -to do this operation. - -@section Close a Particular Memory Partition - -This is the driver close call. Usually this call does nothing. - -With some drivers, it may be necessary to allocate memory when a particular -device is opened. If that is the case, then this is the place -where that memory should be deallocated. - -@section Read from a Particular Memory Partition - -This corresponds to the driver read call. After validating the minor -number and arguments, this call enables reads from the specified -memory area by invoking the user supplied "enable reads handler" -and then reads the indicated memory area. When -invoked the @code{argument_block} is actually a pointer to the following -structure type: - -@example -@group -typedef struct @{ - rtems_unsigned32 offset; - void *buffer; - rtems_unsigned32 length; - rtems_unsigned32 status; -@} Non_volatile_memory_Driver_arguments; -@end group -@end example - -The driver reads @code{length} bytes starting at @code{offset} into -the partition and places them at @code{buffer}. The result is returned -in @code{status}. - -After the read operation is complete, the user supplied "disable reads handler" -is invoked to protect the memory area again. - -@section Write to a Particular Memory Partition - -This corresponds to the driver write call. After validating the minor -number and arguments, this call enables writes to the specified -memory area by invoking the "enable writes handler", then unprotecting -the memory area, and finally actually writing to the indicated memory -area. When invoked the @code{argument_block} is actually a pointer to -the following structure type: - -@example -@group -typedef struct @{ - rtems_unsigned32 offset; - void *buffer; - rtems_unsigned32 length; - rtems_unsigned32 status; -@} Non_volatile_memory_Driver_arguments; -@end group -@end example - -The driver writes @code{length} bytes from @code{buffer} and -writes them to the non-volatile memory starting at @code{offset} into -the partition. The result is returned in @code{status}. - -After the write operation is complete, the "disable writes handler" -is invoked to protect the memory area again. - -@section Erase the Non-Volatile Memory Area - -This is one of the IOCTL functions supported by the I/O control -device driver entry point. When this IOCTL function is invoked, -the specified area of non-volatile memory is erased. - diff --git a/doc/bsp_howto/rtc.t b/doc/bsp_howto/rtc.t deleted file mode 100644 index 2c13a18e03..0000000000 --- a/doc/bsp_howto/rtc.t +++ /dev/null @@ -1,188 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Real-Time Clock Driver - -@section Introduction - -The Real-Time Clock (@b{RTC}) driver is responsible for providing an -interface to an @b{RTC} device. [NOTE: In this chapter, the abbreviation -@b{TOD} is used for @b{Time of Day}.] The capabilities provided by this -driver are: - -@itemize @bullet -@item Set the RTC TOD to RTEMS TOD -@item Set the RTEMS TOD to the RTC TOD -@item Get the RTC TOD -@item Set the RTC TOD to the Specified TOD -@item Get the Difference Between the RTEMS and RTC TOD -@end itemize - -The reference implementation for a real-time clock driver can -be found in @code{c/src/lib/libbsp/shared/tod.c}. This driver -is based on the libchip concept and can be easily configured -to work with any of the RTC chips supported by the RTC -chip drivers in the directory @code{c/src/lib/lib/libchip/rtc}. -There is a README file in this directory for each supported -RTC chip. Each of these README explains how to configure the -shared libchip implementation of the RTC driver for that particular -RTC chip. - -The DY-4 DMV177 BSP uses the shared libchip implementation of the RTC -driver. Its @code{RTC_Table} configuration table can be found in -@code{c/src/lib/libbsp/powerpc/dmv177/tod/config.c}. - -@section Initialization - -The @code{rtc_initialize} routine is responsible for initializing the -RTC chip so it can be used. The shared libchip implementation of this -driver supports multiple RTCs and bases its initialization order on -the order the chips are defined in the @code{RTC_Table}. Each chip -defined in the table may or may not be present on this particular board. -It is the responsibility of the @code{deviceProbe} to indicate the -presence of a particular RTC chip. The first RTC found to be present -is considered the preferred RTC. - -In the shared libchip based implementation -of the driver, the following actions are performed: - -@example -@group -rtems_device_driver rtc_initialize( - rtems_device_major_number major, - rtems_device_minor_number minor_arg, - void *arg -) -@{ - for each RTC configured in RTC_Table - if the deviceProbe for this RTC indicates it is present - set RTC_Minor to this device - set RTC_Present to TRUE - break out of this loop - - if RTC_Present is not TRUE - return RTEMS_INVALID_NUMBER to indicate that no RTC is present - - register this minor number as the "/dev/rtc" - - perform the deviceInitialize routine for the preferred RTC chip - - for RTCs past this one in the RTC_Table - if the deviceProbe for this RTC indicates it is present - perform the deviceInitialize routine for this RTC chip - register the configured name for this RTC -@} -@end group -@end example - -The @code{deviceProbe} routine returns TRUE if the device -configured by this entry in the @code{RTC_Table} is present. -This configuration scheme allows one to support multiple versions -of the same board with a single BSP. For example, if the first -generation of a board had Vendor A's RTC chip and the second -generation had Vendor B's RTC chip, RTC_Table could contain -information for both. The @code{deviceProbe} configured -for Vendor A's RTC chip would need to return TRUE if the -board was a first generation one. The @code{deviceProbe} -routines are very board dependent and must be provided by -the BSP. - -@section setRealTimeToRTEMS - -The @code{setRealTimeToRTEMS} routine sets the current RTEMS TOD to that -of the preferred RTC. - -@example -@group -void setRealTimeToRTEMS(void) -@{ - if no RTCs are present - return - - invoke the deviceGetTime routine for the preferred RTC - set the RTEMS TOD using rtems_clock_set -@} -@end group -@end example - -@section setRealTimeFromRTEMS - -The @code{setRealTimeFromRTEMS} routine sets the preferred RTC TOD to the -current RTEMS TOD. - -@example -@group -void setRealTimeFromRTEMS(void) -@{ - if no RTCs are present - return - - obtain the RTEMS TOD using rtems_clock_get - invoke the deviceSetTime routine for the preferred RTC -@} -@end group -@end example - -@section getRealTime - -The @code{getRealTime} returns the preferred RTC TOD to the -caller. - -@example -@group -void getRealTime( rtems_time_of_day *tod ) -@{ - if no RTCs are present - return - - invoke the deviceGetTime routine for the preferred RTC -@} -@end group -@end example - -@section setRealTime - -The @code{setRealTime} routine sets the preferred RTC TOD to the -TOD specified by the caller. - -@example -@group -void setRealTime( rtems_time_of_day *tod ) -@{ - if no RTCs are present - return - - invoke the deviceSetTime routine for the preferred RTC -@} -@end group -@end example - -@section checkRealTime - -The @code{checkRealTime} routine returns the number of seconds -difference between the RTC TOD and the current RTEMS TOD. - -@example -@group -int checkRealTime( void ) -@{ - if no RTCs are present - return -1 - - - obtain the RTEMS TOD using rtems_clock_get - get the TOD from the preferred RTC using the deviceGetTime routine - - convert the RTEMS TOD to seconds - convert the RTC TOD to seconds - - return the RTEMS TOD in seconds - RTC TOD in seconds -@} -@end group -@end example - diff --git a/doc/bsp_howto/shmsupp.t b/doc/bsp_howto/shmsupp.t deleted file mode 100644 index b1234f7bb9..0000000000 --- a/doc/bsp_howto/shmsupp.t +++ /dev/null @@ -1,269 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Shared Memory Support Driver - -The Shared Memory Support Driver is responsible for providing glue -routines and configuration information required by the Shared -Memory Multiprocessor Communications Interface (MPCI). The -Shared Memory Support Driver tailors the portable Shared -Memory Driver to a particular target platform. - -This driver is only required in shared memory multiprocessing -systems that use the RTEMS mulitprocessing support. For more -information on RTEMS multiprocessing capabilities and the -MPCI, refer to the @b{Multiprocessing Manager} chapter -of the @b{RTEMS Application C User's Guide}. - -@section Shared Memory Configuration Table - -The Shared Memory Configuration Table is defined in the following -structure: - -@example -@group -typedef volatile rtems_unsigned32 vol_u32; - -typedef struct @{ - vol_u32 *address; /* write here for interrupt */ - vol_u32 value; /* this value causes interrupt */ - vol_u32 length; /* for this length (0,1,2,4) */ -@} Shm_Interrupt_information; - -struct shm_config_info @{ - vol_u32 *base; /* base address of SHM */ - vol_u32 length; /* length (in bytes) of SHM */ - vol_u32 format; /* SHM is big or little endian */ - vol_u32 (*convert)(); /* neutral conversion routine */ - vol_u32 poll_intr; /* POLLED or INTR driven mode */ - void (*cause_intr)( rtems_unsigned32 ); - Shm_Interrupt_information Intr; /* cause intr information */ -@}; - -typedef struct shm_config_info shm_config_table; -@end group -@end example - -where the fields are defined as follows: - -@table @b -@item base -is the base address of the shared memory buffer used to pass -messages between the nodes in the system. - -@item length -is the length (in bytes) of the shared memory buffer used to pass -messages between the nodes in the system. - -@item format -is either SHM_BIG or SHM_LITTLE to indicate that the neutral format -of the shared memory area is big or little endian. The format -of the memory should be chosen to match most of the inter-node traffic. - -@item convert -is the address of a routine which converts from native format to -neutral format. Ideally, the neutral format is the same as the -native format so this routine is quite simple. - -@item poll_intr -is either INTR_MODE or POLLED_MODE to indicate how the node will be -informed of incoming messages. - -@item cause_intr - -@item Intr -is the information required to cause an interrupt on a node. This -structure contains the following fields: -@table @b -@item address -is the address to write at to cause an interrupt on that node. -For a polled node, this should be NULL. - -@item value -is the value to write to cause an interrupt. - -@item length -is the length of the entity to write on the node to cause an interrupt. -This can be 0 to indicate polled operation, 1 to write a byte, 2 to -write a sixteen-bit entity, and 4 to write a thirty-two bit entity. -@end table -@end table - -@section Primitives - -@subsection Convert Address - -The @code{Shm_Convert_address} is responsible for converting an address -of an entity in the shared memory area into the address that should be -used from this node. Most targets will simply return the address -passed to this routine. However, some target boards will have a special -window onto the shared memory. For example, some VMEbus boards have -special address windows to access addresses that are normally reserved -in the CPU's address space. - -@example -@group -void *Shm_Convert_address( void *address ) -@{ - return the local address version of this bus address -@} -@end group -@end example - -@subsection Get Configuration - -The @code{Shm_Get_configuration} routine is responsible for filling in the -Shared Memory Configuration Table passed to it. - -@example -@group -void Shm_Get_configuration( - rtems_unsigned32 localnode, - shm_config_table **shmcfg -) -@{ - fill in the Shared Memory Configuration Table -@} -@end group -@end example - -@subsection Locking Primitives - -This is a collection of routines that are invoked by the portable -part of the Shared Memory Driver to manage locks in the shared -memory buffer area. Accesses to the shared memory must be -atomic. Two nodes in a multiprocessor system must not be manipulating -the shared data structures simultaneously. The locking primitives -are used to insure this. - -To avoid deadlock, local processor interrupts should be disabled the entire -time the locked queue is locked. - -The locking primitives operate on the lock -@code{field} of the @code{Shm_Locked_queue_Control} -data structure. This structure is defined as follows: - -@example -@group -typedef struct @{ - vol_u32 lock; /* lock field for this queue */ - vol_u32 front; /* first envelope on queue */ - vol_u32 rear; /* last envelope on queue */ - vol_u32 owner; /* receiving (i.e. owning) node */ -@} Shm_Locked_queue_Control; -@end group -@end example - -where each field is defined as follows: - -@table @b -@item lock -is the lock field. Every node in the system must agree on how this -field will be used. Many processor families provide an atomic -"test and set" instruction that is used to manage this field. - -@item front -is the index of the first message on this locked queue. - -@item rear -is the index of the last message on this locked queue. - -@item owner -is the node number of the node that currently has this structure locked. - -@end table - -@subsubsection Initializing a Shared Lock - -The @code{Shm_Initialize_lock} routine is responsible for -initializing the lock field. This routines usually is implemented -as follows: - -@example -@group -void Shm_Initialize_lock( - Shm_Locked_queue_Control *lq_cb -) -@{ - lq_cb->lock = LQ_UNLOCKED; -@} -@end group -@end example - -@subsubsection Acquiring a Shared Lock - -The @code{Shm_Lock} routine is responsible for -acquiring the lock field. Interrupts should be -disabled while that lock is acquired. If the lock -is currently unavailble, then the locking routine -should delay a few microseconds to allow the other -node to release the lock. Doing this reduces bus contention -for the lock. This routines usually is implemented as follows: - -@example -@group -void Shm_Lock( - Shm_Locked_queue_Control *lq_cb -) -@{ - disable processor interrupts - set Shm_isrstat to previous interrupt disable level - - while ( TRUE ) @{ - atomically attempt to acquire the lock - if the lock was acquired - return - delay some small period of time - @} -@} -@end group -@end example - -@subsubsection Releasing a Shared Lock - -The @code{Shm_Unlock} routine is responsible for -releasing the lock field and reenabling processor -interrupts. This routines usually is implemented as follows: - -@example -@group -void Shm_Unlock( - Shm_Locked_queue_Control *lq_cb -) -@{ - set the lock to the unlocked value - reenable processor interrupts to their level prior - to the lock being acquired. This value was saved - in the global variable Shm_isrstat -@} -@end group -@end example - -@section Installing the MPCI ISR - -The @code{Shm_setvec} is invoked by the portable portion -of the shared memory to install the interrupt service routine -that is invoked when an incoming message is announced. Some -target boards support an interprocessor interrupt or mailbox -scheme and this is where the ISR for that interrupt would be -installed. - -On an interrupt driven node, this routine would be implemented -as follows: - -@example -@group -void Shm_setvec( void ) -@{ - install the interprocessor communications ISR -@} -@end group -@end example - -On a polled node, this routine would be empty. - diff --git a/doc/bsp_howto/support.t b/doc/bsp_howto/support.t deleted file mode 100644 index f728851d9d..0000000000 --- a/doc/bsp_howto/support.t +++ /dev/null @@ -1,257 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Miscellaneous Support Files - -@section GCC Compiler Specifications File - -The file @code{bsp_specs} defines the start files and libraries -that are always used with this BSP. The format of this file -is admittedly cryptic and this document will make no attempt -to explain it completely. Below is the @code{bsp_specs} -file from the PowerPC psim BSP: - -@example -@group -%rename cpp old_cpp -%rename lib old_lib -%rename endfile old_endfile -%rename startfile old_startfile -%rename link old_link - -*cpp: -%(old_cpp) %@{qrtems: -D__embedded__@} -Asystem(embedded) - -*lib: -%@{!qrtems: %(old_lib)@} %@{qrtems: --start-group \ -%@{!qrtems_debug: -lrtemsall@} %@{qrtems_debug: -lrtemsall_g@} \ --lc -lgcc --end-group ecrtn%O%s \ -%@{!qnolinkcmds: -T linkcmds%s@}@} - -*startfile: -%@{!qrtems: %(old_startfile)@} %@{qrtems: ecrti%O%s \ -%@{!qrtems_debug: startsim.o%s@} \ -%@{qrtems_debug: startsim_g.o%s@}@} - -*link: -%@{!qrtems: %(old_link)@} %@{qrtems: -Qy -dp -Bstatic \ --T linkcmds%s -e _start -u __vectors@} -@end group -@end example - -The first section of this file renames the built-in definition of -some specification variables so they can be augmented without -embedded their original definition. The subsequent sections -specify what behavior is expected when the @code{-qrtems} or -@code{-qrtems_debug} option is specified. - -The @code{*cpp} definition specifies that when @code{-qrtems} -is specified, predefine the preprocessor symbol @code{__embedded__}. - -The @code{*lib} section insures that the RTEMS library, BSP specific -linker script, gcc support library, and the EABI specific @code{ecrtn} -file are used. - -The @code{*startfile} section specifies that the BSP specific file -@code{startsim.o} will be used instead of @code{crt0.o}. In addition, -the EABI specific file @code{ecrti.o} will be linked in with the -executable. - -The @code{*link} section specifies the arguments that will be passed to -the linker. - -The format of this file is specific to the GNU Compiler Suite. The -argument used to override and extend the compiler built-in specifications -is relatively new to the toolset. The @code{-specs} option is present -in all @code{egcs} distributions and @code{gcc} distributions starting -with version 2.8.0. - -@section README Files - -Most BSPs provide one or more @code{README} files. Generally, there -is a @code{README} file at the top of the BSP source. This file -describes the board and its hardware configuration, provides vendor -information, local configuration information, information on downloading -code to the board, debugging, etc.. The intent of this -file is to help someone begin to use the BSP faster. - -A @code{README} file in a BSP subdirectory typically explains something -about the contents of that subdirectory in greater detail. For example, -it may list the documentation available for a particular peripheral -controller and how to obtain that documentation. It may also explain some -particularly cryptic part of the software in that directory or provide -rationale on the implementation. - -@section times - -This file contains the results of the RTEMS Timing Test Suite. It is -in a standard format so that results from one BSP can be easily compared -with those of another target board. - -If a BSP supports multiple variants, then there may be multiple @code{times} -files. Usually these are named @code{times.VARIANTn}. - -@section Tools Subdirectory - -Some BSPs provide additional tools that aid in using the target board. -These tools run on the development host and are built as part of building -the BSP. Most common is a script to automate running the RTEMS Test Suites -on the BSP. Examples of this include: - -@itemize @bullet - -@item @code{powerpc/psim} includes scripts to ease use of the simulator - -@item @code{m68k/mvme162} includes a utility to download across the -VMEbus into target memory if the host is a VMEbus board in the same -chasis. - -@item @code{unix/posix} includes scripts to run the tests automatically -on this BSP. - -@end itemize - -@section bsp.h Include File - -The file @code{include/bsp.h} contains prototypes and definitions -specific to this board. Every BSP is required to provide a @code{bsp.h}. -The best approach to writing a @code{bsp.h} is copying an existing one -as a starting point. - -Many @code{bsp.h} files provide prototypes of variables defined -in the linker script (@code{linkcmds}). - -There are a number of fields in this file that are used only by the -RTEMS Test Suites. The following is a list of these: - -@itemize @bullet -@item @code{MAX_LONG_TEST_DURATION} - the longest length of time a -"long running" test should run. - -@item @code{MAX_SHORT_TEST_DURATION} - the longest length of time a -"short running" test should run. - -@item @code{MUST_WAIT_FOR_INTERRUPT} - modifies behavior of @code{tm27}. - -@item @code{Install_tm27_vector} - installs the interrupt service -routine for the Interrupt Benchmark Test (@code{tm27}). - -@item @code{Cause_tm27_intr} - generates the interrupt source -used in the Interrupt Benchmark Test (@code{tm27}). - -@item @code{Clear_tm27_intr} - clears the interrupt source -used in the Interrupt Benchmark Test (@code{tm27}). - -@item @code{Lower_tm27_intr} - lowers the interrupt mask so the -interrupt source used in the Interrupt Benchmark Test (@code{tm27}) -can generate a nested interrupt. - -@end itemize - -@section Calling Overhead File - -The file @code{include/coverhd.h} contains the overhead associated -with invoking each directive. This overhead consists of the execution -time required to package the parameters as well as to execute the "jump to -subroutine" and "return from subroutine" sequence. The intent of this -file is to help separate the calling overhead from the actual execution -time of a directive. This file is only used by the tests in the -RTEMS Timing Test Suite. - -The numbers in this file are obtained by running the "Timer Overhead" -@code{tmoverhd} test. The numbers in this file may be 0 and no -overhead is subtracted from the directive execution times reported by -the Timing Suite. - -@section sbrk() Implementation - -If the BSP wants to dynamically extend the heap used by the -C Library memory allocation routines (i.e. @code{malloc} family), -then this routine must be functional. The following is the -prototype for this routine: - -@example -void * sbrk(size_t increment) -@end example - -The @code{increment} amount is based upon the @code{sbrk_amount} -parameter passed to the @code{RTEMS_Malloc_Initialize} during system -initialization. -See @ref{Initialization Code RTEMS Pretasking Callback} for more -information. - -There is a default implementation which returns an error to indicate -that the heap can not be extended. This implementation can be -found in @code{c/src/lib/libbsp/shared/sbrk.c}. Many of the BSPs -use this shared implementation. In order to use this implementation, -the file @code{Makefile.in} in the BSP's @code{startup} directory -must be modified so that the @code{$VPATH} variable searches -both the @code{startup} directory and the shared directory. The following -illustates the @code{VPATH} setting in the PowerPC psim BSP's -@code{startup/Makefile.in}: - -@example -VPATH = @@srcdir@@:@@srcdir@@/../../../shared -@end example - -This instructs make to look in all of the directories in the @code{VPATH} -for the source files. The directories will be examined in the order -they are specified. - -@section bsp_cleanup() - Cleanup the Hardware - -The @code{bsp_cleanup()} is the last C code invoked. Most of the BSPs -use the same shared version of @code{bsp_cleanup()} that does nothing. -This implementation is located in the following file: - -@example -c/src/lib/libbsp/shared/bspclean.c -@end example - -The @code{bsp_cleanup()} routine can be used to return to a ROM monitor, -insure that interrupt sources are disabled, etc.. This routine is the -last place to insure a clean shutdown of the hardware. - -@section set_vector() - Install an Interrupt Vector - -The @code{set_vector} routine is responsible for installing an interrupt -vector. It invokes the support routines necessary to install an -interrupt handler as either a "raw" or an RTEMS interrupt handler. Raw -handlers bypass the RTEMS interrupt structure and are responsible for -saving and restoring all their own registers. Raw handlers are useful -for handling traps, debug vectors, etc.. - -The @code{set_vector} routine is a central place to perform -interrupt controller manipulation and encapsulate that information. -It is usually implemented as follows: - -@example -@group -rtems_isr_entry set_vector( /* returns old vector */ - rtems_isr_entry handler, /* isr routine */ - rtems_vector_number vector, /* vector number */ - int type /* RTEMS or RAW intr */ -) -@{ - if the type is RAW - install the raw vector - else - use rtems_interrupt_catch to install the vector - - perform any interrupt controller necessary to unmask - the interrupt source - - return the previous handler -@} -@end group -@end example - - -@b{NOTE:} @code{set_vector} is provided by the majority of BSPs but -not all. In particular, the i386 BSPs use a different scheme. - diff --git a/doc/bsp_howto/target.t b/doc/bsp_howto/target.t deleted file mode 100644 index d7b9f51f3e..0000000000 --- a/doc/bsp_howto/target.t +++ /dev/null @@ -1,214 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Target Dependent Files - -RTEMS has a multi-layered approach to portability. This is done to -maximize the amount of software that can be reused. Much of the -RTEMS source code can be reused on all RTEMS platforms. Other parts -of the executive are specific to hardware in some sense. -RTEMS classifies target dependent code based upon its dependencies -into one of the following categories. - -@itemize @bullet -@item CPU dependent -@item Board dependent -@item Peripheral dependent -@end itemize - -@section CPU Dependent - -This class of code includes the foundation -routines for the executive proper such as the context switch and -the interrupt subroutine implementations. Sources for the supported -processor families can be found in @code{c/src/exec/score/cpu}. -A good starting point for a new family of processors is the -@code{no_cpu} directory, which holds both prototypes and -descriptions of each needed CPU dependent function. - -CPU dependent code is further subcategorized if the implementation is -dependent on a particular CPU model. For example, the MC68000 and MC68020 -processors are both members of the m68k CPU family but there are significant -differents between these CPU models which RTEMS must take into account. - -@section Board Dependent - -This class of code provides the most specific glue between RTEMS and -a particular board. This code is represented by the Board Support Packages -and associated Device Drivers. Sources for the BSPs included in the -RTEMS distribution are located in the directory @code{c/src/lib/libbsp}. -The BSP source directory is further subdivided based on the CPU family -and BSP. - -Some BSPs may support multiple board models within a single board family. -This is necessary when the board supports multiple variants on a -single base board. For example, the Motorola MVME162 board family has a -fairly large number of variations based upon the particular CPU model -and the peripherals actually placed on the board. - -@section Peripheral Dependent - -This class of code provides a reusable library of peripheral device -drivers which can be tailored easily to a particular board. The -libchip library is a collection of reusable software objects that -correspond to standard controllers. Just as the hardware engineer -chooses a standard controller when designing a board, the goal of -this library is to let the software engineer do the same thing. - -The source code for the reusable peripheral driver library may be found -in the directory @code{c/src/lib/libchip}. The source code is further -divided based upon the class of hardware. Example classes include serial -communications controllers, real-time clocks, non-volatile memory, and -network controllers. - -@section Questions to Ask - -When evaluating what is required to support RTEMS applications on -a particular target board, the following questions should be asked: - -@itemize @bullet - -@item Does a BSP for this board exist? - -@item Does a BSP for a similar board exists? - -@item Is the board's CPU supported? - -@end itemize - -If there is already a BSP for the board, then things may already be ready -to start developing application software. All that remains is to verify -that the existing BSP provides device drivers for all the peripherals -on the board that the application will be using. For example, the application -in question may require that the board's Ethernet controller be used and -the existing BSP may not support this. - -If the BSP does not exist and the board's CPU model is supported, then -examine the reusable chip library and existing BSPs for a close match. -Other BSPs and libchip provide starting points for the development -of a new BSP. It is often possible to copy existing components in -the reusable chip library or device drivers from BSPs from different -CPU families as the starting point for a new device driver. -This will help reduce the development effort required. - -If the board's CPU family is supported but the particular CPU model on -that board is not, then the RTEMS port to that CPU family will have to -be augmented. After this is done, development of the new BSP can proceed. - -Otherwise both CPU dependent code and the BSP will have to be written. - -Regardless of the amount of development required, OAR Corporation -offers custom development services to assist RTEMS users. -For more information on custom development, training courses, and -support, contact OAR Corporation at -@uref{http://www.oarcorp.com}. - - -@section CPU Dependent Executive Files - -The CPU dependent files in the RTEMS executive source code are found -in the following directory: - -@example -c/src/exec/score/cpu/@i{CPU} -@end example - -where @i{CPU} is replaced with the CPU family name. - -Within each CPU dependent directory inside the executive proper is a -file named @code{@i{CPU}.h} which contains information about each of the -supported CPU models within that family. - -@section CPU Dependent Support Files - -The CPU dependent support files contain routines which aid in the development -of applications using that CPU family. For example, the support routines -may contain standard trap handlers for alignment or floating point exceptions -or device drivers for peripheral controllers found on the CPU itself. -This class of code may be found in the following directory: - -@example -c/src/lib/libcpu/@i{CPU} -@end example - -CPU model dependent support code is found in the following directory: - -@example -c/src/lib/libcpu/@i{CPU}/@i{CPU_MODEL} -@end example - -@section Board Support Package Structure - -The BSPs are all under the c/src/lib/libbsp directory. Below this -directory, there is a subdirectory for each CPU family. Each BSP -is found under the subdirectory for the appropriate processor -family (m68k, powerpc, etc.). In addition, there is source code -available which may be shared across all BSPs regardless of -the CPU family or just across BSPs within a single CPU family. This -results in a BSP using the following directories: - -@example -c/src/lib/libbsp/shared -c/src/lib/libbsp/@i{CPU}/shared -c/src/lib/libbsp/@i{CPU}/@i{BSP} -@end example - -Under each BSP specific directory, there is a collection of -subdirectories. For commonly provided functionality, the BSPs -follow a convention on subdirectory naming. The following list -describes the commonly found subdirectories under each BSP. - -@itemize @bullet - -@item @b{console}: -is technically the serial driver for the BSP rather -than just a console driver, it deals with the board -UARTs (i.e. serial devices). - -@item @b{clock}: -support for the clock tick -- a regular time basis to the kernel. - -@item @b{timer}: -support of timer devices. - -@item @b{rtc}: -support for the hardware real-time clock. - -@item @b{nvmem}: -support for non-volatile memory such as EEPROM or Flash. - -@item @b{network}: -the Ethernet driver. - -@item @b{shmsupp}: -support of shared memory driver MPCI layer in a multiprocessor system, - -@item @b{include}: -include files for this BSP. - -@item @b{wrapup}: -bundles all the components necessary to construct the BSP library. - -@end itemize - -The build order of the BSP is determined by the Makefile structure. -This structure is discussed in more detail in the @ref{Makefiles} -chapter. - -@b{NOTE:} This manual refers to the gen68340 BSP for numerous concrete -examples. You should have a copy of the gen68340 BSP available while -reading this piece of documentation. This BSP is located in the -following directory: - -@example -c/src/lib/libbsp/m68k/gen68340 -@end example - -Later in this document, the $BSP340_ROOT label will be used -to refer to this directory. - diff --git a/doc/bsp_howto/timer.t b/doc/bsp_howto/timer.t deleted file mode 100644 index fa4850a424..0000000000 --- a/doc/bsp_howto/timer.t +++ /dev/null @@ -1,121 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Timer Driver - -The timer driver is primarily used by the RTEMS Timing Tests. -This driver provides as accurate a benchmark timer as possible. -It typically reports its time in microseconds, CPU cycles, or -bus cycles. This information can be very useful for determining -precisely what pieces of code require optimization and to measure the -impact of specific minor changes. - -The gen68340 BSP also uses the Timer Driver to support a high performance -mode of the on-CPU UART. - -@section Benchmark Timer - -The RTEMS Timing Test Suite requires a benchmark timer. The -RTEMS Timing Test Suite is very helpful for determining -the performance of target hardware and comparing its performance -to that of other RTEMS targets. - -This section describes the routines which are assumed to exist by -the RTEMS Timing Test Suite. The names used are @b{EXACTLY} what -is used in the RTEMS Timing Test Suite so follow the naming convention. - -@subsection Timer_initialize - -Initialize the timer source. - -@example -void Timer_initialize(void) -@{ - initialize the benchmark timer -@} -@end example - -@subsection Read_timer - -The @code{Read_timer} routine -returns the number of benchmark time units (typically microseconds) -that have elapsed since the last call to @code{Timer_initialize}. - -@example -int Read_timer(void) -@{ - stop time = read the hardware timer - if the subtract overhead feature is enabled - subtract overhead from stop time - return the stop time -@} -@end example - -Many implementations of this routine subtract the overhead required -to initialize and read the benchmark timer. This makes the times reported -more accurate. - -Some implementations report 0 if the harware timer value change is -sufficiently small. This is intended to indicate that the execution time -is below the resolution of the timer. - -@subsection An Empty Function - -This routine is invoked by the RTEMS Timing Test Suite to measure -the cost of invoking a subroutine. - -@example -rtems_status_code Empty_function (void) -@{ - return RTEMS_SUCCESSFUL; -@} -@end example - -@subsection Set_find_average_overhead - -This routine is invoked by the "Check Timer" (@code{tmck}) test in the -RTEMS Timing Test Suite. It makes the @code{Read_timer} -routine NOT subtract the overhead required -to initialize and read the benchmark timer. This is used -by the @code{tmoverhd} test to determine the overhead -required to initialize and read the timer. - -@example -void Set_find_average_overhead(rtems_boolean find_flag) -@{ - disable the subtract overhead feature -@} -@end example - -The @code{Timer_driver_Find_average_overhead} variable is usually -used to indicate the state of the "subtract overhead feature". - -@section gen68340 UART FIFO Full Mode - -The gen68340 BSP is an example of the use of the timer to support the UART -input FIFO full mode (FIFO means First In First Out and roughly means -buffer). This mode consists in the UART raising an interrupt when n -characters have been received (@i{n} is the UART's FIFO length). It results -in a lower interrupt processing time, but the problem is that a scanf -primitive will block on a receipt of less than @i{n} characters. The solution -is to set a timer that will check whether there are some characters -waiting in the UART's input FIFO. The delay time has to be set carefully -otherwise high rates will be broken: - -@itemize @bullet - -@item if no character was received last time the interrupt subroutine was -entered, set a long delay, - -@item otherwise set the delay to the delay needed for @i{n} characters -receipt. - -@end itemize - - - diff --git a/doc/common/cpright.texi b/doc/common/cpright.texi deleted file mode 100644 index 2d188d2394..0000000000 --- a/doc/common/cpright.texi +++ /dev/null @@ -1,45 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c The following puts a space somewhere on an otherwise empty page so we -@c can force the copyright description onto a left hand page. -@c - -@tex -{\parskip=0pt \hfill On-Line Applications Research Corporation\par \hfill -\TeX{}info \texinfoversion\par } -@end tex - -@vskip 0pt plus 1filll -COPYRIGHT @copyright{} 1988 - 1999.@* -On-Line Applications Research Corporation (OAR).@* - -The authors have used their best efforts in preparing -this material. These efforts include the development, research, -and testing of the theories and programs to determine their -effectiveness. No warranty of any kind, expressed or implied, -with regard to the software or the material contained in this -document is provided. No liability arising out of the -application or use of any product described in this document is -assumed. The authors reserve the right to revise this material -and to make changes from time to time in the content hereof -without obligation to notify anyone of such revision or changes. - -Any inquiries concerning RTEMS, its related support -components, or its documentation should be directed to either: - -@example -On-Line Applications Research Corporation -4910-L Corporate Drive -Huntsville, AL 35805 -VOICE: (256) 722-9985 -FAX: (256) 722-0985 -EMAIL: rtems@@OARcorp.com -@end example - diff --git a/doc/common/dvi.gif b/doc/common/dvi.gif deleted file mode 100644 index 163a5d52b5..0000000000 Binary files a/doc/common/dvi.gif and /dev/null differ diff --git a/doc/common/oaronly.jpg b/doc/common/oaronly.jpg deleted file mode 100644 index c87c151404..0000000000 Binary files a/doc/common/oaronly.jpg and /dev/null differ diff --git a/doc/common/pdf.gif b/doc/common/pdf.gif deleted file mode 100644 index c88fd777c4..0000000000 Binary files a/doc/common/pdf.gif and /dev/null differ diff --git a/doc/common/pdf1.gif b/doc/common/pdf1.gif deleted file mode 100644 index 784fe2ac8c..0000000000 Binary files a/doc/common/pdf1.gif and /dev/null differ diff --git a/doc/common/ps.gif b/doc/common/ps.gif deleted file mode 100644 index 0f565bc1db..0000000000 Binary files a/doc/common/ps.gif and /dev/null differ diff --git a/doc/common/setup.texi b/doc/common/setup.texi deleted file mode 100644 index 38ff545f7f..0000000000 --- a/doc/common/setup.texi +++ /dev/null @@ -1,75 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Set Variables -@c - -@set RTEMS-RELEASE 20000104 -@set RTEMS-EDITION 20000104 -@set RTEMS-VERSION 20000104 -@set RTEMS-UPDATE-DATE January 4 2000 -@set RTEMS-UPDATE-MONTH January 2000 - -@c -@c The following determines which set of the tables and figures we will use. -@c We default to ASCII but if available TeX or HTML versions will -@c be used instead. -@c - -@set use-ascii -@clear use-html -@clear use-tex - -@iftex -@clear use-ascii -@clear use-html -@set use-tex -@end iftex - -@ifhtml -@clear use-ascii -@clear use-tex -@set use-html -@end ifhtml - -@c -@c The following variable says to use texinfo or html for the two column -@c texinfo tables. For somethings the format does not look good in html. -@c With our adjustment to the left column in TeX, it nearly always looks -@c good printed. -@c -@ifset use-ascii -@set use-texinfo-tables -@end ifset -@ifset use-tex -@set use-texinfo-tables -@end ifset -@ifset use-html -@clear use-texinfo-tables -@end ifset - -@c -@c Custom whitespace adjustments. We could fiddle a bit more. -@c -@tex -\global\parindent 0in -\global\chapheadingskip = 15pt plus 4pt minus 2pt -\global\secheadingskip = 12pt plus 4pt minus 2pt -\global\subsecheadingskip = 9pt plus 4pt minus 2pt -\global\hbadness = 10000 -\global\tolerance = 6000 -\global\tableindent = 1.5in -\global\itemindent = 0.5in - -@ifclear smallbook -\global\parskip 6pt plus 1pt -@end ifclear -@end tex - - diff --git a/doc/common/timemac.texi b/doc/common/timemac.texi deleted file mode 100644 index 3a98a12bf2..0000000000 --- a/doc/common/timemac.texi +++ /dev/null @@ -1,36 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c -@c -@c Macros to help with the tables in this file -@c - -@tex -\global\advance \smallskipamount by -4pt - -\global\def\rtemstimetable{ -\vrule\strut##& -\hbox to 3.0in{\enskip##\hfil}& -\hbox to 0.75in{\enskip##\hfil}& -\vrule##\cr -\noalign{\hrule} -} - -\global\def\rtemsendtimetable{} -\global\def\rtemsonecase#1#2{ -& \bf #1\hfil& #2 & \cr\noalign{\hrule} -} - -\global\def\rtemsdirective#1{ -& \bf #1 \hfil& & \cr\noalign{\hrule} -} - -\global\def\rtemscase#1#2{ -& \hskip 0.3in #1\hfil& #2 & \cr\noalign{\hrule} -} - -@end tex diff --git a/doc/common/timetbl.t b/doc/common/timetbl.t deleted file mode 100644 index a190cbad1b..0000000000 --- a/doc/common/timetbl.t +++ /dev/null @@ -1,1330 +0,0 @@ -@c ****** This comment is here to remind you not to edit the timetbl.t -@c ****** in any directory but common. -@c -@c Time Table Template -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifset use-tex -@sp 1 -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{No Floating Point Contexts}{RTEMS_NO_FP_CONTEXTS} -\rtemsdirective{Floating Point Contexts} -\rtemscase{restore first FP task}{RTEMS_RESTORE_1ST_FP_TASK} -\rtemscase{save initialized, restore initialized}{RTEMS_SAVE_INIT_RESTORE_INIT} -\rtemscase{save idle, restore initialized}{RTEMS_SAVE_IDLE_RESTORE_INIT} -\rtemscase{save idle, restore idle}{RTEMS_SAVE_IDLE_RESTORE_IDLE} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet -@item No Floating Point Contexts -@itemize - -@item only case: RTEMS_NO_FP_CONTEXTS -@end itemize -@item Floating Point Contexts -@itemize - -@item restore first FP task: RTEMS_RESTORE_1ST_FP_TASK -@item save initialized, restore initialized: RTEMS_SAVE_INIT_RESTORE_INIT -@item save idle, restore initialized: RTEMS_SAVE_IDLE_RESTORE_INIT -@item save idle, restore idle: RTEMS_SAVE_IDLE_RESTORE_INIT -@end itemize -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - -
    No Floating Point ContextsRTEMS_NO_FP_CONTEXTS
    Floating Point Contexts
    restore first FP task
    		RTEMS_RESTORE_1ST_FP_TASK
    save initialized, restore initialized
    		RTEMS_SAVE_INIT_RESTORE_INIT
    save idle, restore initialized
    		RTEMS_SAVE_IDLE_RESTORE_INIT
    save idle, restore idle
    		RTEMS_SAVE_IDLE_RESTORE_IDLE
    -
    -@end html -@end ifset - -@section Directive Times - -This sections is divided into a number of -subsections, each of which contains a table listing the -execution times of that manager's directives. - -@page -@section Task Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{TASK\_CREATE}{RTEMS_TASK_CREATE_ONLY} -\rtemsonecase{TASK\_IDENT}{RTEMS_TASK_IDENT_ONLY} -\rtemsonecase{TASK\_START}{RTEMS_TASK_START_ONLY} -\rtemsdirective{TASK\_RESTART} -\rtemscase{calling task}{RTEMS_TASK_RESTART_CALLING_TASK} -\rtemscase{suspended task -- returns to caller} - {RTEMS_TASK_RESTART_SUSPENDED_RETURNS_TO_CALLER} -\rtemscase{blocked task -- returns to caller} - {RTEMS_TASK_RESTART_BLOCKED_RETURNS_TO_CALLER} -\rtemscase{ready task -- returns to caller} - {RTEMS_TASK_RESTART_READY_RETURNS_TO_CALLER} -\rtemscase{suspended task -- preempts caller} - {RTEMS_TASK_RESTART_SUSPENDED_PREEMPTS_CALLER} -\rtemscase{blocked task -- preempts caller} - {RTEMS_TASK_RESTART_BLOCKED_PREEMPTS_CALLER} -\rtemscase{ready task -- preempts caller} - {RTEMS_TASK_RESTART_READY_PREEMPTS_CALLER} -\rtemsdirective{TASK\_DELETE} -\rtemscase{calling task}{RTEMS_TASK_DELETE_CALLING_TASK} -\rtemscase{suspended task}{RTEMS_TASK_DELETE_SUSPENDED_TASK} -\rtemscase{blocked task}{RTEMS_TASK_DELETE_BLOCKED_TASK} -\rtemscase{ready task}{RTEMS_TASK_DELETE_READY_TASK} -\rtemsdirective{TASK\_SUSPEND} -\rtemscase{calling task}{RTEMS_TASK_SUSPEND_CALLING_TASK} -\rtemscase{returns to caller}{RTEMS_TASK_SUSPEND_RETURNS_TO_CALLER} -\rtemsdirective{TASK\_RESUME} -\rtemscase{task readied -- returns to caller} - {RTEMS_TASK_RESUME_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_TASK_RESUME_TASK_READIED_PREEMPTS_CALLER} -\rtemsdirective{TASK\_SET\_PRIORITY} -\rtemscase{obtain current priority} - {RTEMS_TASK_SET_PRIORITY_OBTAIN_CURRENT_PRIORITY} -\rtemscase{returns to caller}{RTEMS_TASK_SET_PRIORITY_RETURNS_TO_CALLER} -\rtemscase{preempts caller}{RTEMS_TASK_SET_PRIORITY_PREEMPTS_CALLER} -\rtemsdirective{TASK\_MODE} -\rtemscase{obtain current mode}{RTEMS_TASK_MODE_OBTAIN_CURRENT_MODE} -\rtemscase{no reschedule}{RTEMS_TASK_MODE_NO_RESCHEDULE} -\rtemscase{reschedule -- returns to caller} - {RTEMS_TASK_MODE_RESCHEDULE_RETURNS_TO_CALLER} -\rtemscase{reschedule -- preempts caller} - {RTEMS_TASK_MODE_RESCHEDULE_PREEMPTS_CALLER} -\rtemsonecase{TASK\_GET\_NOTE}{RTEMS_TASK_GET_NOTE_ONLY} -\rtemsonecase{TASK\_SET\_NOTE}{RTEMS_TASK_SET_NOTE_ONLY} -\rtemsdirective{TASK\_WAKE\_AFTER} -\rtemscase{yield -- returns to caller} - {RTEMS_TASK_WAKE_AFTER_YIELD_RETURNS_TO_CALLER} -\rtemscase{yield -- preempts caller} - {RTEMS_TASK_WAKE_AFTER_YIELD_PREEMPTS_CALLER} -\rtemsonecase{TASK\_WAKE\_WHEN}{RTEMS_TASK_WAKE_WHEN_ONLY} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item TASK_CREATE -@itemize - -@item only case: RTEMS_TASK_CREATE_ONLY -@end itemize - -@item TASK_IDENT -@itemize - -@item only case: RTEMS_TASK_IDENT_ONLY -@end itemize - -@item TASK_START -@itemize - -@item only case: RTEMS_TASK_START_ONLY -@end itemize - -@item TASK_RESTART -@itemize - -@item calling task: RTEMS_TASK_RESTART_CALLING_TASK -@item suspended task -- returns to caller: RTEMS_TASK_RESTART_SUSPENDED_RETURNS_TO_CALLER -@item blocked task -- returns to caller: RTEMS_TASK_RESTART_BLOCKED_RETURNS_TO_CALLER -@item ready task -- returns to caller: RTEMS_TASK_RESTART_READY_RETURNS_TO_CALLER -@item suspended task -- preempts caller: RTEMS_TASK_RESTART_SUSPENDED_PREEMPTS_CALLER -@item blocked task -- preempts caller: RTEMS_TASK_RESTART_BLOCKED_PREEMPTS_CALLER -@item ready task -- preempts caller: RTEMS_TASK_RESTART_READY_PREEMPTS_CALLER -@end itemize - -@item TASK_DELETE -@itemize - -@item calling task: RTEMS_TASK_DELETE_CALLING_TASK -@item suspended task: RTEMS_TASK_DELETE_SUSPENDED_TASK -@item blocked task: RTEMS_TASK_DELETE_BLOCKED_TASK -@item ready task: RTEMS_TASK_DELETE_READY_TASK -@end itemize - -@item TASK_SUSPEND -@itemize - -@item calling task: RTEMS_TASK_SUSPEND_CALLING_TASK -@item returns to caller: RTEMS_TASK_SUSPEND_RETURNS_TO_CALLER -@end itemize - -@item TASK_RESUME -@itemize - -@item task readied -- returns to caller: RTEMS_TASK_RESUME_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_TASK_RESUME_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@item TASK_SET_PRIORITY -@itemize - -@item obtain current priority: RTEMS_TASK_SET_PRIORITY_OBTAIN_CURRENT_PRIORITY -@item returns to caller: RTEMS_TASK_SET_PRIORITY_RETURNS_TO_CALLER -@item preempts caller: RTEMS_TASK_SET_PRIORITY_PREEMPTS_CALLER -@end itemize - -@item TASK_MODE -@itemize - -@item obtain current mode: RTEMS_TASK_MODE_OBTAIN_CURRENT_MODE -@item no reschedule: RTEMS_TASK_MODE_NO_RESCHEDULE -@item reschedule -- returns to caller: RTEMS_TASK_MODE_RESCHEDULE_RETURNS_TO_CALLER -@item reschedule -- preempts caller: RTEMS_TASK_MODE_RESCHEDULE_PREEMPTS_CALLER -@end itemize - -@item TASK_GET_NOTE -@itemize - -@item only case: RTEMS_TASK_GET_NOTE_ONLY -@end itemize - -@item TASK_SET_NOTE -@itemize - -@item only case: RTEMS_TASK_SET_NOTE_ONLY -@end itemize - -@item TASK_WAKE_AFTER -@itemize - -@item yield -- returns to caller: RTEMS_TASK_WAKE_AFTER_YIELD_RETURNS_TO_CALLER -@item yield -- preempts caller: RTEMS_TASK_WAKE_AFTER_YIELD_PREEMPTS_CALLER -@end itemize - -@item TASK_WAKE_WHEN -@itemize - -@item only case: RTEMS_TASK_WAKE_WHEN_ONLY -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    TASK_CREATERTEMS_TASK_CREATE_ONLY
    TASK_IDENTRTEMS_TASK_IDENT_ONLY
    TASK_STARTRTEMS_TASK_START_ONLY
    TASK_RESTART
    calling task
    		RTEMS_TASK_RESTART_CALLING_TASK
    suspended task -- returns to caller
    		RTEMS_TASK_RESTART_SUSPENDED_RETURNS_TO_CALLER
    blocked task -- returns to caller
    		RTEMS_TASK_RESTART_BLOCKED_RETURNS_TO_CALLER
    ready task -- returns to caller
    		RTEMS_TASK_RESTART_READY_RETURNS_TO_CALLER
    suspended task -- preempts caller
    		RTEMS_TASK_RESTART_SUSPENDED_PREEMPTS_CALLER
    blocked task -- preempts caller
    		RTEMS_TASK_RESTART_BLOCKED_PREEMPTS_CALLER
    ready task -- preempts caller
    		RTEMS_TASK_RESTART_READY_PREEMPTS_CALLER
    TASK_DELETE
    calling task
    		RTEMS_TASK_DELETE_CALLING_TASK
    suspended task
    		RTEMS_TASK_DELETE_SUSPENDED_TASK
    blocked task
    		RTEMS_TASK_DELETE_BLOCKED_TASK
    ready task
    		RTEMS_TASK_DELETE_READY_TASK
    TASK_SUSPEND
    calling task
    		RTEMS_TASK_SUSPEND_CALLING_TASK
    returns to caller
    		RTEMS_TASK_SUSPEND_RETURNS_TO_CALLER
    TASK_RESUME
    task readied -- returns to caller
    		RTEMS_TASK_RESUME_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		RTEMS_TASK_RESUME_TASK_READIED_PREEMPTS_CALLER
    TASK_SET_PRIORITY
    obtain current priority
    		RTEMS_TASK_SET_PRIORITY_OBTAIN_CURRENT_PRIORITY
    returns to caller
    		RTEMS_TASK_SET_PRIORITY_RETURNS_TO_CALLER
    preempts caller
    		RTEMS_TASK_SET_PRIORITY_PREEMPTS_CALLER
    TASK_MODE
    obtain current mode
    		RTEMS_TASK_MODE_OBTAIN_CURRENT_MODE
    no reschedule
    		RTEMS_TASK_MODE_NO_RESCHEDULE
    reschedule -- returns to caller
    		RTEMS_TASK_MODE_RESCHEDULE_RETURNS_TO_CALLER
    reschedule -- preempts caller
    		RTEMS_TASK_MODE_RESCHEDULE_PREEMPTS_CALLER
    TASK_GET_NOTERTEMS_TASK_GET_NOTE_ONLY
    TASK_SET_NOTERTEMS_TASK_SET_NOTE_ONLY
    TASK_WAKE_AFTER
    yield -- returns to caller
    		RTEMS_TASK_WAKE_AFTER_YIELD_RETURNS_TO_CALLER
    yield -- preempts caller
    		RTEMS_TASK_WAKE_AFTER_YIELD_PREEMPTS_CALLER
    TASK_WAKE_WHENRTEMS_TASK_WAKE_WHEN_ONLY
    -
    -@end html -@end ifset - -@page -@section Interrupt Manager - -It should be noted that the interrupt entry times -include vectoring the interrupt handler. - -@ifset use-tex -@sp 1 -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsdirective{Interrupt Entry Overhead} -\rtemscase{returns to nested interrupt}{RTEMS_INTR_ENTRY_RETURNS_TO_NESTED} -\rtemscase{returns to interrupted task} - {RTEMS_INTR_ENTRY_RETURNS_TO_INTERRUPTED_TASK} -\rtemscase{returns to preempting task} - {RTEMS_INTR_ENTRY_RETURNS_TO_PREEMPTING_TASK} -\rtemsdirective{Interrupt Exit Overhead} -\rtemscase{returns to nested interrupt}{RTEMS_INTR_EXIT_RETURNS_TO_NESTED} -\rtemscase{returns to interrupted task} - {RTEMS_INTR_EXIT_RETURNS_TO_INTERRUPTED_TASK} -\rtemscase{returns to preempting task} - {RTEMS_INTR_EXIT_RETURNS_TO_PREEMPTING_TASK} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item Interrupt Entry Overhead -@itemize - -@item returns to nested interrupt: RTEMS_INTR_ENTRY_RETURNS_TO_NESTED -@item returns to interrupted task: RTEMS_INTR_ENTRY_RETURNS_TO_INTERRUPTED_TASK -@item returns to preempting task: RTEMS_INTR_ENTRY_RETURNS_TO_PREEMPTING_TASK -@end itemize - -@item Interrupt Exit Overhead -@itemize - -@item returns to nested interrupt: RTEMS_INTR_EXIT_RETURNS_TO_NESTED -@item returns to interrupted task: RTEMS_INTR_EXIT_RETURNS_TO_INTERRUPTED_TASK -@item returns to preempting task: RTEMS_INTR_EXIT_RETURNS_TO_PREEMPTING_TASK -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - -
    Interrupt Entry Overhead
    returns to nested interrupt
    		RTEMS_INTR_ENTRY_RETURNS_TO_NESTED
    returns to interrupted task
    		RTEMS_INTR_ENTRY_RETURNS_TO_INTERRUPTED_TASK
    returns to preempting task
    		RTEMS_INTR_ENTRY_RETURNS_TO_PREEMPTING_TASK
    Interrupt Exit Overhead
    returns to nested interrupt
    		RTEMS_INTR_EXIT_RETURNS_TO_NESTED
    returns to interrupted task
    		RTEMS_INTR_EXIT_RETURNS_TO_INTERRUPTED_TASK
    returns to preempting task
    		RTEMS_INTR_EXIT_RETURNS_TO_PREEMPTING_TASK
    -
    -@end html -@end ifset - - -@section Clock Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{CLOCK\_SET}{RTEMS_CLOCK_SET_ONLY} -\rtemsonecase{CLOCK\_GET}{RTEMS_CLOCK_GET_ONLY} -\rtemsonecase{CLOCK\_TICK}{RTEMS_CLOCK_TICK_ONLY} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item CLOCK_SET -@itemize - -@item only case: RTEMS_CLOCK_SET_ONLY -@end itemize - -@item CLOCK_GET -@itemize - -@item only case: RTEMS_CLOCK_GET_ONLY -@end itemize - -@item CLOCK_TICK -@itemize - -@item only case: RTEMS_CLOCK_TICK_ONLY -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - -
    CLOCK_SETRTEMS_CLOCK_SET_ONLY
    CLOCK_GETRTEMS_CLOCK_GET_ONLY
    CLOCK_TICKRTEMS_CLOCK_TICK_ONLY
    -
    -@end html -@end ifset - -@section Timer Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{TIMER\_CREATE}{RTEMS_TIMER_CREATE_ONLY} -\rtemsonecase{TIMER\_IDENT}{RTEMS_TIMER_IDENT_ONLY} -\rtemsdirective{TIMER\_DELETE} -\rtemscase{inactive}{RTEMS_TIMER_DELETE_INACTIVE} -\rtemscase{active}{RTEMS_TIMER_DELETE_ACTIVE} -\rtemsdirective{TIMER\_FIRE\_AFTER} -\rtemscase{inactive}{RTEMS_TIMER_FIRE_AFTER_INACTIVE} -\rtemscase{active}{RTEMS_TIMER_FIRE_AFTER_ACTIVE} -\rtemsdirective{TIMER\_FIRE\_WHEN} -\rtemscase{inactive}{RTEMS_TIMER_FIRE_WHEN_INACTIVE} -\rtemscase{active}{RTEMS_TIMER_FIRE_WHEN_ACTIVE} -\rtemsdirective{TIMER\_RESET} -\rtemscase{inactive}{RTEMS_TIMER_RESET_INACTIVE} -\rtemscase{active}{RTEMS_TIMER_RESET_ACTIVE} -\rtemsdirective{TIMER\_CANCEL} -\rtemscase{inactive}{RTEMS_TIMER_CANCEL_INACTIVE} -\rtemscase{active}{RTEMS_TIMER_CANCEL_ACTIVE} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item TIMER_CREATE -@itemize - -@item only case: RTEMS_TIMER_CREATE_ONLY -@end itemize - -@item TIMER_IDENT -@itemize - -@item only case: RTEMS_TIMER_IDENT_ONLY -@end itemize - -@item TIMER_DELETE -@itemize - -@item inactive: RTEMS_TIMER_DELETE_INACTIVE -@item active: RTEMS_TIMER_DELETE_ACTIVE -@end itemize - -@item TIMER_FIRE_AFTER -@itemize - -@item inactive: RTEMS_TIMER_FIRE_AFTER_INACTIVE -@item active: RTEMS_TIMER_FIRE_AFTER_ACTIVE -@end itemize - -@item TIMER_FIRE_WHEN -@itemize - -@item inactive: TIMER_FIRE_WHEN_INACTIVE -@item active: TIMER_FIRE_WHEN_ACTIVE -@end itemize - -@item TIMER_RESET -@itemize - -@item inactive: TIMER_RESET_INACTIVE -@item active: TIMER_RESET_ACTIVE -@end itemize - -@item TIMER_CANCEL -@itemize - -@item inactive: TIMER_CANCEL_INACTIVE -@item active: TIMER_CANCEL_ACTIVE -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    TIMER_CREATERTEMS_TIMER_CREATE_ONLY
    TIMER_IDENTRTEMS_TIMER_IDENT_ONLY
    TIMER_DELETE
    inactive
    		RTEMS_TIMER_DELETE_INACTIVE
    active
    		RTEMS_TIMER_DELETE_ACTIVE
    TIMER_FIRE_AFTER
    inactive
    		RTEMS_TIMER_FIRE_AFTER_INACTIVE
    active
    		RTEMS_TIMER_FIRE_AFTER_ACTIVE
    TIMER_FIRE_WHEN
    inactive
    		RTEMS_TIMER_FIRE_WHEN_INACTIVE
    active
    		RTEMS_TIMER_FIRE_WHEN_ACTIVE
    TIMER_RESET
    inactive
    		RTEMS_TIMER_RESET_INACTIVE
    active
    		RTEMS_TIMER_RESET_ACTIVE
    TIMER_CANCEL
    inactive
    		RTEMS_TIMER_CANCEL_INACTIVE
    active
    		RTEMS_TIMER_CANCEL_ACTIVE
    -
    -@end html -@end ifset - -@page -@section Semaphore Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{SEMAPHORE\_CREATE}{RTEMS_SEMAPHORE_CREATE_ONLY} -\rtemsonecase{SEMAPHORE\_IDENT}{RTEMS_SEMAPHORE_IDENT_ONLY} -\rtemsonecase{SEMAPHORE\_DELETE}{RTEMS_SEMAPHORE_DELETE_ONLY} -\rtemsdirective{SEMAPHORE\_OBTAIN} -\rtemscase{available}{RTEMS_SEMAPHORE_OBTAIN_AVAILABLE} -\rtemscase{not available -- NO\_WAIT} - {RTEMS_SEMAPHORE_OBTAIN_NOT_AVAILABLE_NO_WAIT} -\rtemscase{not available -- caller blocks} - {RTEMS_SEMAPHORE_OBTAIN_NOT_AVAILABLE_CALLER_BLOCKS} -\rtemsdirective{SEMAPHORE\_RELEASE} -\rtemscase{no waiting tasks}{RTEMS_SEMAPHORE_RELEASE_NO_WAITING_TASKS} -\rtemscase{task readied -- returns to caller} - {RTEMS_SEMAPHORE_RELEASE_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_SEMAPHORE_RELEASE_TASK_READIED_PREEMPTS_CALLER} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item SEMAPHORE_CREATE -@itemize - -@item only case: RTEMS_SEMAPHORE_CREATE_ONLY -@end itemize - -@item SEMAPHORE_IDENT -@itemize - -@item only case: RTEMS_SEMAPHORE_IDENT_ONLY -@end itemize - -@item SEMAPHORE_DELETE -@itemize - -@item only case: RTEMS_SEMAPHORE_DELETE_ONLY -@end itemize - -@item SEMAPHORE_OBTAIN -@itemize - -@item available: RTEMS_SEMAPHORE_OBTAIN_AVAILABLE -@item not available -- NO_WAIT: RTEMS_SEMAPHORE_OBTAIN_NOT_AVAILABLE_NO_WAIT -@item not available -- caller blocks: RTEMS_SEMAPHORE_OBTAIN_NOT_AVAILABLE_CALLER_BLOCKS -@end itemize - -@item SEMAPHORE_RELEASE -@itemize - -@item no waiting tasks: RTEMS_SEMAPHORE_RELEASE_NO_WAITING_TASKS -@item task readied -- returns to caller: RTEMS_SEMAPHORE_RELEASE_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_SEMAPHORE_RELEASE_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - -
    SEMAPHORE_CREATERTEMS_SEMAPHORE_CREATE_ONLY
    SEMAPHORE_IDENTRTEMS_SEMAPHORE_IDENT_ONLY
    SEMAPHORE_DELETERTEMS_SEMAPHORE_DELETE_ONLY
    SEMAPHORE_OBTAIN
    available
    		RTEMS_SEMAPHORE_OBTAIN_AVAILABLE
    not available -- NO_WAIT
    		RTEMS_SEMAPHORE_OBTAIN_NOT_AVAILABLE_NO_WAIT
    not available -- caller blocks
    		RTEMS_SEMAPHORE_OBTAIN_NOT_AVAILABLE_CALLER_BLOCKS
    SEMAPHORE_RELEASE
    no waiting tasks
    		RTEMS_SEMAPHORE_RELEASE_NO_WAITING_TASKS
    task readied -- returns to caller
    		RTEMS_SEMAPHORE_RELEASE_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		RTEMS_SEMAPHORE_RELEASE_TASK_READIED_PREEMPTS_CALLER
    -
    -@end html -@end ifset - -@section Message Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{MESSAGE\_QUEUE\_CREATE}{RTEMS_MESSAGE_QUEUE_CREATE_ONLY} -\rtemsonecase{MESSAGE\_QUEUE\_IDENT}{RTEMS_MESSAGE_QUEUE_IDENT_ONLY} -\rtemsonecase{MESSAGE\_QUEUE\_DELETE}{RTEMS_MESSAGE_QUEUE_DELETE_ONLY} -\rtemsdirective{MESSAGE\_QUEUE\_SEND} -\rtemscase{no waiting tasks} - {RTEMS_MESSAGE_QUEUE_SEND_NO_WAITING_TASKS} -\rtemscase{task readied -- returns to caller} - {RTEMS_MESSAGE_QUEUE_SEND_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_MESSAGE_QUEUE_SEND_TASK_READIED_PREEMPTS_CALLER} -\rtemsdirective{MESSAGE\_QUEUE\_URGENT} -\rtemscase{no waiting tasks}{RTEMS_MESSAGE_QUEUE_URGENT_NO_WAITING_TASKS} -\rtemscase{task readied -- returns to caller} - {RTEMS_MESSAGE_QUEUE_URGENT_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_MESSAGE_QUEUE_URGENT_TASK_READIED_PREEMPTS_CALLER} -\rtemsdirective{MESSAGE\_QUEUE\_BROADCAST} -\rtemscase{no waiting tasks}{RTEMS_MESSAGE_QUEUE_BROADCAST_NO_WAITING_TASKS} -\rtemscase{task readied -- returns to caller} - {RTEMS_MESSAGE_QUEUE_BROADCAST_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_MESSAGE_QUEUE_BROADCAST_TASK_READIED_PREEMPTS_CALLER} -\rtemsdirective{MESSAGE\_QUEUE\_RECEIVE} -\rtemscase{available}{RTEMS_MESSAGE_QUEUE_RECEIVE_AVAILABLE} -\rtemscase{not available -- NO\_WAIT} - {RTEMS_MESSAGE_QUEUE_RECEIVE_NOT_AVAILABLE_NO_WAIT} -\rtemscase{not available -- caller blocks} - {RTEMS_MESSAGE_QUEUE_RECEIVE_NOT_AVAILABLE_CALLER_BLOCKS} -\rtemsdirective{MESSAGE\_QUEUE\_FLUSH} -\rtemscase{no messages flushed}{RTEMS_MESSAGE_QUEUE_FLUSH_NO_MESSAGES_FLUSHED} -\rtemscase{messages flushed}{RTEMS_MESSAGE_QUEUE_FLUSH_MESSAGES_FLUSHED} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item MESSAGE_QUEUE_CREATE -@itemize - -@item only case: RTEMS_MESSAGE_QUEUE_CREATE_ONLY -@end itemize - -@item MESSAGE_QUEUE_IDENT -@itemize - -@item only case: RTEMS_MESSAGE_QUEUE_IDENT_ONLY -@end itemize - -@item MESSAGE_QUEUE_DELETE -@itemize - -@item only case: RTEMS_MESSAGE_QUEUE_DELETE_ONLY -@end itemize - -@item MESSAGE_QUEUE_SEND -@itemize - -@item no waiting tasks: RTEMS_MESSAGE_QUEUE_SEND_NO_WAITING_TASKS -@item task readied -- returns to caller: RTEMS_MESSAGE_QUEUE_SEND_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_MESSAGE_QUEUE_SEND_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@item MESSAGE_QUEUE_URGENT -@itemize - -@item no waiting tasks: RTEMS_MESSAGE_QUEUE_URGENT_NO_WAITING_TASKS -@item task readied -- returns to caller: RTEMS_MESSAGE_QUEUE_URGENT_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_MESSAGE_QUEUE_URGENT_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@item MESSAGE_QUEUE_BROADCAST -@itemize - -@item no waiting tasks: RTEMS_MESSAGE_QUEUE_BROADCAST_NO_WAITING_TASKS -@item task readied -- returns to caller: RTEMS_MESSAGE_QUEUE_BROADCAST_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_MESSAGE_QUEUE_BROADCAST_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@item MESSAGE_QUEUE_RECEIVE -@itemize - -@item available: RTEMS_MESSAGE_QUEUE_RECEIVE_AVAILABLE -@item not available -- NO_WAIT: RTEMS_MESSAGE_QUEUE_RECEIVE_NOT_AVAILABLE_NO_WAIT -@item not available -- caller blocks: RTEMS_MESSAGE_QUEUE_RECEIVE_NOT_AVAILABLE_CALLER_BLOCKS -@end itemize - -@item MESSAGE_QUEUE_FLUSH -@itemize - -@item no messages flushed: RTEMS_MESSAGE_QUEUE_FLUSH_NO_MESSAGES_FLUSHED -@item messages flushed: RTEMS_MESSAGE_QUEUE_FLUSH_MESSAGES_FLUSHED -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    MESSAGE_QUEUE_CREATERTEMS_MESSAGE_QUEUE_CREATE_ONLY
    MESSAGE_QUEUE_IDENTRTEMS_MESSAGE_QUEUE_IDENT_ONLY
    MESSAGE_QUEUE_DELETERTEMS_MESSAGE_QUEUE_DELETE_ONLY
    MESSAGE_QUEUE_SEND
    no waiting tasks
    		RTEMS_MESSAGE_QUEUE_SEND_NO_WAITING_TASKS
    task readied -- returns to caller
    		RTEMS_MESSAGE_QUEUE_SEND_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		RTEMS_MESSAGE_QUEUE_SEND_TASK_READIED_PREEMPTS_CALLER
    MESSAGE_QUEUE_URGENT
    no waiting tasks
    		RTEMS_MESSAGE_QUEUE_URGENT_NO_WAITING_TASKS
    task readied -- returns to caller
    		RTEMS_MESSAGE_QUEUE_URGENT_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		RTEMS_MESSAGE_QUEUE_URGENT_TASK_READIED_PREEMPTS_CALLER
    MESSAGE_QUEUE_BROADCAST
    no waiting tasks
    		RTEMS_MESSAGE_QUEUE_BROADCAST_NO_WAITING_TASKS
    task readied -- returns to caller
    		RTEMS_MESSAGE_QUEUE_BROADCAST_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		RTEMS_MESSAGE_QUEUE_BROADCAST_TASK_READIED_PREEMPTS_CALLER
    MESSAGE_QUEUE_RECEIVE
    available
    		RTEMS_MESSAGE_QUEUE_RECEIVE_AVAILABLE
    not available -- NO_WAIT
    		RTEMS_MESSAGE_QUEUE_RECEIVE_NOT_AVAILABLE_NO_WAIT
    not available -- caller blocks
    		RTEMS_MESSAGE_QUEUE_RECEIVE_NOT_AVAILABLE_CALLER_BLOCKS
    MESSAGE_QUEUE_FLUSH
    no messages flushed
    		RTEMS_MESSAGE_QUEUE_FLUSH_NO_MESSAGES_FLUSHED
    messages flushed
    		RTEMS_MESSAGE_QUEUE_FLUSH_MESSAGES_FLUSHED
    -
    -@end html -@end ifset - -@page -@section Event Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsdirective{EVENT\_SEND} -\rtemscase{no task readied}{RTEMS_EVENT_SEND_NO_TASK_READIED} -\rtemscase{task readied -- returns to caller} - {RTEMS_EVENT_SEND_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_EVENT_SEND_TASK_READIED_PREEMPTS_CALLER} -\rtemsdirective{EVENT\_RECEIVE} -\rtemscase{obtain current events}{RTEMS_EVENT_RECEIVE_OBTAIN_CURRENT_EVENTS} -\rtemscase{available}{RTEMS_EVENT_RECEIVE_AVAILABLE} -\rtemscase{not available -- NO\_WAIT}{RTEMS_EVENT_RECEIVE_NOT_AVAILABLE_NO_WAIT} -\rtemscase{not available -- caller blocks} - {RTEMS_EVENT_RECEIVE_NOT_AVAILABLE_CALLER_BLOCKS} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item EVENT_SEND -@itemize - -@item no task readied: RTEMS_EVENT_SEND_NO_TASK_READIED -@item task readied -- returns to caller: RTEMS_EVENT_SEND_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_EVENT_SEND_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@item EVENT_RECEIVE -@itemize - -@item obtain current events: RTEMS_EVENT_RECEIVE_OBTAIN_CURRENT_EVENTS -@item available: RTEMS_EVENT_RECEIVE_AVAILABLE -@item not available -- NO_WAIT: RTEMS_EVENT_RECEIVE_NOT_AVAILABLE_NO_WAIT -@item not available -- caller blocks: RTEMS_EVENT_RECEIVE_NOT_AVAILABLE_CALLER_BLOCKS -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - -
    EVENT_SEND
    no task readied
    		RTEMS_EVENT_SEND_NO_TASK_READIED
    task readied -- returns to caller
    		RTEMS_EVENT_SEND_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		RTEMS_EVENT_SEND_TASK_READIED_PREEMPTS_CALLER
    EVENT_RECEIVE
    obtain current events
    		RTEMS_EVENT_RECEIVE_OBTAIN_CURRENT_EVENTS
    available
    		RTEMS_EVENT_RECEIVE_AVAILABLE
    not available -- NO_WAIT
    		RTEMS_EVENT_RECEIVE_NOT_AVAILABLE_NO_WAIT
    not available -- caller blocks
    		RTEMS_EVENT_RECEIVE_NOT_AVAILABLE_CALLER_BLOCKS
    -
    -@end html -@end ifset -@section Signal Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{SIGNAL\_CATCH}{RTEMS_SIGNAL_CATCH_ONLY} -\rtemsdirective{SIGNAL\_SEND} -\rtemscase{returns to caller}{RTEMS_SIGNAL_SEND_RETURNS_TO_CALLER} -\rtemscase{signal to self}{RTEMS_SIGNAL_SEND_SIGNAL_TO_SELF} -\rtemsdirective{EXIT ASR OVERHEAD} -\rtemscase{returns to calling task} - {RTEMS_SIGNAL_EXIT_ASR_OVERHEAD_RETURNS_TO_CALLING_TASK} -\rtemscase{returns to preempting task} - {RTEMS_SIGNAL_EXIT_ASR_OVERHEAD_RETURNS_TO_PREEMPTING_TASK} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet -@item SIGNAL_CATCH -@itemize - -@item only case: RTEMS_SIGNAL_CATCH_ONLY -@end itemize - -@item SIGNAL_SEND -@itemize - -@item returns to caller: RTEMS_SIGNAL_SEND_RETURNS_TO_CALLER -@item signal to self: RTEMS_SIGNAL_SEND_SIGNAL_TO_SELF -@end itemize - -@item EXIT ASR OVERHEAD -@itemize - -@item returns to calling task: RTEMS_SIGNAL_EXIT_ASR_OVERHEAD_RETURNS_TO_CALLING_TASK -@item returns to preempting task: RTEMS_SIGNAL_EXIT_ASR_OVERHEAD_RETURNS_TO_PREEMPTING_TASK -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - -
    SIGNAL_CATCHRTEMS_SIGNAL_CATCH_ONLY
    SIGNAL_SEND
    returns to caller
    		RTEMS_SIGNAL_SEND_RETURNS_TO_CALLER
    signal to self
    		RTEMS_SIGNAL_SEND_SIGNAL_TO_SELF
    EXIT ASR OVERHEAD
    returns to calling task
    		 - RTEMS_SIGNAL_EXIT_ASR_OVERHEAD_RETURNS_TO_CALLING_TASK
    returns to preempting task
    		 - RTEMS_SIGNAL_EXIT_ASR_OVERHEAD_RETURNS_TO_PREEMPTING_TASK
    -
    -@end html -@end ifset - -@section Partition Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{PARTITION\_CREATE}{RTEMS_PARTITION_CREATE_ONLY} -\rtemsonecase{PARTITION\_IDENT}{RTEMS_PARTITION_IDENT_ONLY} -\rtemsonecase{PARTITION\_DELETE}{RTEMS_PARTITION_DELETE_ONLY} -\rtemsdirective{PARTITION\_GET\_BUFFER} -\rtemscase{available}{RTEMS_PARTITION_GET_BUFFER_AVAILABLE} -\rtemscase{not available}{RTEMS_PARTITION_GET_BUFFER_NOT_AVAILABLE} -\rtemsonecase{PARTITION\_RETURN\_BUFFER} - {RTEMS_PARTITION_GET_BUFFER_NOT_AVAILABLE} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item PARTITION_CREATE -@itemize - -@item only case: RTEMS_PARTITION_CREATE_ONLY -@end itemize - -@item PARTITION_IDENT -@itemize - -@item only case: RTEMS_PARTITION_IDENT_ONLY -@end itemize - -@item PARTITION_DELETE -@itemize - -@item only case: RTEMS_PARTITION_DELETE_ONLY -@end itemize - -@item PARTITION_GET_BUFFER -@itemize - -@item available: RTEMS_PARTITION_GET_BUFFER_AVAILABLE -@item not available: RTEMS_PARTITION_GET_BUFFER_NOT_AVAILABLE -@end itemize - -@item PARTITION_RETURN_BUFFER -@itemize - -@item only case: RTEMS_PARTITION_RETURN_BUFFER_ONLY -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - -
    PARTITION_CREATERTEMS_PARTITION_CREATE_ONLY
    PARTITION_IDENTRTEMS_PARTITION_IDENT_ONLY
    PARTITION_DELETERTEMS_PARTITION_DELETE_ONLY
    PARTITION_GET_BUFFER
    available
    		RTEMS_PARTITION_GET_BUFFER_AVAILABLE
    not available
    		RTEMS_PARTITION_GET_BUFFER_NOT_AVAILABLE
    PARTITION_RETURN_BUFFERRTEMS_PARTITION_GET_BUFFER_NOT_AVAILABLE
    -
    -@end html -@end ifset - -@page -@section Region Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{REGION\_CREATE}{RTEMS_REGION_CREATE_ONLY} -\rtemsonecase{REGION\_IDENT}{RTEMS_REGION_IDENT_ONLY} -\rtemsonecase{REGION\_DELETE}{RTEMS_REGION_DELETE_ONLY} -\rtemsdirective{REGION\_GET\_SEGMENT} -\rtemscase{available}{RTEMS_REGION_GET_SEGMENT_AVAILABLE} -\rtemscase{not available -- NO\_WAIT} - {RTEMS_REGION_GET_SEGMENT_NOT_AVAILABLE_NO_WAIT} -\rtemscase{not available -- caller blocks} - {RTEMS_REGION_GET_SEGMENT_NOT_AVAILABLE_CALLER_BLOCKS} -\rtemsdirective{REGION\_RETURN\_SEGMENT} -\rtemscase{no waiting tasks}{RTEMS_REGION_RETURN_SEGMENT_NO_WAITING_TASKS} -\rtemscase{task readied -- returns to caller} - {RTEMS_REGION_RETURN_SEGMENT_TASK_READIED_RETURNS_TO_CALLER} -\rtemscase{task readied -- preempts caller} - {RTEMS_REGION_RETURN_SEGMENT_TASK_READIED_PREEMPTS_CALLER} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item REGION_CREATE -@itemize - -@item only case: RTEMS_REGION_CREATE_ONLY -@end itemize - -@item REGION_IDENT -@itemize - -@item only case: RTEMS_REGION_IDENT_ONLY -@end itemize - -@item REGION_DELETE -@itemize - -@item only case: RTEMS_REGION_DELETE_ONLY -@end itemize - -@item REGION_GET_SEGMENT -@itemize - -@item available: RTEMS_REGION_GET_SEGMENT_AVAILABLE -@item not available -- NO_WAIT: RTEMS_REGION_GET_SEGMENT_NOT_AVAILABLE_NO_WAIT -@item not available -- caller blocks: RTEMS_REGION_GET_SEGMENT_NOT_AVAILABLE_CALLER_BLOCKS -@end itemize - -@item REGION_RETURN_SEGMENT -@itemize - -@item no waiting tasks: RTEMS_REGION_RETURN_SEGMENT_NO_WAITING_TASKS -@item task readied -- returns to caller: RTEMS_REGION_RETURN_SEGMENT_TASK_READIED_RETURNS_TO_CALLER -@item task readied -- preempts caller: RTEMS_REGION_RETURN_SEGMENT_TASK_READIED_PREEMPTS_CALLER -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - -
    REGION_CREATERTEMS_REGION_CREATE_ONLY
    REGION_IDENTRTEMS_REGION_IDENT_ONLY
    REGION_DELETERTEMS_REGION_DELETE_ONLY
    REGION_GET_SEGMENT
    available
    		RTEMS_REGION_GET_SEGMENT_AVAILABLE
    not available -- NO_WAIT
    		 - RTEMS_REGION_GET_SEGMENT_NOT_AVAILABLE_NO_WAIT
    not available -- caller blocks
    		 - RTEMS_REGION_GET_SEGMENT_NOT_AVAILABLE_CALLER_BLOCKS
    REGION_RETURN_SEGMENT
    no waiting tasks
    		RTEMS_REGION_RETURN_SEGMENT_NO_WAITING_TASKS
    task readied -- returns to caller
    		 - RTEMS_REGION_RETURN_SEGMENT_TASK_READIED_RETURNS_TO_CALLER
    task readied -- preempts caller
    		 - RTEMS_REGION_RETURN_SEGMENT_TASK_READIED_PREEMPTS_CALLER
    -
    -@end html -@end ifset - -@section Dual-Ported Memory Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{PORT\_CREATE}{RTEMS_PORT_CREATE_ONLY} -\rtemsonecase{PORT\_IDENT}{RTEMS_PORT_IDENT_ONLY} -\rtemsonecase{PORT\_DELETE}{RTEMS_PORT_DELETE_ONLY} -\rtemsonecase{PORT\_INTERNAL\_TO\_EXTERNAL} - {RTEMS_PORT_INTERNAL_TO_EXTERNAL_ONLY} -\rtemsonecase{PORT\_EXTERNAL\_TO\_INTERNAL} - {RTEMS_PORT_EXTERNAL_TO_INTERNAL_ONLY} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item PORT_CREATE -@itemize - -@item only case: RTEMS_PORT_CREATE_ONLY -@end itemize - -@item PORT_IDENT -@itemize - -@item only case: RTEMS_PORT_IDENT_ONLY -@end itemize - -@item PORT_DELETE -@itemize - -@item only case: RTEMS_PORT_DELETE_ONLY -@end itemize - -@item PORT_INTERNAL_TO_EXTERNAL -@itemize - -@item only case: RTEMS_PORT_INTERNAL_TO_EXTERNAL_ONLY -@end itemize - -@item PORT_EXTERNAL_TO_INTERNAL -@itemize - -@item only case: RTEMS_PORT_EXTERNAL_TO_INTERNAL_ONLY -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - -
    PORT_CREATERTEMS_PORT_CREATE_ONLY
    PORT_IDENTRTEMS_PORT_IDENT_ONLY
    PORT_DELETERTEMS_PORT_DELETE_ONLY
    PORT_INTERNAL_TO_EXTERNALRTEMS_PORT_INTERNAL_TO_EXTERNAL_ONLY
    PORT_EXTERNAL_TO_INTERNALRTEMS_PORT_EXTERNAL_TO_INTERNAL_ONLY
    -
    -@end html -@end ifset - -@section I/O Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{IO\_INITIALIZE}{RTEMS_IO_INITIALIZE_ONLY} -\rtemsonecase{IO\_OPEN}{RTEMS_IO_OPEN_ONLY} -\rtemsonecase{IO\_CLOSE}{RTEMS_IO_CLOSE_ONLY} -\rtemsonecase{IO\_READ}{RTEMS_IO_READ_ONLY} -\rtemsonecase{IO\_WRITE}{RTEMS_IO_WRITE_ONLY} -\rtemsonecase{IO\_CONTROL}{RTEMS_IO_CONTROL_ONLY} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item IO_INITIALIZE -@itemize - -@item only case: RTEMS_IO_INITIALIZE_ONLY -@end itemize - -@item IO_OPEN -@itemize - -@item only case: RTEMS_IO_OPEN_ONLY -@end itemize - -@item IO_CLOSE -@itemize - -@item only case: RTEMS_IO_CLOSE_ONLY -@end itemize - -@item IO_READ -@itemize - -@item only case: RTEMS_IO_READ_ONLY -@end itemize - -@item IO_WRITE -@itemize - -@item only case: RTEMS_IO_WRITE_ONLY -@end itemize - -@item IO_CONTROL -@itemize - -@item only case: RTEMS_IO_CONTROL_ONLY -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - -
    IO_INITIALIZERTEMS_IO_INITIALIZE_ONLY
    IO_OPENRTEMS_IO_OPEN_ONLY
    IO_CLOSERTEMS_IO_CLOSE_ONLY
    IO_READRTEMS_IO_READ_ONLY
    IO_WRITERTEMS_IO_WRITE_ONLY
    IO_CONTROLRTEMS_IO_CONTROL_ONLY
    -
    -@end html -@end ifset - -@section Rate Monotonic Manager - -@ifset use-tex -@tex -\centerline{\vbox{\offinterlineskip\halign{ -\span\rtemstimetable -\rtemsonecase{RATE\_MONOTONIC\_CREATE}{RTEMS_RATE_MONOTONIC_CREATE_ONLY} -\rtemsonecase{RATE\_MONOTONIC\_IDENT}{RTEMS_RATE_MONOTONIC_IDENT_ONLY} -\rtemsonecase{RATE\_MONOTONIC\_CANCEL}{RTEMS_RATE_MONOTONIC_CANCEL_ONLY} -\rtemsdirective{RATE\_MONOTONIC\_DELETE} -\rtemscase{active}{RTEMS_RATE_MONOTONIC_DELETE_ACTIVE} -\rtemscase{inactive}{RTEMS_RATE_MONOTONIC_DELETE_INACTIVE} -\rtemsdirective{RATE\_MONOTONIC\_PERIOD} -\rtemscase{initiate period -- returns to caller} - {RTEMS_RATE_MONOTONIC_PERIOD_INITIATE_PERIOD_RETURNS_TO_CALLER} -\rtemscase{conclude period -- caller blocks} - {RTEMS_RATE_MONOTONIC_PERIOD_CONCLUDE_PERIOD_CALLER_BLOCKS} -\rtemscase{obtain status}{RTEMS_RATE_MONOTONIC_PERIOD_OBTAIN_STATUS} -\rtemsendtimetable -}}\hfil} -@end tex -@end ifset - -@ifset use-ascii -@ifinfo -@itemize @bullet - -@item RATE_MONOTONIC_CREATE -@itemize - -@item only case: RTEMS_RATE_MONOTONIC_CREATE_ONLY -@end itemize - -@item RATE_MONOTONIC_IDENT -@itemize - -@item only case: RTEMS_RATE_MONOTONIC_IDENT_ONLY -@end itemize - -@item RATE_MONOTONIC_CANCEL -@itemize - -@item only case: RTEMS_RATE_MONOTONIC_CANCEL_ONLY -@end itemize - -@item RATE_MONOTONIC_DELETE -@itemize - -@item active: RTEMS_RATE_MONOTONIC_DELETE_ACTIVE -@item inactive: RTEMS_RATE_MONOTONIC_DELETE_INACTIVE -@end itemize - -@item RATE_MONOTONIC_PERIOD -@itemize - -@item initiate period -- returns to caller: RTEMS_RATE_MONOTONIC_PERIOD_INITIATE_PERIOD_RETURNS_TO_CALLER -@item conclude period -- caller blocks: RTEMS_RATE_MONOTONIC_PERIOD_CONCLUDE_PERIOD_CALLER_BLOCKS -@item obtain status: RTEMS_RATE_MONOTONIC_PERIOD_OBTAIN_STATUS -@end itemize - -@end itemize -@end ifinfo -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - -
    RATE_MONOTONIC_CREATERTEMS_RATE_MONOTONIC_CREATE_ONLY
    RATE_MONOTONIC_IDENTRTEMS_RATE_MONOTONIC_IDENT_ONLY
    RATE_MONOTONIC_CANCELRTEMS_RATE_MONOTONIC_CANCEL_ONLY
    RATE_MONOTONIC_DELETE
    active
    		RTEMS_RATE_MONOTONIC_DELETE_ACTIVE
    inactive
    		RTEMS_RATE_MONOTONIC_DELETE_INACTIVE
    RATE_MONOTONIC_PERIOD
    initiate period -- returns to caller
    		 - RTEMS_RATE_MONOTONIC_PERIOD_INITIATE_PERIOD_RETURNS_TO_CALLER
    conclude period -- caller blocks
    		 - RTEMS_RATE_MONOTONIC_PERIOD_CONCLUDE_PERIOD_CALLER_BLOCKS
    obtain status
    		RTEMS_RATE_MONOTONIC_PERIOD_OBTAIN_STATUS
    -
    -@end html -@end ifset - -@tex -\global\advance \smallskipamount by 4pt -@end tex diff --git a/doc/common/timing.t b/doc/common/timing.t deleted file mode 100644 index 5e717e87de..0000000000 --- a/doc/common/timing.t +++ /dev/null @@ -1,396 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Timing Specification - -@section Introduction - -This chapter provides information pertaining to the -measurement of the performance of RTEMS, the methods of -gathering the timing data, and the usefulness of the data. Also -discussed are other time critical aspects of RTEMS that affect -an applications design and ultimate throughput. These aspects -include determinancy, interrupt latency and context switch times. - -@section Philosophy - -Benchmarks are commonly used to evaluate the -performance of software and hardware. Benchmarks can be an -effective tool when comparing systems. Unfortunately, -benchmarks can also be manipulated to justify virtually any -claim. Benchmarks of real-time executives are difficult to -evaluate for a variety of reasons. Executives vary in the -robustness of features and options provided. Even when -executives compare favorably in functionality, it is quite -likely that different methodologies were used to obtain the -timing data. Another problem is that some executives provide -times for only a small subset of directives, This is typically -justified by claiming that these are the only time-critical -directives. The performance of some executives is also very -sensitive to the number of objects in the system. To obtain any -measure of usefulness, the performance information provided for -an executive should address each of these issues. - -When evaluating the performance of a real-time -executive, one typically considers the following areas: -determinancy, directive times, worst case interrupt latency, and -context switch time. Unfortunately, these areas do not have -standard measurement methodologies. This allows vendors to -manipulate the results such that their product is favorably -represented. We have attempted to provide useful and meaningful -timing information for RTEMS. To insure the usefulness of our -data, the methodology and definitions used to obtain and -describe the data are also documented. - -@subsection Determinancy - -The correctness of data in a real-time system must -always be judged by its timeliness. In many real-time systems, -obtaining the correct answer does not necessarily solve the -problem. For example, in a nuclear reactor it is not enough to -determine that the core is overheating. This situation must be -detected and acknowledged early enough that corrective action -can be taken and a meltdown avoided. - -Consequently, a system designer must be able to -predict the worst-case behavior of the application running under -the selected executive. In this light, it is important that a -real-time system perform consistently regardless of the number -of tasks, semaphores, or other resources allocated. An -important design goal of a real-time executive is that all -internal algorithms be fixed-cost. Unfortunately, this goal is -difficult to completely meet without sacrificing the robustness -of the executive's feature set. - -Many executives use the term deterministic to mean -that the execution times of their services can be predicted. -However, they often provide formulas to modify execution times -based upon the number of objects in the system. This usage is -in sharp contrast to the notion of deterministic meaning fixed -cost. - -Almost all RTEMS directives execute in a fixed amount -of time regardless of the number of objects present in the -system. The primary exception occurs when a task blocks while -acquiring a resource and specifies a non-zero timeout interval. - -Other exceptions are message queue broadcast, -obtaining a variable length memory block, object name to ID -translation, and deleting a resource upon which tasks are -waiting. In addition, the time required to service a clock tick -interrupt is based upon the number of timeouts and other -"events" which must be processed at that tick. This second -group is composed primarily of capabilities which are inherently -non-deterministic but are infrequently used in time critical -situations. The major exception is that of servicing a clock -tick. However, most applications have a very small number of -timeouts which expire at exactly the same millisecond (usually -none, but occasionally two or three). - -@subsection Interrupt Latency - -Interrupt latency is the delay between the CPU's -receipt of an interrupt request and the execution of the first -application-specific instruction in an interrupt service -routine. Interrupts are a critical component of most real-time -applications and it is critical that they be acted upon as -quickly as possible. - -Knowledge of the worst case interrupt latency of an -executive aids the application designer in determining the -maximum period of time between the generation of an interrupt -and an interrupt handler responding to that interrupt. The -interrupt latency of an system is the greater of the executive's -and the applications's interrupt latency. If the application -disables interrupts longer than the executive, then the -application's interrupt latency is the system's worst case -interrupt disable period. - -The worst case interrupt latency for a real-time -executive is based upon the following components: - -@itemize @bullet -@item the longest period of time interrupts are disabled -by the executive, - -@item the overhead required by the executive at the -beginning of each ISR, - -@item the time required for the CPU to vector the -interrupt, and - -@item for some microprocessors, the length of the longest -instruction. -@end itemize - -The first component is irrelevant if an interrupt -occurs when interrupts are enabled, although it must be included -in a worst case analysis. The third and fourth components are -particular to a CPU implementation and are not dependent on the -executive. The fourth component is ignored by this document -because most applications use only a subset of a -microprocessor's instruction set. Because of this the longest -instruction actually executed is application dependent. The -worst case interrupt latency of an executive is typically -defined as the sum of components (1) and (2). The second -component includes the time necessry for RTEMS to save registers -and vector to the user-defined handler. RTEMS includes the -third component, the time required for the CPU to vector the -interrupt, because it is a required part of any interrupt. - -Many executives report the maximum interrupt disable -period as their interrupt latency and ignore the other -components. This results in very low worst-case interrupt -latency times which are not indicative of actual application -performance. The definition used by RTEMS results in a higher -interrupt latency being reported, but accurately reflects the -longest delay between the CPU's receipt of an interrupt request -and the execution of the first application-specific instruction -in an interrupt service routine. - -The actual interrupt latency times are reported in -the Timing Data chapter of this supplement. - -@subsection Context Switch Time - -An RTEMS context switch is defined as the act of -taking the CPU from the currently executing task and giving it -to another task. This process involves the following components: - -@itemize @bullet -@item Saving the hardware state of the current task. - -@item Optionally, invoking the TASK_SWITCH user extension. - -@item Restoring the hardware state of the new task. -@end itemize - -RTEMS defines the hardware state of a task to include -the CPU's data registers, address registers, and, optionally, -floating point registers. - -Context switch time is often touted as a performance -measure of real-time executives. However, a context switch is -performed as part of a directive's actions and should be viewed -as such when designing an application. For example, if a task -is unable to acquire a semaphore and blocks, a context switch is -required to transfer control from the blocking task to a new -task. From the application's perspective, the context switch is -a direct result of not acquiring the semaphore. In this light, -the context switch time is no more relevant than the performance -of any other of the executive's subroutines which are not -directly accessible by the application. - -In spite of the inappropriateness of using the -context switch time as a performance metric, RTEMS context -switch times for floating point and non-floating points tasks -are provided for comparison purposes. Of the executives which -actually support floating point operations, many do not report -context switch times for floating point context switch time. -This results in a reported context switch time which is -meaningless for an application with floating point tasks. - -The actual context switch times are reported in the -Timing Data chapter of this supplement. - -@subsection Directive Times - -Directives are the application's interface to the -executive, and as such their execution times are critical in -determining the performance of the application. For example, an -application using a semaphore to protect a critical data -structure should be aware of the time required to acquire and -release a semaphore. In addition, the application designer can -utilize the directive execution times to evaluate the -performance of different synchronization and communication -mechanisms. - -The actual directive execution times are reported in -the Timing Data chapter of this supplement. - -@section Methodology - -@subsection Software Platform - -The RTEMS timing suite is written in C. The overhead -of passing arguments to RTEMS by C is not timed. The times -reported represent the amount of time from entering to exiting -RTEMS. - -The tests are based upon one of two execution models: -(1) single invocation times, and (2) average times of repeated -invocations. Single invocation times are provided for -directives which cannot easily be invoked multiple times in the -same scenario. For example, the times reported for entering and -exiting an interrupt service routine are single invocation -times. The second model is used for directives which can easily -be invoked multiple times in the same scenario. For example, -the times reported for semaphore obtain and semaphore release -are averages of multiple invocations. At least 100 invocations -are used to obtain the average. - -@subsection Hardware Platform - -Since RTEMS supports a variety of processors, the -hardware platform used to gather the benchmark times must also -vary. Therefore, for each processor supported the hardware -platform must be defined. Each definition will include a brief -description of the target hardware platform including the clock -speed, memory wait states encountered, and any other pertinent -information. This definition may be found in the processor -dependent timing data chapter within this supplement. - -@subsection What is measured? - -An effort was made to provide execution times for a -large portion of RTEMS. Times were provided for most directives -regardless of whether or not they are typically used in time -critical code. For example, execution times are provided for -all object create and delete directives, even though these are -typically part of application initialization. - -The times include all RTEMS actions necessary in a -particular scenario. For example, all times for blocking -directives include the context switch necessary to transfer -control to a new task. Under no circumstances is it necessary -to add context switch time to the reported times. - -The following list describes the objects created by -the timing suite: - -@itemize @bullet -@item All tasks are non-floating point. - -@item All tasks are created as local objects. - -@item No timeouts are used on blocking directives. - -@item All tasks wait for objects in FIFO order. - -@end itemize - -In addition, no user extensions are configured. - -@subsection What is not measured? - -The times presented in this document are not intended -to represent best or worst case times, nor are all directives -included. For example, no times are provided for the initialize -executive and fatal_error_occurred directives. Other than the -exceptions detailed in the Determinancy section, all directives -will execute in the fixed length of time given. - -Other than entering and exiting an interrupt service -routine, all directives were executed from tasks and not from -interrupt service routines. Directives invoked from ISRs, when -allowable, will execute in slightly less time than when invoked -from a task because rescheduling is delayed until the interrupt -exits. - -@subsection Terminology - -The following is a list of phrases which are used to -distinguish individual execution paths of the directives taken -during the RTEMS performance analysis: - -@table @b -@item another task -The directive was performed -on a task other than the calling task. - -@item available -A task attempted to obtain a resource and -immediately acquired it. - -@item blocked task -The task operated upon by the -directive was blocked waiting for a resource. - -@item caller blocks -The requested resoure was not -immediately available and the calling task chose to wait. - -@item calling task -The task invoking the directive. - -@item messages flushed -One or more messages was flushed -from the message queue. - -@item no messages flushed -No messages were flushed from -the message queue. - -@item not available -A task attempted to obtain a resource -and could not immediately acquire it. - -@item no reschedule -The directive did not require a -rescheduling operation. - -@item NO_WAIT -A resource was not available and the -calling task chose to return immediately via the NO_WAIT option -with an error. - -@item obtain current -The current value of something was -requested by the calling task. - -@item preempts caller -The release of a resource caused a -task of higher priority than the calling to be readied and it -became the executing task. - -@item ready task -The task operated upon by the directive -was in the ready state. - -@item reschedule -The actions of the directive -necessitated a rescheduling operation. - -@item returns to caller -The directive succeeded and -immediately returned to the calling task. - -@item returns to interrupted task -The instructions -executed immediately following this interrupt will be in the -interrupted task. - -@item returns to nested interrupt -The instructions -executed immediately following this interrupt will be in a -previously interrupted ISR. - -@item returns to preempting task -The instructions -executed immediately following this interrupt or signal handler -will be in a task other than the interrupted task. - -@item signal to self -The signal set was sent to the -calling task and signal processing was enabled. - -@item suspended task -The task operated upon by the -directive was in the suspended state. - -@item task readied -The release of a resource caused a -task of lower or equal priority to be readied and the calling -task remained the executing task. - -@item yield -The act of attempting to voluntarily release -the CPU. - -@end table - diff --git a/doc/common/treedef.tex b/doc/common/treedef.tex deleted file mode 100644 index 26eda0c28c..0000000000 --- a/doc/common/treedef.tex +++ /dev/null @@ -1,317 +0,0 @@ -% treedef.tex -% -% These definitions for tree macros are taken from "Trees in TeX", -% by David Eppstein, as published in TUGboat 6#1, March 1985. -% David Eppstein's address (as of 15 June 1988) is -% Computer Science Department -% Columbia University -% New York, NY 10027 -% Eppstein@cs.Columbia.edu -% -% Tree -- a macro to make aligned (horizontal) trees in TeX -% -% Input is of the form -% \tree -% item -% \subtree -% \leaf{item} -% . -% . -% . -% \endsubtree -% \subtree -% . -% . -% . -% \endsubtree -% \endsubtree -% \endtree -% -% Nesting is to any level. \leaf is defined as a subtree of one item: -% \def\leaf#1{\subtree#1\endsubtree}. -% -% A structure: -% \subtree -% item_part1 -% item_part2 -% . -% . -% . -% -% will print item_part2 directly below item_part1 as a single item -% as if they were in a \box. -% -% The macro is a 3-pass macro. On the first pass it sets up a data -% structure from the \subtree ... \endsubtree definitions. On the second pass -% it recursively calculates the width of each level of the tree. On the third -% pass it sets up the boxes, glue and rules. -% -% By David Eppstein, TUGboat, vol. 6 (1985), no. 1, pp. 31--35. -% Transcribed by Margaret Kromer (peg), Feb., 1986. -% -% Pass 1 -% At the end of pass 1, the tree is coded as a nested collection of \hboxes -% and \vboxes. -\newbox\treebox\newcount\treeboxcnt -\def\tree{\message{Begin tree}\treeboxcnt=1\global\setbox\treebox=\boxtree} -\def\subtree{\ettext \advance\treeboxcnt by 1 \boxtree} -\def\leaf#1{\subtree#1\endsubtree} -\def\endsubtree{\ettext \egroup \advance\treeboxcnt-1{}% - \ifnum\treeboxcnt=-1 \treeerrora\fi} -\def\endtree{\endsubtree \ifnum\treeboxcnt>0 \treeerrorb\fi% - \settreesizes \typesettree \message{-- end tree}} -% Error messages for unbalanced tree -\def\treeerrora{\errhelp=\treeerrorahelp% - \errmessage{Unbalanced tree -- too many endsubtrees}} -\newhelp\treeerrorahelp{There are more subtrees closed than opened} -\def\treeerrorb{\errhelp=\treeerrorbhelp% - \errmessage{Unbalanced tree -- not enough endsubtrees}} -\newhelp\treeerrorbhelp{Not all the subtrees of the tree are closed. -If you continue, you'll get some mysterious secondary errors.} -% Set up \vbox containing root of tree -\newif\iftreetext\treetextfalse % Whether still aligning text -\def\boxtree{\hbox\bgroup % Start outer box of tree or subtree - \baselineskip 2.5ex % Narrow line spacing slightly - \tabskip 0pt % No spurious glue in alignment - \vbox\bgroup % Start inner text \vbox - \treetexttrue % Remember for \ettext - \let\par\crcr \obeylines % New line breaks without explicit \cr - \halign\bgroup##\hfil\cr} % Start alignment with simple template -\def\ettext{\iftreetext % Are we still in inner text \vbox? - \crcr\egroup \egroup \fi} % Yes, end alignment and box -% Pass 2 -% Recursively calculate widths of tree with \setsizes; keep results in -% \treesizes; \treewidth contains total width calculated so far. \treeworkbox -% is workspace containing subtree being sized. -\newbox\treeworkbox -\def\cons#1#2{\edef#2{\xmark #1#2}} % Add something to start of list -\def\car#1{\expandafter\docar#1\docar} % Take first element of list -\def\docar\xmark#1\xmark#2\docar{#1} % ..by ignoring rest in expansion -\def\cdr#1{\expandafter\docdr#1\docdr#1}% Similarly, drop first element -\def\docdr\xmark#1\xmark#2\docdr#3{\def#3{\xmark #2}} -\def\xmark{\noexpand\xmark} % List separator expands to self -\def\nil{\xmark} % Empty list is just separator -\def\settreesizes{\setbox\treeworkbox=\copy\treebox% - \global\let\treesizes\nil \setsizes} -\newdimen\treewidth % Width of this part of the tree -\def\setsizes{\setbox\treeworkbox=\hbox\bgroup% Get a horiz list as a workspace - \unhbox\treeworkbox\unskip % Take tree, unpack it into horiz list - \inittreewidth % Get old width at this level - \sizesubtrees % Recurse through all subtrees - \sizelevel % Now set width from remaining \vbox - \egroup} % All done, finish our \hbox -\def\inittreewidth{\ifx\treesizes\nil % If this is the first at this level - \treewidth=0pt % ..then we have no previous max width - \else \treewidth=\car\treesizes % Otherwise take old max level width - \global\cdr\treesizes % ..and advance level width storage - \fi} % ..in preparation for next level. -\def\sizesubtrees{\loop % For each box in horiz list (subtree) - \setbox\treeworkbox=\lastbox \unskip % ..pull it off list and flush glue - \ifhbox\treeworkbox \setsizes % If hbox, it's a subtree - recurse - \repeat} % ..and loop; end loop on tree text -\def\sizelevel{% - \ifdim\treewidth<\wd\treeworkbox % If greater than previous maximum - \treewidth=\wd\treeworkbox \fi % Then set max to new high - \global\cons{\the\treewidth}\treesizes}% In either case, put back on list -% Pass 3 -% Recursively typeset tree with \maketree by adding an \hbox containing -% a subtree (in \treebox) to the horizontal list. -\newdimen\treeheight % Height of this part of the tree -\newif\ifleaf % Tree has no subtrees (is a leaf) -\newif\ifbotsub % Bottom subtree of parent -\newif\iftopsub % Top subtree of parent -\def\typesettree{\medskip\maketree\medskip} % Make whole tree -\def\maketree{\hbox{\treewidth=\car\treesizes % Get width at this level - \cdr\treesizes % Set up width list for recursion - \makesubtreebox\unskip % Set \treebox to text, make subtrees - \ifleaf \makeleaf % No subtrees, add glue - \else \makeparent \fi}} % Have subtrees, stick them at right -{\catcode`@=11 % Be able to use \voidb@x -\gdef\makesubtreebox{\unhbox\treebox % Open up tree or subtree - \unskip\global\setbox\treebox\lastbox % Pick up very last box - \ifvbox\treebox % If we're already at the \vbox - \global\leaftrue \let\next\relax % ..then this is a leaf - \else \botsubtrue % Otherwise, we have subtrees - \setbox\treeworkbox\box\voidb@x % Init stack of processed subs - \botsubtrue \let\next\makesubtree % ..and call \maketree on them - \fi \next}} % Finish up for whichever it was -\def\makesubtree{\setbox1\maketree % Call \maketree on this subtree - \unskip\global\setbox\treebox\lastbox % Pick up box before it - \treeheight=\ht1 % Get height of subtree we made - \advance\treeheight 2ex % Add some room around the edges - \ifhbox\treebox \topsubfalse % If picked up box is a \vbox, - \else \topsubtrue \fi % ..this is the top, otherwise not - \addsubtreebox % Stack subtree with the rest - \iftopsub \global\leaffalse % If top, remember not a leaf - \let\next\relax \else % ..(after recursion), set return - \botsubfalse \let\next\makesubtree % Otherwise, we have more subtrees - \fi \next} % Do tail recursion or return -\def\addsubtreebox{\setbox\treeworkbox=\vbox{\subtreebox\unvbox\treeworkbox}} -\def\subtreebox{\hbox\bgroup % Start \hbox of tree and lines - \vbox to \treeheight\bgroup % Start \vbox for vertical rules - \ifbotsub \iftopsub \vfil % If both bottom and top subtree - \hrule width 0.4pt % ..vertical rule is just a dot - \else \treehalfrule \fi \vfil % Bottom gets half-height rule - \else \iftopsub \vfil \treehalfrule % Top gets half-height the other way - \else \hrule width 0.4pt height \treeheight \fi\fi % Middle, full height - \egroup % Finish vertical rule \vbox - \treectrbox{\hrule width 1em}\hskip 0.2em\treectrbox{\box1}\egroup} -\def\treectrbox#1{\vbox to \treeheight{\vfil #1\vfil}} -\def\treehalfrule{\dimen\treeworkbox=\treeheight % Get total height - \divide\dimen\treeworkbox 2% - \advance\dimen\treeworkbox 0.2pt % Divide by two, add half horiz height - \hrule width 0.4pt height \dimen\treeworkbox}% Make a vertical rule that high -\def\makeleaf{\box\treebox} % Add leaf box to horiz list -\def\makeparent{\ifdim\ht\treebox>% - \ht\treeworkbox % If text is higher than subtrees - \treeheight=\ht\treebox % ..use that height - \else \treeheight=\ht\treeworkbox \fi % Otherwise use height of subtrees - \advance\treewidth-\wd\treebox % Take remainder of level width - \advance\treewidth 1em % ..after accounting for text and glue - \treectrbox{\box\treebox}\hskip 0.2em % Add text, space before connection -\treectrbox{\hrule width \treewidth}% - \treectrbox{\box\treeworkbox}} % Add \hrule, subs - -************************************************ -% Plain TeX driver for tree.tex - -\def\uncatcodespecials{\catcode`@=12\def\do##1{\catcode`##1=12}\dospecials} -\def\setupverbatim{\tt\obeylines\uncatcodespecials\obeyspaces} -{\obeyspaces\global\let =\ } -\def\beginshowoff{\par\begingroup\setupverbatim\doverbatim} -{\catcode`\!=0 \catcode`\\=12 -!obeylines!gdef!doverbatim^^M#1\endshowoff{#1!endgroup!medbreak!filbreak% -!smallskip}} - -% see The TeXbook, exercise 22.14 -%\input tree.tex -\centerline{\bf TREE TREE} -\bigskip -\tree - {Tree} - Uses - \subtree - Computer - Science - \subtree - Data - Structures - \leaf{Search Tree} - \leaf{Priority Queue} - \endsubtree - \subtree - Parsing - \leaf{Parse Tree} - \leaf{Symbol Table} - \endsubtree - \subtree - Structured - Programming - \endsubtree - \endsubtree - \subtree - Genealogy - \leaf{Ancestors} - \leaf{Descendants} - \endsubtree - \subtree - Electrical - Engineering - \subtree - Paper - \leaf{{\it Vitae}} - \leaf{Announcements} - \leaf{Proposals} - \leaf{\TeX{} Samples} - \endsubtree - \endsubtree - \subtree - Construction - \leaf{Fences} - \subtree - Buildings - \subtree - Houses - \leaf{Human} - \leaf{Dog} - \leaf{Bird} - \leaf{Tree} - \endsubtree - \leaf{Barns} - \leaf{Other} - \endsubtree - \leaf{\dots} - \endsubtree - \subtree - Taxonomies - \leaf{Tree Uses} - \endsubtree -\endtree - -\vskip.5truein -\beginshowoff -% see The TeXbook, exercise 22.14 -\input tree.tex -\centerline{TREE TREE} -\bigskip -\tree - Tree - Uses - \subtree - Computer - Science - \subtree - Data - Structures - \leaf{Search Tree} - \leaf{Priority Queue} - \endsubtree - \subtree - Parsing - \leaf{Parse Tree} - \leaf{Symbol Table} - \endsubtree - \subtree - Structured - Programming - \endsubtree - \endsubtree - \subtree - Genealogy - \leaf{Ancestors} - \leaf{Descendants} - \endsubtree - \subtree - Electrical - Engineering - \subtree - Paper - \leaf{{\it Vitae}} - \leaf{Announcements} - \leaf{Proposals} - \leaf{\TeX{} Samples} - \endsubtree - \endsubtree - \subtree - Construction - \leaf{Fences} - \subtree - Buildings - \subtree - Houses - \leaf{Human} - \leaf{Dog} - \leaf{Bird} - \leaf{Tree} - \endsubtree - \leaf{Barns} - \leaf{Other} - \endsubtree - \leaf{\dots} - \endsubtree - \subtree - Taxonomies - \leaf{Tree Uses} - \endsubtree -\endtree -\endshowoff diff --git a/doc/common/up-arrow.gif b/doc/common/up-arrow.gif deleted file mode 100644 index 82aa8ccc68..0000000000 Binary files a/doc/common/up-arrow.gif and /dev/null differ diff --git a/doc/common/wksheets.t b/doc/common/wksheets.t deleted file mode 100644 index 7cfe61a40a..0000000000 --- a/doc/common/wksheets.t +++ /dev/null @@ -1,409 +0,0 @@ -@c ****** This comment is here to remind you not to edit the wksheets.t -@c ****** in any directory but common. -@c -@c Figures ... -@c RTEMS RAM Workspace Worksheet -@c RTEMS Code Space Worksheet -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Memory Requirements - -@section Introduction - -Memory is typically a limited resource in real-time -embedded systems, therefore, RTEMS can be configured to utilize -the minimum amount of memory while meeting all of the -applications requirements. Worksheets are provided which allow -the RTEMS application developer to determine the amount of RTEMS -code and RAM workspace which is required by the particular -configuration. Also provided are the minimum code space, -maximum code space, and the constant data space required by -RTEMS. - -@section Data Space Requirements - -RTEMS requires a small amount of memory for its -private variables. This data area must be in RAM and is -separate from the RTEMS RAM Workspace. The following -illustrates the data space required for all configurations of -RTEMS: - -@itemize @bullet -@item Data Space: RTEMS_DATA_SPACE -@end itemize - -@section Minimum and Maximum Code Space Requirements - -A maximum configuration of RTEMS includes the core -and all managers, including the multiprocessing manager. -Conversely, a minimum configuration of RTEMS includes only the -core and the following managers: initialization, task, interrupt -and fatal error. The following illustrates the code space -required by these configurations of RTEMS: - -@itemize @bullet -@item Minimum Configuration: RTEMS_MINIMUM_CONFIGURATION -@item Maximum Configuration: RTEMS_MAXIMUM_CONFIGURATION -@end itemize - -@section RTEMS Code Space Worksheet - -The RTEMS Code Space Worksheet is a tool provided to -aid the RTEMS application designer to accurately calculate the -memory required by the RTEMS run-time environment. RTEMS allows -the custom configuration of the executive by optionally -excluding managers which are not required by a particular -application. This worksheet provides the included and excluded -size of each manager in tabular form allowing for the quick -calculation of any custom configuration of RTEMS. The RTEMS -Code Space Worksheet is below: - -@ifset use-ascii -@page -@end ifset -@ifset use-tex -@page -@end ifset - -@page -@center @b{RTEMS Code Space Worksheet} -@sp 1 - -@ifset use-ascii - -The following is a list of the components of the RTEMS code space. The first -number in parentheses is the size when the component is included, -while the second number indicates its size when not included. If the second -number is "NA", then the component must always be included. - -@itemize @bullet -@item Core (RTEMS_CORE_CODE_SIZE, NA) -@item Initialization (RTEMS_INITIALIZATION_CODE_SIZE, NA) -@item Task (RTEMS_TASK_CODE_SIZE, NA) -@item Interrupt (RTEMS_INTERRUPT_CODE_SIZE, NA) -@item Clock (RTEMS_CLOCK_CODE_SIZE, NA) -@item Timer (RTEMS_TIMER_CODE_SIZE, RTEMS_TIMER_CODE_OPTSIZE) -@item Semaphore (RTEMS_SEMAPHORE_CODE_SIZE, RTEMS_SEMAPHORE_CODE_OPTSIZE) -@item Message (RTEMS_MESSAGE_CODE_SIZE, RTEMS_MESSAGE_CODE_OPTSIZE) -@item Event (RTEMS_EVENT_CODE_SIZE, RTEMS_EVENT_CODE_OPTSIZE) -@item Signal (RTEMS_SIGNAL_CODE_SIZE, RTEMS_SIGNAL_CODE_OPTSIZE) -@item Partition (RTEMS_PARTITION_CODE_SIZE, RTEMS_PARTITION_CODE_OPTSIZE) -@item Region (RTEMS_REGION_CODE_SIZE, RTEMS_REGION_CODE_OPTSIZE) -@item Dual Ported Memory (RTEMS_DPMEM_CODE_SIZE, RTEMS_DPMEM_CODE_OPTSIZE) -@item I/O (RTEMS_IO_CODE_SIZE, RTEMS_IO_CODE_OPTSIZE) -@item Fatal Error (RTEMS_FATAL_ERROR_CODE_SIZE, NA) -@item Rate Monotonic (RTEMS_RATE_MONOTONIC_CODE_SIZE, RTEMS_RATE_MONOTONIC_CODE_OPTSIZE) -@item Multiprocessing (RTEMS_MULTIPROCESSING_CODE_SIZE, RTEMS_MULTIPROCESSING_CODE_OPTSIZE) -@end itemize -@end ifset - -@ifset use-tex - -@tex -\line{\hskip 0.50in\vbox{\offinterlineskip\halign{ -\vrule\strut#& -\hbox to 2.25in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 1.00in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 1.00in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 1.25in{\enskip\hfil#\hfil}& -\vrule#\cr -\noalign{\hrule} -&\bf Component && \bf Included && \bf Not Included && \bf Size &\cr\noalign{\hrule} -&Core && RTEMS_CORE_CODE_SIZE && NA && &\cr\noalign{\hrule} -&Initialization && RTEMS_INITIALIZATION_CODE_SIZE && NA && &\cr\noalign{\hrule} -&Task && RTEMS_TASK_CODE_SIZE && NA && &\cr\noalign{\hrule} -&Interrupt && RTEMS_INTERRUPT_CODE_SIZE && NA && &\cr\noalign{\hrule} -&Clock && RTEMS_CLOCK_CODE_SIZE && NA && &\cr\noalign{\hrule} -&Timer && RTEMS_TIMER_CODE_SIZE && RTEMS_TIMER_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Semaphore && RTEMS_SEMAPHORE_CODE_SIZE && RTEMS_SEMAPHORE_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Message && RTEMS_MESSAGE_CODE_SIZE && RTEMS_MESSAGE_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Event && RTEMS_EVENT_CODE_SIZE && RTEMS_EVENT_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Signal && RTEMS_SIGNAL_CODE_SIZE && RTEMS_SIGNAL_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Partition && RTEMS_PARTITION_CODE_SIZE && RTEMS_PARTITION_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Region && RTEMS_REGION_CODE_SIZE && RTEMS_REGION_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Dual Ported Memory && RTEMS_DPMEM_CODE_SIZE && RTEMS_DPMEM_CODE_OPTSIZE && &\cr\noalign{\hrule} -&I/O && RTEMS_IO_CODE_SIZE && RTEMS_IO_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Fatal Error && RTEMS_FATAL_ERROR_CODE_SIZE && NA && &\cr\noalign{\hrule} -&Rate Monotonic && RTEMS_RATE_MONOTONIC_CODE_SIZE && RTEMS_RATE_MONOTONIC_CODE_OPTSIZE && &\cr\noalign{\hrule} -&Multiprocessing && RTEMS_MULTIPROCESSING_CODE_SIZE && RTEMS_MULTIPROCESSING_CODE_OPTSIZE && &\cr\noalign{\hrule} -&\multispan 5 \bf\hfil Total Code Space Requirements\qquad\hfil&&&\cr\noalign{\hrule} -}}\hfil} -@end tex -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ComponentIncludedNot IncludedSize
    CoreRTEMS_CORE_CODE_SIZENA
    InitializationRTEMS_INITIALIZATION_CODE_SIZENA
    TaskRTEMS_TASK_CODE_SIZENA
    InterruptRTEMS_INTERRUPT_CODE_SIZENA
    ClockRTEMS_CLOCK_CODE_SIZENA
    TimerRTEMS_TIMER_CODE_SIZERTEMS_TIMER_CODE_OPTSIZE
    SemaphoreRTEMS_SEMAPHORE_CODE_SIZERTEMS_SEMAPHORE_CODE_OPTSIZE
    MessageRTEMS_MESSAGE_CODE_SIZERTEMS_MESSAGE_CODE_OPTSIZE
    EventRTEMS_EVENT_CODE_SIZERTEMS_EVENT_CODE_OPTSIZE
    SignalRTEMS_SIGNAL_CODE_SIZERTEMS_SIGNAL_CODE_OPTSIZE
    PartitionRTEMS_PARTITION_CODE_SIZERTEMS_PARTITION_CODE_OPTSIZE
    RegionRTEMS_REGION_CODE_SIZERTEMS_REGION_CODE_OPTSIZE
    Dual Ported MemoryRTEMS_DPMEM_CODE_SIZERTEMS_DPMEM_CODE_OPTSIZE
    I/ORTEMS_IO_CODE_SIZERTEMS_IO_CODE_OPTSIZE
    Fatal ErrorRTEMS_FATAL_ERROR_CODE_SIZENA
    Rate MonotonicRTEMS_RATE_MONOTONIC_CODE_SIZERTEMS_RATE_MONOTONIC_CODE_OPTSIZE
    MultiprocessingRTEMS_MULTIPROCESSING_CODE_SIZERTEMS_MULTIPROCESSING_CODE_OPTSIZE
    - Total Code Space Requirements
    -
    -@end html -@end ifset - -@page - -@c ****** Next node is set by a sed script in the document Makefile. -@c ****** This comment is here to remind you not to edit the wksheets.t -@c ****** in any directory but common. - -@section RTEMS RAM Workspace Worksheet - -The RTEMS RAM Workspace Worksheet is a tool provided -to aid the RTEMS application designer to accurately calculate -the minimum memory block to be reserved for RTEMS use. This -worksheet provides equations for calculating the amount of -memory required based upon the number of objects configured, -whether for single or multiple processor versions of the -executive. This information is presented in tabular form, along -with the fixed system requirements, allowing for quick -calculation of any application defined configuration of RTEMS. -The RTEMS RAM Workspace Worksheet is provided below: - -@ifset use-ascii -@page -@end ifset -@ifset use-tex -@sp 2 -@end ifset - -@center @b{RTEMS RAM Workspace Worksheet} -@sp 2 - -@ifset use-ascii -The total RTEMS RAM Workspace required is the sum of the following: - -@itemize @bullet -@item maximum_tasks * RTEMS_BYTES_PER_TASK -@item maximum_timers * RTEMS_BYTES_PER_TIMER -@item maximum_semaphores * RTEMS_BYTES_PER_SEMAPHORE -@item maximum_message_queues * RTEMS_BYTES_PER_MESSAGE_QUEUE -@item maximum_regions * RTEMS_BYTES_PER_REGION -@item maximum_partitions * RTEMS_BYTES_PER_PARTITION -@item maximum_ports * RTEMS_BYTES_PER_PORT -@item maximum_periods * RTEMS_BYTES_PER_PERIOD -@item maximum_extensions * RTEMS_BYTES_PER_EXTENSION -@item Floating Point Tasks * RTEMS_BYTES_PER_FP_TASK -@item Task Stacks -@item maximum_nodes * RTEMS_BYTES_PER_NODE -@item maximum_global_objects * RTEMS_BYTES_PER_GLOBAL_OBJECT -@item maximum_proxies * RTEMS_BYTES_PER_PROXY -@item Fixed System Requirements of RTEMS_BYTES_OF_FIXED_SYSTEM_REQUIREMENTS -@end itemize -@end ifset - -@ifset use-tex -@tex -\line{\hskip 0.75in\vbox{\offinterlineskip\halign{ -\vrule\strut#& -\hbox to 3.0in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 0.75in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 1.25in{\enskip\hfil#\hfil}& -\vrule#\cr -\noalign{\hrule} -& \bf Description && \bf Equation && \bf Bytes Required &\cr\noalign{\hrule} -& maximum\_tasks && * RTEMS_BYTES_PER_TASK = &&&\cr\noalign{\hrule} -& maximum\_timers && * RTEMS_BYTES_PER_TIMER = &&&\cr\noalign{\hrule} -& maximum\_semaphores && * RTEMS_BYTES_PER_SEMAPHORE = &&&\cr\noalign{\hrule} -& maximum\_message\_queues && * RTEMS_BYTES_PER_MESSAGE_QUEUE = &&&\cr\noalign{\hrule} -& maximum\_regions && * RTEMS_BYTES_PER_REGION = &&&\cr\noalign{\hrule} -& maximum\_partitions && * RTEMS_BYTES_PER_PARTITION = &&&\cr\noalign{\hrule} -& maximum\_ports && * RTEMS_BYTES_PER_PORT = &&&\cr\noalign{\hrule} -& maximum\_periods && * RTEMS_BYTES_PER_PERIOD = &&&\cr\noalign{\hrule} -& maximum\_extensions && * RTEMS_BYTES_PER_EXTENSION = &&&\cr\noalign{\hrule} -& Floating Point Tasks && * RTEMS_BYTES_PER_FP_TASK = &&&\cr\noalign{\hrule} -& Task Stacks &&\hskip 2.3em=&&&\cr\noalign{\hrule} -& Total Single Processor Requirements &&&&&\cr\noalign{\hrule} -}}\hfil} - -\line{\hskip 0.75in\vbox{\offinterlineskip\halign{ -\vrule\strut#& -\hbox to 3.0in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 0.75in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 1.25in{\enskip\hfil#\hfil}& -\vrule#\cr -\noalign{\hrule} -& \bf Description && \bf Equation && \bf Bytes Required &\cr\noalign{\hrule} -& maximum\_nodes && * RTEMS_BYTES_PER_NODE = &&&\cr\noalign{\hrule} -& maximum\_global\_objects && * RTEMS_BYTES_PER_GLOBAL_OBJECT = &&&\cr\noalign{\hrule} -& maximum\_proxies && * RTEMS_BYTES_PER_PROXY = &&&\cr\noalign{\hrule} -}}\hfil} - -\line{\hskip 0.75in\vbox{\offinterlineskip\halign{ -\vrule\strut#& -\hbox to 3.0in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 0.75in{\enskip\hfil#\hfil}& -\vrule#& -\hbox to 1.25in{\enskip\hfil#\hfil}& -\vrule#\cr -\noalign{\hrule} -& Total Multiprocessing Requirements &&&&&\cr\noalign{\hrule} -& Fixed System Requirements && RTEMS_BYTES_OF_FIXED_SYSTEM_REQUIREMENTS &&&\cr\noalign{\hrule} -& Total Single Processor Requirements &&&&&\cr\noalign{\hrule} -& Total Multiprocessing Requirements &&&&&\cr\noalign{\hrule} -& Minimum Bytes for RTEMS Workspace &&&&&\cr\noalign{\hrule} -}}\hfil} -@end tex -@end ifset - -@ifset use-html -@html -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    DescriptionEquationBytes Required
    maximum_tasks* RTEMS_BYTES_PER_TASK =
    maximum_timers* RTEMS_BYTES_PER_TIMER =
    maximum_semaphores* RTEMS_BYTES_PER_SEMAPHORE =
    maximum_message_queues* RTEMS_BYTES_PER_MESSAGE_QUEUE =
    maximum_regions* RTEMS_BYTES_PER_REGION =
    maximum_partitions* RTEMS_BYTES_PER_PARTITION =
    maximum_ports* RTEMS_BYTES_PER_PORT =
    maximum_periods* RTEMS_BYTES_PER_PERIOD =
    maximum_extensions* RTEMS_BYTES_PER_EXTENSION =
    Floating Point Tasks* RTEMS_BYTES_PER_FP_TASK =
    Task Stacks
    - Total Single Processor Requirements
    DescriptionEquationBytes Required
    maximum_nodes* RTEMS_BYTES_PER_NODE =
    maximum_global_objects* RTEMS_BYTES_PER_GLOBAL_OBJECT =
    maximum_proxies* RTEMS_BYTES_PER_PROXY =
    - Total Multiprocessing Requirements
    Fixed System RequirementsRTEMS_BYTES_OF_FIXED_SYSTEM_REQUIREMENTS
    Total Single Processor Requirements
    Total Multiprocessing Requirements
    - Minimum Bytes for RTEMS Workspace
    -
    -@end html -@end ifset - diff --git a/doc/develenv/Makefile b/doc/develenv/Makefile deleted file mode 100644 index 2214554ae6..0000000000 --- a/doc/develenv/Makefile +++ /dev/null @@ -1,54 +0,0 @@ -# -# COPYRIGHT (c) 1988-1999. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=develenv - -include ../Make.config - -all: html info ps pdf - -dirs: - $(make-dirs) - -COMMON_FILES=../common/cpright.texi - -FILES=compile.texi $(PROJECT).texi direct.texi intro.texi sample.texi utils.texi - -info: dirs $(PROJECT) - cp $(PROJECT) $(INFO_INSTALL) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: dirs $(PROJECT).dvi -ps: dirs $(PROJECT).ps -pdf: dirs $(PROJECT).pdf - -$(PROJECT).pdf: $(FILES) - $(TEXI2PDF) $(PROJECT).texi - cp $(PROJECT).pdf $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).ps: $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - cp $(PROJECT).dvi $(WWW_INSTALL)/$(PROJECT) - -html: dirs - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - -cd .. ; gmake headers - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -clean: - rm -f *.o $(PROG) *.txt core *.html $(PROJECT).pdf - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* _* - diff --git a/doc/develenv/compile.texi b/doc/develenv/compile.texi deleted file mode 100644 index 79d1db7df8..0000000000 --- a/doc/develenv/compile.texi +++ /dev/null @@ -1,159 +0,0 @@ -@c This chapter is not currently in the Development Environment Guide. - -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node Compilation and GNU Make Stanzas, Compilation and GNU Make Stanzas Building the Entire Tree, Test Suite Source Directory, Top -@end ifinfo -@chapter Compilation and GNU Make Stanzas -@ifinfo -@menu -* Compilation and GNU Make Stanzas Building the Entire Tree:: -* Compilation and GNU Make Stanzas Making a Component:: -* Compilation and GNU Make Stanzas Optional Manager Support:: -@end menu -@end ifinfo - -RTEMS is compiled using the GNU gmake(1G) utilities. -All examples in this section are with the gmake(1G) command. -Note that the installation procedure for GNU Make installs it as -make. It is referred to as gmake in this document to -distinguish it from any other make utilities which may also be -on the development system. - -The GNU Make utility uses a file that describes the -relationships among the files and the operations necessary for -updating each file. The GNU Make utility uses stanzas to specify -which set of relationships to update. Each component and suite -control directory contains a make control file, Makefile, which -describes the relationships which must be checked and the -associated update operations for each stanza. This facility is -used to perform compilation, to remove intermediate files, to -install RTEMS, and to maintain release and working set source -and documentation notebooks. The following is a list of stanzas -used by RTEMS make control files: - -@ifset use-texinfo-tables -@table @code -@item all -perform compilation but do not install - -@item install -perform compilation if directory contains source but do not install - -@item clean -delete most generated files and directories for the current CPU and target - -@item clobber -delete all generated files and directories for the current CPU and target -@end table -@end ifset - -@ifclear use-texinfo-tables -@html -
    - - - - - - - - - -
    allperform compilation but do not install
    installperform compilation if directory contains source - but do not install
    cleandelete most generated files and directories for - the current CPU and target
    clobberdelete all generated files and directories for - the current CPU and target
    -
    -@end html -@end ifclear - -@ifinfo -@node Compilation and GNU Make Stanzas Building the Entire Tree, Compilation and GNU Make Stanzas Making a Component, Compilation and GNU Make Stanzas, Compilation and GNU Make Stanzas -@end ifinfo -@section Building the Entire Tree - -At the top of the C source tree, execute the command -gmake all. This will build and install all components and tests -into the directory in this directory. - -@ifinfo -@node Compilation and GNU Make Stanzas Making a Component, Compilation and GNU Make Stanzas Optional Manager Support, Compilation and GNU Make Stanzas Building the Entire Tree, Compilation and GNU Make Stanzas -@end ifinfo -@section Making a Component - -A single component can be compiled by changing to the -directory which contains that component and performing the -following command: - -@example -gmake -@end example - - -This is equivalent to the following command: - -@example -gmake all -@end example - -Both commands will result in the GNU Make utility -determining which files require compilation or assembly. If any -files require compilation or assembly, then these operations -will be performed followed by the appropriate archive or link -command. Files installed are placed in subdirectories under the -install point. The install point is determined by the setting -of the variable PROJECT_HOME in the file -c/make/custom/.cfg. - -If the current directory is not a leaf directory, -then the requested operation will be performed recursively to -all subdirectories under the current directory. - -By specifying one of the other stanzas supported by -the Makefile, the GNU Make utility can be used to perform such -operations as removing all automatically generated files in a -component (clean and clobbers stanza). - -NOTE: For many components it is not possible to -compile them until other components have been installed. - -@ifinfo -@node Compilation and GNU Make Stanzas Optional Manager Support, Sample Applications, Compilation and GNU Make Stanzas Making a Component, Compilation and GNU Make Stanzas -@end ifinfo -@section Optional Manager Support - -RTEMS allows the C applications developer to build -images that only contain those components of the executive that -are needed, leaving out those that will not be utilized. This -is accomplished by the RTEMS Makefile system linking in the -"stub" versions of the optional managers in the place of those -managers not needed by the specific application. The -application Makefile sets the system variable $(MANAGERS) list -to contain those managers that are required by the application. -The RTEMS Makefile system then is able to build a list of -managers that are unwanted, effectively linking in the stubbed -versions of these managers before the RTEMS library is built. - -For more information and implementation details refer -to the following files: - -@itemize @bullet -@item c/make/leaf.cfg, - -@item a Makefile for a test or sample application, and - -@item a compiler description file from c/make/compilers -@end itemize - -These files demonstrate the use of $(MANAGERS) and -how the unwanted managers are handled. - - diff --git a/doc/develenv/develenv.texi b/doc/develenv/develenv.texi deleted file mode 100644 index 330d68591b..0000000000 --- a/doc/develenv/develenv.texi +++ /dev/null @@ -1,122 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c %**start of header -@setfilename develenv -@syncodeindex vr fn -@synindex ky cp -@paragraphindent 0 -@c @smallbook -@c %**end of header - -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Master file -@c - -@c Joel's Questions -@c -@c 1. Why does paragraphindent only impact makeinfo? -@c 2. Why does paragraphindent show up in HTML? -@c - -@include ../common/setup.texi - -@ignore -@ifinfo -@format -START-INFO-DIR-ENTRY -* RTEMS C User: (develenv). The C User's Guide -END-INFO-DIR-ENTRY -@end format -@end ifinfo -@end ignore - -@c variable substitution info: -@c -@c @set LANGUAGE C -@c the language is @value{LANGUAGE} -@c NOTE: don't use underscore in the name -@c - -@c -@c Title Page Stuff -@c - -@set edition @value{RTEMS-EDITION} -@set version @value{RTEMS-VERSION} -@set update-date @value{RTEMS-UPDATE-DATE} -@set update-month @value{RTEMS-UPDATE-MONTH} - -@c -@c I don't really like having a short title page. --joel -@c -@c @shorttitlepage RTEMS Development Environment Guide - -@setchapternewpage odd -@settitle RTEMS Development Environment Guide -@titlepage -@finalout - -@title RTEMS Development Environment Guide -@subtitle Edition @value{edition}, for RTEMS @value{version} -@sp 1 -@subtitle @value{update-month} -@author On-Line Applications Research Corporation -@page -@include ../common/cpright.texi -@end titlepage - -@c This prevents a black box from being printed on "overflow" lines. -@c The alternative is to rework a sentence to avoid this problem. - -@include intro.texi -@include direct.texi -@c @include compile.texi -@include sample.texi -@include utils.texi - -@ifinfo -@node Top, Introduction, (dir), (dir) -@top develenv - -This is the online version of the RTEMS Development Environment Guide. - -@c * Compilation and GNU Make Stanzas:: - -@menu -* Introduction:: -* Directory Structure:: -* Sample Applications:: -* RTEMS Specific Utilities:: -* Command and Variable Index:: -* Concept Index:: -@end menu - -@end ifinfo -@c -@c -@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here -@c - -@node Command and Variable Index, Concept Index, RTEMS Specific Utilities Ada Language Specific Utilities, Top -@unnumbered Command and Variable Index - -There are currently no Command and Variable Index entries. - -@c @printindex fn - -@node Concept Index, , Command and Variable Index, Top -@unnumbered Concept Index - -There are currently no Concept Index entries. -@c @printindex cp - -@contents -@bye - diff --git a/doc/develenv/direct.texi b/doc/develenv/direct.texi deleted file mode 100644 index 8a7d2abdef..0000000000 --- a/doc/develenv/direct.texi +++ /dev/null @@ -1,730 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node Directory Structure, Directory Structure Suites, Introduction, Top -@end ifinfo -@chapter Directory Structure -@ifinfo -@menu -* Directory Structure Suites:: -@end menu -@end ifinfo - -The RTEMS directory structure is designed to meet -the following requirements: - -@itemize @bullet -@item encourage development of modular components. - -@item isolate processor and target dependent code, while -allowing as much common source code as possible to be shared -across multiple processors and targets. - -@item allow multiple RTEMS users to perform simultaneous -compilation of RTEMS and its support facilities for different -processors and targets. -@end itemize - -The resulting directory structure has processor and -target dependent source files isolated from generic files. When -RTEMS is built, object directories and an install point will be -automatically created based upon the target BSP selected. The -placement of object files based upon the selected BSP name -insures that object files are not mixed across CPUs or targets. -This in combination with the make files allows the specific -compilation options to be tailored for a particular target -board. For example, the efficiency of the memory subsystem for -a particular target board may be sensitive to the alignment of -data structures, while on another target board with the same -processor memory may be very limited. For the first target, the -options could specify very strict alignment requirements, while -on the second the data structures could be "packed" to conserve -memory. It is impossible to achieve this degree of flexibility -without providing source code. -@ifinfo -@node Directory Structure Suites, C Suites, Directory Structure, Directory Structure -@end ifinfo -@section Suites -@ifinfo -@menu -* C Suites:: -* Executive Source Directory:: -* Support Library Source Directory:: -* Test Suite Source Directory:: -@end menu -@end ifinfo - -The RTEMS source tree is organized based on the -following four variables: - -@itemize @bullet -@item language, - -@item target processor, - -@item target board, and - -@item compiler vendor (Ada only). -@end itemize - -The language may be either C or Ada and there is -currently nothing shared between the source trees for these two -implementations of RTEMS. The user generally selects the -subdirectory for the implementation they are using and ignores -that for the other implementation. The only exceptions to this -normally occurs when comparing the source code for the two -implementations or when porting both to a new CPU or target -board. The following shows the top level RTEMS directory -structure which includes directories for each language -implementation and a language independent source documentation -directory. The source documentation directory is currently not -supported. - -@c -@c Tree 1 - Top Level -@c - -@ifset use-ascii -@example -@group - RTEMS - | -+-----------------------+-----------------------+ -| | -c doc -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 15.0em -\hskip 1.25em\hbox to 3.00em{\hss{RTEMS}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 15.0em -\hskip 2.75em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 15.0em -\hskip 0.25em\vrule width2.50em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width2.50em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 15.0em -\hskip 0.25em\vrule width.04em% -\hskip 4.92em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 15.0em -\hskip 0.00em\hbox to 0.50em{\hss{c}\hss}% -\hskip 1.50em\hbox to 1.50em{\hss{ }\hss}% -\hskip 1.00em\hbox to 1.50em{\hss{doc}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@c -@c for now continue to use the ascii -@c -@ifset use-html -@example -@group - RTEMS - | -+-----------------------+-----------------------+ -| | -c doc -@end group -@end example -@html -@end html -@end ifset - -Each of the following sections will describe the -contents of the directories in the RTEMS source -tree. - -@ifinfo -@node C Suites, Executive Source Directory, Directory Structure Suites, Directory Structure Suites -@end ifinfo -@subsection C Suites - -The following table lists the suites currently included with the -C implementation of RTEMS and the directory in which they may be located: - -@ifset use-texinfo-tables -@table @code -@item Support Libraries (BSPs, C library, CPU support) -$RTEMS_ROOT/c/src/lib - -@item Single Processor Tests -$RTEMS_ROOT/c/src/tests/sptests - -@item Timing Tests -$RTEMS_ROOT/c/src/tests/tmtests - -@item Multiprocessor Tests -$RTEMS_ROOT/c/src/tests/mptests - -@item Sample Applications -$RTEMS_ROOT/c/src/tests/samples - -@item RTEMS Build Tools -$RTEMS_SRC_BASE/c/build_tools - -@item Make Support -$RTEMS_ROOT/c/make -@end table -@end ifset - -@ifclear use-texinfo-tables -@html -
    - - - - - - - - - - - - - - - -
    Support Libraries (BSPs, C library, CPU support)$RTEMS_ROOT/c/src/lib
    Single Processor Tests$RTEMS_ROOT/c/src/tests/sptests
    Timing Tests$RTEMS_ROOT/c/src/tests/tmtests
    Multiprocessor Tests$RTEMS_ROOT/c/src/tests/mptests
    Sample Applications$RTEMS_ROOT/c/src/tests/samples
    RTEMS Build Tools$RTEMS_SRC_BASE/c/build_tools
    Make Support$RTEMS_ROOT/c/make
    -
    -@end html -@end ifclear - - -The top level directory structure for the C implementation of RTEMS -is as follows: - -@c -@c Tree 2 - Top C Level -@c - -@ifset use-ascii -@example -@group - C - | - +----------+-----------+----------+ - | | | | -build_tools make src update_tools -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 08.0em -\hskip 13.00em\hbox to 0.50em{\hss{C}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 08.0em -\hskip 13.25em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 08.0em -\hskip 1.75em\vrule width11.50em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width11.50em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 08.0em -\hskip 1.75em\vrule width.04em% -\hskip 5.71em\vrule width.04em% -\hskip 5.71em\vrule width.04em% -\hskip 5.71em\vrule width.04em% -\hskip 5.71em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 08.0em -\hskip 0.00em\hbox to 3.50em{\hss{Modules}\hss}% -\hskip 1.00em\hbox to 6.00em{\hss{build\_tools}\hss}% -\hskip 1.75em\hbox to 2.00em{\hss{make}\hss}% -\hskip 4.00em\hbox to 1.50em{\hss{src}\hss}% -\hskip 1.75em\hbox to 6.50em{\hss{update\_tools}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@ifset use-html -@example -@group - C - | - +----------+-----------+----------+ - | | | | -build_tools make src update_tools -@end group -@end example -@html -@end html -@end ifset - -This directory contains the subdirectories which -contain the entire C implementation of the RTEMS executive. -The "build-tools" directory contains an assortment of support tools -for the RTEMS development environment. Two subdirectories exist -under "build-tools" which contain scripts (executables) and -source for the support tools. The "make" directory contains -configuration files and subdirectories which provide a robust -host and cross-target makefile system supporting the building of -the executive for numerous application environments. The -"update_tools" directory contains utilities which aid in the -updating from a previous version to the current version of the -RTEMS executive. - -The "src" directory structure for the C implementation of RTEMS is as follows: - -@c -@c Tree 3 - Top C src Level -@c - -@ifset use-ascii -@example -@group - C Source - | - +-----------------------+-----------------------+ - | | | -exec lib tests -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 15.0em -\hskip 2.00em\hbox to 4.00em{\hss{C Source}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 15.0em -\hskip 4.00em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 15.0em -\hskip 1.00em\vrule width3.00em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width3.00em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 15.0em -\hskip 1.00em\vrule width.04em% -\hskip 2.96em\vrule width.04em% -\hskip 2.96em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 15.0em -\hskip 0.00em\hbox to 2.00em{\hss{exec}\hss}% -\hskip 1.25em\hbox to 1.50em{\hss{lib}\hss}% -\hskip 1.00em\hbox to 2.50em{\hss{tests}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@ifset use-html -@example -@group - C Source - | - +-----------------------+-----------------------+ - | | | -exec lib tests -@end group -@end example -@html -@end html -@end ifset - -This directory contains all source files that -comprises the RTEMS executive, supported target board support -packages, and the RTEMS Test Suite. - -@ifinfo -@node Executive Source Directory, Support Library Source Directory, C Suites, Directory Structure Suites -@end ifinfo -@subsection Executive Source Directory - -The "exec" directory structure for the C implementation is as follows: - -@c -@c Tree 4 - C Executive Tree -@c - -@ifset use-ascii -@example -@group - C Executive - | - +-----------+----------+-----------+----------+ - | | | | | -posix rtems sapi score wrapup -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 10.0em -\hskip 6.00em\hbox to 5.50em{\hss{C Executive}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 10.0em -\hskip 8.75em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 10.0em -\hskip 1.25em\vrule width7.50em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width7.50em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 10.0em -\hskip 1.25em\vrule width.04em% -\hskip 3.71em\vrule width.04em% -\hskip 3.71em\vrule width.04em% -\hskip 3.71em\vrule width.04em% -\hskip 3.71em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 10.0em -\hskip 0.00em\hbox to 2.50em{\hss{posix}\hss}% -\hskip 1.25em\hbox to 2.50em{\hss{rtems}\hss}% -\hskip 1.50em\hbox to 2.00em{\hss{sapi}\hss}% -\hskip 1.50em\hbox to 2.50em{\hss{score}\hss}% -\hskip 1.00em\hbox to 3.00em{\hss{wrapup}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@ifset use-html -@example -@group - C Executive - | - +-----------+----------+-----------+----------+ - | | | | | -posix rtems sapi score wrapup -@end group -@end example -@html -@end html -@end ifset - -This directory contains a set of subdirectories which -contains the source files comprising the executive portion of -the RTEMS development environment. At this point the API -specific and "supercore" source code files are separated into -distinct directory trees. The "rtems" and the "posix" -subdirectories contain the C language source files for each -module comprising the respective API. Also included in this -directory are the subdirectories "sapi" and "score" which are -the supercore modules. Within the "score" directory the CPU -dependent modules are found. - -The "cpu" directory contains a subdirectory for each -target CPU supported by the @value{RELEASE} release of the RTEMS -executive. Each processor directory contains the CPU dependent -code necessary to host RTEMS. The "no_cpu" directory provides a -starting point for developing a new port to an unsupported -processor. The files contained within the "no_cpu" directory -may also be used as a reference for the other ports to specific -processors. - -@ifinfo -@node Support Library Source Directory, Test Suite Source Directory, Executive Source Directory, Directory Structure Suites -@end ifinfo -@subsection Support Library Source Directory - -The "lib" directory contains the support libraries and BSPS. -Board support packages (BSPs), processor environment start up code, -C library support, the FreeBSD TCP/IP stack, common BSP header files, -and miscellaneous support functions are provided in the subdirectories. -These are combined with the RTEMS executive object to form the single -RTEMS library which installed. - -@c -@c Tree 6 - Libraries -@c - - -The "libbsp" directory contains a directory for each CPU family supported -by RTEMS. Beneath each CPU directory is a directory for each BSP for that -processor family. - -@c -@c Tree 7 - C BSP Library -@c - -The "libbsp" directory provides all the BSPs provided with this -release of the RTEMS executive. The subdirectories are -divided, as discussed previously, based on specific processor -family, then further breaking down into specific target board -environments. The "shmdr" subdirectory provides the -implementation of a shared memory driver which supports the -multiprocessing portion of the executive. In addition, two -starting point subdirectories are provided for reference. The -"no_cpu" subdirectory provides a template BSP which can be used -to develop a specific BSP for an unsupported target board. The -"stubdr" subdirectory provides stubbed out BSPs. These files -may aid in preliminary testing of the RTEMS development -environment that has been built for no particular target in mind. - -Below each CPU dependent directory is a directory for each target BSP -supported in this release. - -Each BSP provides the modules which comprise an RTEMS BSP. The -modules are separated into the subdirectories "clock", "console", -"include", "shmsupp", "startup", and "timer" as shown in the following -figure: - -@c -@c Tree 8 - Each BSP -@c - -@ifset use-ascii -@example -@group - Each BSP - | - +-----------+----------+-----+-----+----------+----------+ - | | | | | | -clock console include shmsupp startup timer -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 10.0em -\hskip 10.25em\hbox to 4.50em{\hss{Each BSP}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 10.0em -\hskip 12.50em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 10.0em -\hskip 1.25em\vrule width11.25em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width11.25em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 10.0em -\hskip 1.25em\vrule width.04em% -\hskip 4.46em\vrule width.04em% -\hskip 4.46em\vrule width.04em% -\hskip 4.46em\vrule width.04em% -\hskip 4.46em\vrule width.04em% -\hskip 4.46em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 10.0em -\hskip 0.00em\hbox to 2.50em{\hss{clock}\hss}% -\hskip 1.50em\hbox to 3.50em{\hss{console}\hss}% -\hskip 1.00em\hbox to 3.50em{\hss{include}\hss}% -\hskip 1.00em\hbox to 3.50em{\hss{shmsupp}\hss}% -\hskip 1.00em\hbox to 3.50em{\hss{startup}\hss}% -\hskip 1.50em\hbox to 2.50em{\hss{timer}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@ifset use-html -@example -@group - Each BSP - | - +-----------+----------+-----+-----+----------+----------+ - | | | | | | -clock console include ... startup timer -@end group -@end example -@html -@end html -@end ifset - -@ifinfo -@node Test Suite Source Directory, Sample Applications, Support Library Source Directory, Directory Structure Suites -@end ifinfo -@subsection Test Suite Source Directory - -The "tests" directory structure for the C -implementation is as follows: - -@c -@c Tree 9 - C Tests -@c - -@ifset use-ascii -@example -@group - C Tests - | - +----------+---------+----------+---------+---------+---------+ - | | | | | | | -libtests sptests support tmtests mptests psxtest samples -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 05.0em -\hskip 14.50em\hbox to 3.50em{\hss{C Tests}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 05.0em -\hskip 16.25em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 05.0em -\hskip 2.00em\vrule width14.25em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width14.25em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 05.0em -\hskip 2.00em\vrule width.04em% -\hskip 4.71em\vrule width.04em% -\hskip 4.71em\vrule width.04em% -\hskip 4.71em\vrule width.04em% -\hskip 4.71em\vrule width.04em% -\hskip 4.71em\vrule width.04em% -\hskip 4.71em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 05.0em -\hskip 0.00em\hbox to 4.00em{\hss{libtests}\hss}% -\hskip 1.00em\hbox to 3.50em{\hss{sptests}\hss}% -\hskip 1.25em\hbox to 3.50em{\hss{support}\hss}% -\hskip 1.25em\hbox to 3.50em{\hss{tmtests}\hss}% -\hskip 1.25em\hbox to 3.50em{\hss{mptests}\hss}% -\hskip 1.75em\hbox to 2.50em{\hss{tools}\hss}% -\hskip 1.75em\hbox to 3.50em{\hss{samples}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@ifset use-html -@example -@group - C Tests - | - +----------+---------+----------+---------+---------+---------+ - | | | | | | | -libtests sptests support tmtests mptests tools samples -@end group -@end example -@html -@end html -@end ifset - -This directory provides the entire RTEMS Test Suite -which includes the single processor tests, multiprocessor tests, -timing tests, library tests, and sample tests. Additionally, -subdirectories for support functions and test related header -files are provided. - -The "sptests" subdirectory consists of twenty-four -tests designed to cover the entire executive code. The -"spfatal" test will verify any code associated with the -occurrence of a fatal error. Also provided is a test which -will determine the size of the RTEMS executive. - -The multiprocessor test are provided in "mptests". -Fourteen tests are provided in this subdirectory which address -two node configurations and cover the multiprocessor code found -in RTEMS. - -Tests that time each directive and a set of critical -executive functions are provided in the "tmtests" subdirectory. -Within this subdirectory thirty-one tests are provided along -with a subdirectory to contain each targets timing results. - -The "samples" directory structure for the C -implementation is as follows: - -@c -@c Tree 10 - C Samples -@c - -@ifset use-ascii -@example -@group - C Samples - | - +-----------+----------+-----+-----+----------+----------+ - | | | | | | -base_mp base_sp cdtest hello paranoia ticker -@end group -@end example -@end ifset - -@ifset use-tex -@sp 1 - -@tex -{\parskip=0pt\offinterlineskip% -\hskip 05.0em -\hskip 12.25em\hbox to 4.50em{\hss{C Samples}\hss}% -\vrule width0em height1.972ex depth0.812ex\par\penalty10000 -\hskip 05.0em -\hskip 14.50em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 05.0em -\hskip 2.00em\vrule width12.50em height-0.407ex depth0.500ex% -\vrule width.04em\vrule width12.50em height-0.407ex depth0.500ex% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 05.0em -\hskip 2.00em\vrule width.04em% -\hskip 4.96em\vrule width.04em% -\hskip 4.96em\vrule width.04em% -\hskip 4.96em\vrule width.04em% -\hskip 4.96em\vrule width.04em% -\hskip 4.96em\vrule width.04em% -\vrule width0em height1.500ex depth0.500ex\par\penalty10000 -\hskip 05.0em -\hskip 0.00em\hbox to 4.00em{\hss{base\_mp}\hss}% -\hskip 1.00em\hbox to 4.00em{\hss{base\_sp}\hss}% -\hskip 1.50em\hbox to 3.00em{\hss{cdtest}\hss}% -\hskip 2.25em\hbox to 2.50em{\hss{hello}\hss}% -\hskip 1.75em\hbox to 4.00em{\hss{paranoia}\hss}% -\hskip 1.50em\hbox to 3.00em{\hss{ticker}\hss}% -\vrule width0em height1.972ex depth0.812ex\par} -@end tex -@end ifset - -@ifset use-html -@example -@group - C Samples - | - +-----------+----------+-----+-----+----------+----------+ - | | | | | | -base_mp base_sp cdtest hello paranoia ticker -@end group -@end example -@html -@end html -@end ifset - -This directory provides sample application tests -which aid in the testing a newly built RTEMS environment, a new -BSP, or as starting points for the development of an application -using the RTEMS executive. A Hello World test is provided in -the subdirectory "hello". This test is helpful when testing new -versions of RTEMS, BSPs, or modifications to any portion of the -RTEMS development environment. The "ticker" subdirectory -provides a test for verification of clock chip device drivers of -BSPs. A simple single processor test similar to those in the -single processor test suite is provided in "base_sp". A simple -two node multiprocessor test capable of testing an newly -developed MPCI layer is provided in "base_mp". The "cdtest" -subdirectory provides a simple C++ application using -constructors and destructors. The final sample test is a -public domain floating point and math library toolset test is -provided in "paranoia". diff --git a/doc/develenv/intro.texi b/doc/develenv/intro.texi deleted file mode 100644 index 0c7262d23f..0000000000 --- a/doc/develenv/intro.texi +++ /dev/null @@ -1,58 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node Introduction, Directory Structure, Top, Top -@end ifinfo -@chapter Introduction - -This document describes the RTEMS development -environment. Discussions are provided for the following topics: - -@itemize @bullet -@item the directory structure used by RTEMS, - -@item usage of the GNU Make utility within the RTEMS -development environment, - -@item sample applications, and - -@item the RTEMS specific utilities. -@end itemize - -RTEMS was designed as a reusable software component. -Highly reusable software such as RTEMS is typically distributed -in the form of source code without providing any support tools. -RTEMS is the foundation for a complex family of facilities -including board support packages, device drivers, and support -libraries. The RTEMS Development Environment is not a CASE -tool. It is a collection of tools designed to reduce the -complexity of using and enhancing the RTEMS family. Tools are -provided which aid in the management of the development, -maintenance, and usage of RTEMS, its run-time support -facilities, and applications which utilize the executive. - -A key component of the RTEMS development environment -is the GNU family of free tools. This is robust set of -development and POSIX compatible tools for which source code is -freely available. The primary compilers, assemblers, linkers, -and make utility used by the RTEMS development team are the GNU -tools. They are highly portable supporting a wide variety of -host computers and, in the case of the development tools, a wide -variety of target processors. - -It is recommended that the RTEMS developer become -familiar with the RTEMS Development Environment before -proceeding with any modifications to the executive source tree. -The source code for the executive is very modular and source -code is divided amongst directories based upon functionality as -well as dependencies on CPU and target board. This organization -is aimed at isolating and minimizing non-portable code. This -has the immediate result that adding support for a new CPU or -target board requires very little "wandering" around the source -tree. diff --git a/doc/develenv/sample.texi b/doc/develenv/sample.texi deleted file mode 100644 index 75dbc78b89..0000000000 --- a/doc/develenv/sample.texi +++ /dev/null @@ -1,287 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node Sample Applications, Sample Applications Introduction, Test Suite Source Directory, Top -@end ifinfo -@chapter Sample Applications -@ifinfo -@menu -* Sample Applications Introduction:: -* Sample Applications Hello World:: -* Sample Applications Clock Tick:: -* Sample Applications Base Single Processor Application:: -* Sample Applications Base Multiple Processor Application:: -* Sample Applications Constructor/Destructor C++ Application:: -* Sample Applications Paranoia Floating Point Application:: -@end menu -@end ifinfo - -@ifinfo -@node Sample Applications Introduction, Sample Applications Hello World, Sample Applications, Sample Applications -@end ifinfo -@section Introduction - -RTEMS is shipped with the following sample applications: - -@itemize @bullet -@item Hello World - C and Ada - -@item Clock Tick - C and Ada - -@item Base Single Processor - C and Ada - -@item Base Multiple Processor - C and Ada - -@item Constructor/Destructor C++ Test - C only if C++ -enabled - -@item Paranoia Floating Point Test - C only -@end itemize - -These applications are intended to illustrate the -basic format of RTEMS single and multiple processor -applications. In addition, these relatively simple applications -can be used to test locally developed board support packages and -device drivers. - -The reader should be familiar with the terms used and -material presented in the RTEMS Applications User's Guide. - -@ifinfo -@node Sample Applications Hello World, Sample Applications Clock Tick, Sample Applications Introduction, Sample Applications -@end ifinfo -@section Hello World - -This sample application is in the following directory: - -@example -$RTEMS_SRC_BASE/tests/samples/hello -@end example - -It provides a rudimentary test of the BSP start up -code and the console output routine. The C version of this -sample application uses the printf function from the RTEMS -Standard C Library to output messages. The Ada version of this -sample use the TEXT_IO package to output the hello messages. -The following messages are printed: - -@example -@group -*** HELLO WORLD TEST *** -Hello World -*** END OF HELLO WORLD TEST *** -@end group -@end example - -These messages are printed from the application's -single initialization task. If the above messages are not -printed correctly, then either the BSP start up code or the -console output routine is not operating properly. - -@ifinfo -@node Sample Applications Clock Tick, Sample Applications Base Single Processor Application, Sample Applications Hello World, Sample Applications -@end ifinfo -@section Clock Tick - -This sample application is in the following directory: - -@example -$RTEMS_SRC_BASE/tests/samples/ticker -@end example - -This application is designed as a simple test of the -clock tick device driver. In addition, this application also -tests the printf function from the RTEMS Standard C Library by -using it to output the following messages: - -@example -@group -*** CLOCK TICK TEST *** -TA1 - tm_get - 09:00:00 12/31/1988 -TA2 - tm_get - 09:00:00 12/31/1988 -TA3 - tm_get - 09:00:00 12/31/1988 -TA1 - tm_get - 09:00:05 12/31/1988 -TA1 - tm_get - 09:00:10 12/31/1988 -TA2 - tm_get - 09:00:10 12/31/1988 -TA1 - tm_get - 09:00:15 12/31/1988 -TA3 - tm_get - 09:00:15 12/31/1988 -TA1 - tm_get - 09:00:20 12/31/1988 -TA2 - tm_get - 09:00:20 12/31/1988 -TA1 - tm_get - 09:00:25 12/31/1988 -TA1 - tm_get - 09:00:30 12/31/1988 -TA2 - tm_get - 09:00:30 12/31/1988 -TA3 - tm_get - 09:00:30 12/31/1988 -*** END OF CLOCK TICK TEST *** -@end group -@end example - -The clock tick sample application utilizes a single -initialization task and three copies of the single application -task. The initialization task prints the test herald, sets the -time and date, and creates and starts the three application -tasks before deleting itself. The three application tasks -generate the rest of the output. Every five seconds, one or -more of the tasks will print the current time obtained via the -tm_get directive. The first task, TA1, executes every five -seconds, the second task, TA2, every ten seconds, and the third -task, TA3, every fifteen seconds. If the time printed does not -match the above output, then the clock device driver is not -operating properly. - -@ifinfo -@node Sample Applications Base Single Processor Application, Sample Applications Base Multiple Processor Application, Sample Applications Clock Tick, Sample Applications -@end ifinfo -@section Base Single Processor Application - -This sample application is in the following directory: - -@example -$RTEMS_SRC_BASE/tests/samples/base_sp -@end example - -It provides a framework from which a single processor -RTEMS application can be developed. The use of the task argument -is illustrated. This sample application uses the printf -function from the RTEMS Standard C Library or TEXT_IO functions -when using the Ada version to output the following messages: - -@example -@group -*** SAMPLE SINGLE PROCESSOR APPLICATION *** -Creating and starting an application task -Application task was invoked with argument (0) and has id of 0x10002 -*** END OF SAMPLE SINGLE PROCESSOR APPLICATION *** -@end group -@end example - -The first two messages are printed from the -application's single initialization task. The final messages -are printed from the single application task. - -@ifinfo -@node Sample Applications Base Multiple Processor Application, Sample Applications Constructor/Destructor C++ Application, Sample Applications Base Single Processor Application, Sample Applications -@end ifinfo -@section Base Multiple Processor Application - -This sample application is in the following directory: - -@example -$RTEMS_SRC_BASE/tests/samples/base_mp -@end example - -It provides a framework from which a multiprocessor -RTEMS application can be developed. This directory has a -subdirectory for each node in the multiprocessor system. The -task argument is used to distinguish the node on which the -application task is executed. The first node will print the -following messages: - -@example -@group -*** SAMPLE MULTIPROCESSOR APPLICATION *** -Creating and starting an application task -This task was invoked with the node argument (1) -This task has the id of 0x10002 -*** END OF SAMPLE MULTIPROCESSOR APPLICATION *** -@end group -@end example - -The second node will print the following messages: - -@example -@group -*** SAMPLE MULTIPROCESSOR APPLICATION *** -Creating and starting an application task -This task was invoked with the node argument (2) -This task has the id of 0x20002 -*** END OF SAMPLE MULTIPROCESSOR APPLICATION *** -@end group -@end example - -The herald is printed from the application's single -initialization task on each node. The final messages are -printed from the single application task on each node. - -In this sample application, all source code is shared -between the nodes except for the node dependent configuration -files. These files contains the definition of the node number -used in the initialization of the RTEMS Multiprocessor -Configuration Table. This file is not shared because the node -number field in the RTEMS Multiprocessor Configuration Table -must be unique on each node. - -@ifinfo -@node Sample Applications Constructor/Destructor C++ Application, Sample Applications Paranoia Floating Point Application, Sample Applications Base Multiple Processor Application, Sample Applications -@end ifinfo -@section Constructor/Destructor C++ Application - -This sample application is in the following directory: - -@example -$RTEMS_SRC_BASE/tests/samples/cdtest -@end example - -This sample application demonstrates that RTEMS is -compatible with C++ applications. It uses constructors, -destructor, and I/O stream output in testing these various -capabilities. The board support package responsible for this -application must support a C++ environment. - -This sample application uses the printf function from -the RTEMS Standard C Library to output the following messages: - -@example -@group -Hey I'M in base class constructor number 1 for 0x400010cc. -Hey I'M in base class constructor number 2 for 0x400010d4. -Hey I'M in derived class constructor number 3 for 0x400010d4. -*** CONSTRUCTOR/DESTRUCTOR TEST *** -Hey I'M in base class constructor number 4 for 0x4009ee08. -Hey I'M in base class constructor number 5 for 0x4009ee10. -Hey I'M in base class constructor number 6 for 0x4009ee18. -Hey I'M in base class constructor number 7 for 0x4009ee20. -Hey I'M in derived class constructor number 8 for 0x4009ee20. -Testing a C++ I/O stream -Hey I'M in derived class constructor number 8 for 0x4009ee20. -Derived class - Instantiation order 8 -Hey I'M in base class constructor number 7 for 0x4009ee20. -Instantiation order 8 -Hey I'M in base class constructor number 6 for 0x4009ee18. -Instantiation order 6 -Hey I'M in base class constructor number 5 for 0x4009ee10. -Instantiation order 5 -Hey I'M in base class constructor number 4 for 0x4009ee08. -Instantiation order 5 -*** END OF CONSTRUCTOR/DESTRUCTOR TEST *** -Hey I'M in base class constructor number 3 for 0x400010d4. -Hey I'M in base class constructor number 2 for 0x400010d4. -Hey I'M in base class constructor number 1 for 0x400010cc. -@end group -@end example - -@ifinfo -@node Sample Applications Paranoia Floating Point Application, RTEMS Specific Utilities, Sample Applications Constructor/Destructor C++ Application, Sample Applications -@end ifinfo -@section Paranoia Floating Point Application - -This sample application is in the following directory: - -@example -$RTEMS_SRC_BASE/tests/samples/paranoia -@end example - -This sample application uses a public domain floating -point and math library test to verify these capabilities of the -RTEMS executive. Deviations between actual and expected results -are reported to the screen. This is a very extensive test which -tests all mathematical and number conversion functions. -Paranoia is also very large and requires a long period of time -to run. Problems which commonly prevent this test from -executing to completion include stack overflow and FPU exception -handlers not installed. diff --git a/doc/develenv/utils.texi b/doc/develenv/utils.texi deleted file mode 100644 index 2443bd8495..0000000000 --- a/doc/develenv/utils.texi +++ /dev/null @@ -1,312 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node RTEMS Specific Utilities, RTEMS Specific Utilities C Language Specific Utilities, Sample Applications Paranoia Floating Point Application, Top -@end ifinfo -@chapter RTEMS Specific Utilities -@ifinfo -@menu -* RTEMS Specific Utilities C Language Specific Utilities:: -* RTEMS Specific Utilities Ada Language Specific Utilities:: -@end menu -@end ifinfo - -This section describes the additional commands -available within the RTEMS Development Environment. Although -some of these commands are of general use, most are included to -provide some capability necessary to perform a required function -in the development of the RTEMS executive, one of its support -components, or an RTEMS based application. The commands have -been classified into the following categories for clarity: - -@itemize @bullet -@item C Language Specific Utilities - -@item Ada Language Specific Utilities -@end itemize - -Some of the commands are implemented as C programs. -However, most commands are implemented as Bourne shell scripts. -Even if the current user has selected a different shell, the -scripts will automatically invoke the Bourne shell during their -execution lifetime. - -The commands are presented in UNIX manual page style -for compatibility and convenience. A standard set of paragraph -headers were used for all of the command descriptions. If a -section contained no data, the paragraph header was omitted to -conserve space. Each of the permissible paragraph headers and -their contents are described below: - -@table @code -@item SYNOPSIS -describes the command syntax - -@item DESCRIPTION -a full description of the command - -@item OPTIONS -describes each of the permissible options for the command - -@item NOTES -lists any special noteworthy comments about the command - -@item ENVIRONMENT -describes all environment variables utilized by the command - -@item EXAMPLES -illustrates the use of the command with specific examples - -@item FILES -provides a list of major files that the command references - -@item SEE ALSO -lists any relevant commands which can be consulted -@end table - -Most environment variables referenced by the commands -are defined for the RTEMS Development Environment during the -login procedure. During login, the user selects a default RTEMS -environment through the use of the Modules package. This tool -effectively sets the environment variables to provide a -consistent development environment for a specific user. -Additional environment variables within the RTEMS environment -were set by the system administrator during installation. When -specifying paths, a command description makes use of these -environment variables. - -When referencing other commands in the SEE ALSO -paragraph, the following notation is used: command(code). -Where command is the name of a related command, and code is a -section number. Valid section numbers are as follows: - -@table @code -@item 1 -Section 1 of the standard UNIX documentation - -@item 1G -Section 1 of the GNU documentation - -@item 1R -a manual page from this document, the RTEMS Development Environment Guide -@end table - -For example, ls(1) means see the standard ls command -in section 1 of the UNIX documentation. gcc020(1G) means see -the description of gcc020 in section 1 of the GNU documentation. - -@ifinfo -@node RTEMS Specific Utilities C Language Specific Utilities, packhex - Compress Hexadecimal File, RTEMS Specific Utilities, RTEMS Specific Utilities -@end ifinfo -@section C Language Specific Utilities -@ifinfo -@menu -* packhex - Compress Hexadecimal File:: -* unhex - Convert Hexadecimal File into Binary:: -* size_rtems - report RTEMS size information:: -@end menu -@end ifinfo - -The C language utilities provide a powerful set of -tools which combine to allow operations within the RTEMS -Development Environment to be consistent and easy to use. Much -effort was devoted to providing as close to the standard UNIX -and GNU style of operations as possible. Each of these -utilities are described in the section below. - -@ifinfo -@node packhex - Compress Hexadecimal File, unhex - Convert Hexadecimal File into Binary, RTEMS Specific Utilities C Language Specific Utilities, RTEMS Specific Utilities C Language Specific Utilities -@end ifinfo -@subsection packhex - Compress Hexadecimal File - -@subheading SYNOPSIS - -@example -packhex destination -@end example - -@subheading DESCRIPTION - -packhex accepts Intel Hexadecimal or Motorola Srecord -on its standard input and attempts to pack as many contiguous -bytes as possible into a single hexadecimal record. Many -programs output hexadecimal records which are less than 80 bytes -long (for human viewing). The overhead required by each -unnecessary record is significant and packhex can often reduce -the size of the download image by 20%. packhex attempts to -output records which are as long as the hexadecimal format -allows. - -@subheading OPTIONS - -This command has no options. - -@subheading EXAMPLES - -Assume the current directory contains the Motorola -Srecord file download.sr. Then executing the command: - -@example -packhex packed.sr -@end example - -will generate the file packed.sr which is usually -smaller than download.sr. - -@subheading CREDITS - -The source for packhex first appeared in the May 1993 -issue of Embedded Systems magazine. The code was downloaded -from their BBS. Unfortunately, the author's name was not -provided in the listing. - -@ifinfo -@node unhex - Convert Hexadecimal File into Binary, size_rtems - report RTEMS size information, packhex - Compress Hexadecimal File, RTEMS Specific Utilities C Language Specific Utilities -@end ifinfo -@subsection unhex - Convert Hexadecimal File into Binary Equivalent - -@subheading SYNOPSIS - -@example -unhex [-valF] [-o file] [file [file ...] ] -@end example - -@subheading DESCRIPTION - -unhex accepts Intel Hexadecimal, Motorola Srecord, or -TI 'B' records and converts them to their binary equivalent. -The output may sent to standout or may be placed in a specified -file with the -o option. The designated output file may not be -an input file. Multiple input files may be specified with their -outputs logically concatenated into the output file. - -@subheading OPTIONS - -This command has the following options: - -@table @code -@item v -Verbose - -@item a base -First byte of output corresponds with base -address - -@item l -Linear Output - -@item o file -Output File - -@item F k_bits -Fill holes in input with 0xFFs up to k_bits * 1024 bits -@end table - -@subheading EXAMPLES - -The following command will create a binary equivalent -file for the two Motorola S record files in the specified output -file binary.bin: - -@example -unhex -o binary.bin downloadA.sr downloadB.sr -@end example - -@ifinfo -@node size_rtems - report RTEMS size information, RTEMS Specific Utilities Ada Language Specific Utilities, unhex - Convert Hexadecimal File into Binary, RTEMS Specific Utilities C Language Specific Utilities -@end ifinfo -@subsection size_rtems - report RTEMS size information - -@subheading SYNOPSIS - -@example -size_rtems -@end example - -@subheading DESCRIPTION - -size_rtems analyzes RTEMS and determines all of the -critical sizing information which is reported in the related -documentation. - -@subheading EXAMPLES - -To generate the RTEMS size report for the currently -configured processor, execute the following command: - -@example -size_rtems -@end example - -Although the actual size information will differ, a -report of the following format will be output: - -@example - RTEMS SIZE REPORT - -CODE DATA BSS -================== -MANAGERS: 15988 0 0 -CORE : 4568 0 0 -CPU : 364 0 0 -OVERALL : 20556 0 0 -MINIMUM : 8752 0 0 - -init : 1592 0 0 -tasks : 2440 0 0 -intr : 64 0 0 -clock : 2252 0 0 -sem : 876 0 0 -msg : 1624 0 0 -event : 604 0 0 -signal : 212 0 0 -part : 872 0 0 -region : 844 0 0 -dpmem : 532 0 0 -timer : 424 0 0 -io : 288 0 0 -fatal : 40 0 0 -rtmon : 764 0 0 -mp : 2984 0 0 - -sem : 4 0 0 -msg : 4 0 0 -event : 4 0 0 -signal : 4 0 0 -part : 4 0 0 -region : 4 0 0 -timer : 4 0 0 -dpmem : 4 0 0 -io : 4 0 0 -rtmon : 4 0 0 -mp : 8 0 0 -@end example - -@subheading SEE ALSO - -gsize020(1G), gsize386(1G), gsize960(1G) - - -@ifinfo -@node RTEMS Specific Utilities Ada Language Specific Utilities, Command and Variable Index, size_rtems - report RTEMS size information, RTEMS Specific Utilities -@end ifinfo -@section Ada Language Specific Utilities - -The Ada language utilities provide a powerful set of -tools which combine to allow operations within the RTEMS -Development Environment to be consistent and easy to use. Much -effort was devoted to providing as close to the standard UNIX -and GNU style of operations as possible. Each of these -utilities are described in the section below. - -NOTE: The Ada implementation is not included in this -release. - - - diff --git a/doc/do_docs b/doc/do_docs deleted file mode 100755 index ef3771a6f4..0000000000 --- a/doc/do_docs +++ /dev/null @@ -1,53 +0,0 @@ -#! /bin/sh -# -# $Id$ -# - -basedir=$1 -shift - -# classes of documents -supplements="supplements/hppa1_1 supplements/i386 \ - supplements/i960 supplements/m68k supplements/sparc supplements/powerpc" - -# relnotes is obsolete - -# Division by access level -public_docs="FAQ user develenv networking posix_users itron3.0 \ - started started_ada rtems_gdb rgdb_specs" -support_docs="${supplements} bsp_howto filesystem porting ada_user posix1003.1" - -if [ x${MANUAL_SET} = x ] ; then - MANUAL_SET=public -fi - -case ${MANUAL_SET} in - public) - # manuals="$public_docs" - # ;; - #support) - manuals="$public_docs $support_docs" - ;; - *) - echo "ERROR: Unknown manual set ${MANUAL_SET}" - exit 1 - ;; -esac - -for action in $* -do - for manual in $manuals - do - if [ x${TEST} = xyes ] ; then - echo "TEST *** make $action on ${basedir}/${manual} ***" - else - echo - echo "*** make $action on ${basedir}/${manual} ***" - echo - cd ${basedir}/${manual} - gmake $action || exit $? - fi - done -done - -exit 0 diff --git a/doc/filesystem/Makefile b/doc/filesystem/Makefile deleted file mode 100644 index 868ab9b40c..0000000000 --- a/doc/filesystem/Makefile +++ /dev/null @@ -1,120 +0,0 @@ -# -# COPYRIGHT (c) 1988-1999. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=filesystem - -include ../Make.config - -REPLACE=../tools/word-replace - -BMENU+= -c - -all: html info ps pdf - -dirs: - $(make-dirs) - -COMMON_FILES=../common/cpright.texi ../common/setup.texi - -GENERATED_FILES=patheval.texi \ - init.texi mounting.texi syscalls.texi fsrequirements.texi imfs.texi \ - miniimfs.texi tftp.texi - -FILES= $(PROJECT).texi \ - preface.texi $(GENERATED_FILES) - -INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*) - -info: dirs $(PROJECT) - #cp $(wildcard $(PROJECT) $(PROJECT)-*) $(INFO_INSTALL) - cp $(PROJECT) $(INFO_INSTALL) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: dirs $(PROJECT).dvi -ps: dirs $(PROJECT).ps -pdf: dirs $(PROJECT).pdf - -$(PROJECT).pdf: $(FILES) - $(TEXI2PDF) $(PROJECT).texi - cp $(PROJECT).pdf $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).ps: $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - cp $(PROJECT).dvi $(WWW_INSTALL)/$(PROJECT) - -patheval.texi: patheval.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -init.texi: init.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -mounting.texi: mounting.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -syscalls.texi: syscalls.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -fsrequirements.texi: fsrequirements.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -imfs.texi: imfs.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -miniimfs.texi: miniimfs.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -tftp.texi: tftp.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -html: dirs $(FILES) - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - # rm -f $(WWW_INSTALL)/$(PROJECT)/networkflow.jpg - # rm -f $(WWW_INSTALL)/$(PROJECT)/networkflow.png - # rm -f $(WWW_INSTALL)/$(PROJECT)/PCIreg.jpg - # cp recvbd.jpg $(WWW_INSTALL)/$(PROJECT)/recvbd.jpg - # cp networkflow.jpg $(WWW_INSTALL)/$(PROJECT)/networkflow.jpg - # cp networkflow.png $(WWW_INSTALL)/$(PROJECT)/networkflow.png - # cp PCIreg.jpg $(WWW_INSTALL)/$(PROJECT)/PCIreg.jpg - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -clean: - rm -f *.o $(PROG) *.txt core $(PROJECT).pdf - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* $(GENERATED_FILES) - rm -f networking networking-* - rm -f timedata.texi timetbl.texi intr.texi wksheets.texi - rm -f timetbl.t wksheets.t - rm -f *.fixed _* - -convert: -# /usr/bin/gs -dMaxBitmap=300000000 -g5500x7500 -sDEVICE=pdfwrite -q -dNOPAUSE -dSAFER -sOutputFile=networkflow.pdf -- networkflow.eps -c -quit -# /usr/bin/gs -dMaxBitmap=300000000 -g4500x5500 -sDEVICE=pdfwrite -q -dNOPAUSE -dSAFER -sOutputFile=PCIreg.pdf -- PCIreg.eps -c -quit -# /usr/bin/gs -dMaxBitmap=300000000 -g4500x5500 -sDEVICE=pdfwrite -q -dNOPAUSE -dSAFER -sOutputFile=recvbd.pdf -- recvbd.eps -c -quit diff --git a/doc/filesystem/filesystem.texi b/doc/filesystem/filesystem.texi deleted file mode 100644 index eabde38005..0000000000 --- a/doc/filesystem/filesystem.texi +++ /dev/null @@ -1,115 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c %**start of header -@setfilename filesystem -@syncodeindex vr fn -@synindex ky cp -@paragraphindent 0 -@c @smallbook -@c %**end of header - -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Master file for the Filesystem Design Guide -@c - -@include ../common/setup.texi - -@ignore -@ifinfo -@format -START-INFO-DIR-ENTRY -* RTEMS Filesystem Design Guide: -END-INFO-DIR-ENTRY -@end format -@end ifinfo -@end ignore - -@c -@c Title Page Stuff -@c - -@set edition @value{RTEMS-EDITION} -@set version @value{RTEMS-VERSION} -@set update-date @value{RTEMS-UPDATE-DATE} -@set update-month @value{RTEMS-UPDATE-MONTH} - -@c -@c I don't really like having a short title page. --joel -@c -@c @shorttitlepage RTEMS Filesystem Design Guide - -@setchapternewpage odd -@settitle RTEMS Filesystem Design Guide -@titlepage -@finalout - -@title RTEMS Filesystem Design Guide -@subtitle Edition @value{edition}, for RTEMS @value{version} -@sp 1 -@subtitle @value{update-month} -@author On-Line Applications Research Corporation -@page -@include ../common/cpright.texi -@end titlepage - -@c This prevents a black box from being printed on "overflow" lines. -@c The alternative is to rework a sentence to avoid this problem. - -@include preface.texi -@include patheval.texi -@include init.texi -@include mounting.texi -@include syscalls.texi -@include fsrequirements.texi -@include imfs.texi -@include miniimfs.texi -@include tftp.texi -@ifinfo -@node Top, Preface, (dir), (dir) -@top filesystem - -This is the online version of the RTEMS Filesystem Design Guide. - -@menu -* Preface:: -* Pathname Evaluation:: -* System Initialization:: -* Mounting and Unmounting Filesystems:: -* System Call Development Notes:: -* Filesystem Implementation Requirements:: -* In-Memory Filesystem:: -* Miniature In-Memory Filesystem:: -* Trivial FTP Client Filesystem:: -* Command and Variable Index:: -* Concept Index:: -@end menu - -@end ifinfo -@c -@c -@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here -@c - -@node Command and Variable Index, Concept Index, , Top -@unnumbered Command and Variable Index - -There are currently no Command and Variable Index entries. - -@c @printindex fn - -@node Concept Index, , Command and Variable Index, Top -@unnumbered Concept Index - -There are currently no Concept Index entries. -@c @printindex cp - -@contents -@bye - diff --git a/doc/filesystem/fsrequirements.t b/doc/filesystem/fsrequirements.t deleted file mode 100644 index 5ce4e86c61..0000000000 --- a/doc/filesystem/fsrequirements.t +++ /dev/null @@ -1,1183 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - - -@chapter Filesystem Implementation Requirements - -This chapter details the behavioral requirements that all filesystem -implementations must adhere to. - -@section General - -The RTEMS filesystem framework was intended to be compliant with the -POSIX Files and Directories interface standard. The following filesystem -characteristics resulted in a functional switching layer. - -@example -Figure of the Filesystem Functional Layering goes here. -This figure includes networking and disk caching layering. -@end example - -@ifset use-ascii -@example -@group -@end group -@end example -@end ifset - -@ifset use-tex -@c @image{FunctionalLayerCake,6in,4in} -@end ifset - -@ifset use-html -@end ifset - -@enumerate - -@item Application programs are presented with a standard set of POSIX -compliant functions that allow them to interface with the files, devices -and directories in the filesystem. The interfaces to these routines do -not reflect the type of subordinate filesystem implementation in which -the file will be found. - -@item The filesystem framework developed under RTEMS allows for mounting -filesystem of different types under the base filesystem. - -@item The mechanics of locating file information may be quite different -between filesystem types. - -@item The process of locating a file may require crossing filesystem -boundaries. - -@item The transitions between filesystem and the processing required to -access information in different filesystem is not visible at the level -of the POSIX function call. - -@item The POSIX interface standard provides file access by character -pathname to the file in some functions and through an integer file -descriptor in other functions. - -@item The nature of the integer file descriptor and its associated -processing is operating system and filesystem specific. - -@item Directory and device information must be processed with some of the -same routines that apply to files. - -@item The form and content of directory and device information differs -greatly from that of a regular file. - -@item Files, directories and devices represent elements (nodes) of a tree -hierarchy. - -@item The rules for processing each of the node types that exist under the -filesystem are node specific but are still not reflected in the POSIX -interface routines. - -@end enumerate - - -@example -Figure of the Filesystem Functional Layering goes here. -This figure focuses on the Base Filesystem and IMFS. -@end example - -@example -Figure of the IMFS Memfile control blocks -@end example - -@section File and Directory Removal Constraints - -The following POSIX constraints must be honored by all filesystems. - -@itemize @bullet - -@item If a node is a directory with children it cannot be removed. - -@item The root node of any filesystem, whether the base filesystem or a -mounted filesystem, cannot be removed. - -@item A node that is a directory that is acting as the mount point of a file -system cannot be removed. - -@item On filesystems supporting hard links, a link count is maintained. -Prior to node removal, the node's link count is decremented by one. The -link count must be less than one to allow for removal of the node. - -@end itemize - -@c -@c -@c -@section API Layering - -@subsection Mapping of Generic System Calls to Filesystem Specific Functions - -The list of generic system calls includes the routines open(), read(), -write(), close(), etc.. - -The Files and Directories section of the POSIX Application Programs -Interface specifies a set of functions with calling arguments that are -used to gain access to the information in a filesystem. To the -application program, these functions allow access to information in any -mounted filesystem without explicit knowledge of the filesystem type or -the filesystem mount configuration. The following are functions that are -provided to the application: - -@enumerate -@item access() -@item chdir() -@item chmod() -@item chown() -@item close() -@item closedir() -@item fchmod() -@item fcntl() -@item fdatasync() -@item fpathconf() -@item fstat() -@item fsync() -@item ftruncate() -@item link() -@item lseek() -@item mkdir() -@item mknod() -@item mount() -@item open() -@item opendir() -@item pathconf() -@item read() -@item readdir() -@item rewinddir() -@item rmdir() -@item rmnod() -@item scandir() -@item seekdir() -@item stat() -@item telldir() -@item umask() -@item unlink() -@item unmount() -@item utime() -@item write() -@end enumerate - -The filesystem's type as well as the node type within the filesystem -determine the nature of the processing that must be performed for each of -the functions above. The RTEMS filesystem provides a framework that -allows new filesystem to be developed and integrated without alteration -to the basic framework. - -To provide the functional switching that is required, each of the POSIX -file and directory functions have been implemented as a shell function. -The shell function adheres to the POSIX interface standard. Within this -functional shell, filesystem and node type information is accessed which -is then used to invoke the appropriate filesystem and node type specific -routine to process the POSIX function call. - -@subsection File/Device/Directory function access via file control block - rtems_libio_t structure - -The POSIX open() function returns an integer file descriptor that is used -as a reference to file control block information for a specific file. The -file control block contains information that is used to locate node, file -system, mount table and functional handler information. The diagram in -Figure 8 depicts the relationship between and among the following -components. - -@enumerate - -@item File Descriptor Table - -This is an internal RTEMS structure that tracks all currently defined file -descriptors in the system. The index that is returned by the file open() -operation references a slot in this table. The slot contains a pointer to -the file descriptor table entry for this file. The rtems_libio_t structure -represents the file control block. - -@item Allocation of entry in the File Descriptor Table - -Access to the file descriptor table is controlled through a semaphore that -is implemented using the rtems_libio_allocate() function. This routine -will grab a semaphore and then scan the file control blocks to determine -which slot is free for use. The first free slot is marked as used and the -index to this slot is returned as the file descriptor for the open() -request. After the alterations have been made to the file control block -table, the semaphore is released to allow further operations on the table. - -@item Maximum number of entries in the file descriptor table is -configurable through the src/exec/sapi/headers/confdefs.h file. If the -CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS constant is defined its value -will represent the maximum number of file descriptors that are allowed. -If CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS is not specified a default -value of 20 will be used as the maximum number of file descriptors -allowed. - -@item File control block - rtems_libio_t structure - -@example -struct rtems_libio_tt @{ - rtems_driver_name_t *driver; - off_t size; - off_t offset; - unsigned32 flags; - rtems_filesystem_location_info_t pathinfo; - Objects_Id sem; - unsigned32 data0; - void data1; - void file_info; - rtems_filesystem_file_handlers_r handlers; -@}; -@end example - -A file control block can exist for regular files, devices and directories. -The following fields are important for regular file and directory access: - -@itemize @bullet - -@item Size - For a file this represents the number of bytes currently -stored in a file. For a directory this field is not filled in. - -@item Offset - For a file this is the byte file position index relative to -the start of the file. For a directory this is the byte offset into a -sequence of dirent structures. - -@item Pathinfo - This is a structure that provides a pointer to node -information, OPS table functions, Handler functions and the mount table -entry associated with this node. - -@item file_info - A pointer to node information that is used by Handler -functions - -@item handlers - A pointer to a table of handler functions that operate on -a file, device or directory through a file descriptor index - -@end itemize - -@end enumerate - -@subsection File/Directory function access via rtems_filesystem_location_info_t structure - -The rtems_filesystem_location_info_tt structure below provides sufficient -information to process nodes under a mounted filesystem. - -@example -struct rtems_filesystem_location_info_tt @{ - void *node_access; - rtems_filesystem_file_handlers_r *handlers; - rtems_filesystem_operations_table *ops; - rtems_filesystem_mount_table_entry_t *mt_entry; -@}; -@end example - -It contains a void pointer to filesystem specific nodal structure, -pointers to the OPS table for the filesystem that contains the node, the -node type specific handlers for the node and a reference pointer to the -mount table entry associated with the filesystem containing the node - -@section Operation Tables - -Filesystem specific operations are invoked indirectly. The set of -routines that implement the filesystem are configured into two tables. -The Filesystem Handler Table has routines that are specific to a -filesystem but remain constant regardless of the actual file type. -The File Handler Table has routines that are both filesystem and file type -specific. - -@subsection Filesystem Handler Table Functions - -OPS table functions are defined in a @code{rtems_filesystem_operations_table} -structure. It defines functions that are specific to a given filesystem. -One table exists for each filesystem that is supported in the RTEMS -configuration. The structure definition appears below and is followed by -general developmental information on each of the functions contained in this -function management structure. - -@example -typedef struct @{ - rtems_filesystem_evalpath_t evalpath; - rtems_filesystem_evalmake_t evalformake; - rtems_filesystem_link_t link; - rtems_filesystem_unlink_t unlink; - rtems_filesystem_node_type_t node_type; - rtems_filesystem_mknod_t mknod; - rtems_filesystem_rmnod_t rmnod; - rtems_filesystem_chown_t chown; - rtems_filesystem_freenode_t freenod; - rtems_filesystem_mount_t mount; - rtems_filesystem_fsmount_me_t fsmount_me; - rtems_filesystem_unmount_t unmount; - rtems_filesystem_fsunmount_me_t fsunmount_me; - rtems_filesystem_utime_t utime; - rtems_filesystem_evaluate_link_t eval_link; - rtems_filesystem_symlink_t symlink; -@} rtems_filesystem_operations_table; -@end example - -@c -@c -@c -@c @page - -@subsubsection evalpath Handler - -@subheading Corresponding Structure Element: - -evalpath - -@subheading Arguments: - -@example - const char *pathname, /* IN */ - int flags, /* IN */ - rtems_filesystem_location_info_t *pathloc /* IN/OUT */ -@end example - -@subheading Description: - -This routine is responsible for evaluating the pathname passed in -based upon the flags and the valid @code{rthems_filesystem_location_info_t}. -Additionally, it must make any changes to pathloc necessary to identify -the pathname node. This should include calling the evalpath for a mounted -filesystem, if the given filesystem supports the mount command. - -This routine returns a 0 if the evaluation was successful. -Otherwise, it returns a -1 and sets errno to the correct error. - -This routine is required and should NOT be set to NULL. - -@c -@c -@c -@c @page - -@subsubsection evalformake Handler - -@subheading Corresponding Structure Element: - -evalformake - -@subheading Arguments: - -@example - const char *path, /* IN */ - rtems_filesystem_location_info_t *pathloc, /* IN/OUT */ - const char **name /* OUT */ -@end example - -@subheading Description: - -This method is given a path to evaluate and a valid start location. It -is responsible for finding the parent node for a requested make command, -setting pathloc information to identify the parent node, and setting -the name pointer to the first character of the name of the new node. -Additionally, if the filesystem supports the mount command, this method -should call the evalformake routine for the mounted filesystem. - -This routine returns a 0 if the evaluation was successful. Otherwise, it -returns a -1 and sets errno to the correct error. - -This routine is required and should NOT be set to NULL. However, if -the filesystem does not support user creation of a new node, it may -set errno to ENOSYS and return -1. - -@c -@c -@c -@c @page - -@subsubsection link Handler - -@subheading Corresponding Structure Element: - -link - -@subheading Arguments: - - -@example -rtems_filesystem_location_info_t *to_loc, /* IN */ -rtems_filesystem_location_info_t *parent_loc, /* IN */ -const char *token /* IN */ -@end example - -@subheading Description: - - -This routine is used to create a hard-link. - -It will first examine the st_nlink count of the node that we are trying to. -If the link count exceeds LINK_MAX an error will be returned. - -The name of the link will be normalized to remove extraneous separators from -the end of the name. - -This routine is not required and may be set to NULL. - -@c -@c -@c -@c @page - -@subsubsection unlink Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection node_type Handler - -@subheading Corresponding Structure Element: - -node_type() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -@end example - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection mknod Handler - -@subheading Corresponding Structure Element: - -mknod() - -@subheading Arguments: - -@example -const char *token, /* IN */ -mode_t mode, /* IN */ -dev_t dev, /* IN */ -rtems_filesystem_location_info_t *pathloc /* IN/OUT */ -@end example - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection rmnod Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection chown Handler - -@subheading Corresponding Structure Element: - -chown() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -uid_t owner /* IN */ -gid_t group /* IN */ -@end example - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection freenod Handler - -@subheading Corresponding Structure Element: - -freenod() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -@end example - -@subheading Description: - -This routine is used by the generic code to allow memory to be allocated -during the evaluate routines, and set free when the generic code is finished -accessing a node. If the evaluate routines allocate memory to identify -a node this routine should be utilized to free that memory. - -This routine is not required and may be set to NULL. - -@c -@c -@c -@c @page - -@subsubsection mount Handler - -@subheading Corresponding Structure Element: - -mount() - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection fsmount_me Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading Description: - -This function is provided with a filesystem to take care of the internal -filesystem management details associated with mounting that filesystem -under the RTEMS environment. - -It is not responsible for the mounting details associated the filesystem -containing the mount point. - -The rtems_filesystem_mount_table_entry_t structure contains the key elements -below: - -rtems_filesystem_location_info_t *mt_point_node, - -This structure contains information about the mount point. This -allows us to find the ops-table and the handling functions -associated with the filesystem containing the mount point. - -rtems_filesystem_location_info_t *fs_root_node, - -This structure contains information about the root node in the file -system to be mounted. It allows us to find the ops-table and the -handling functions associated with the filesystem to be mounted. - -rtems_filesystem_options_t options, - -Read only or read/write access - -void *fs_info, - -This points to an allocated block of memory the will be used to -hold any filesystem specific information of a global nature. This -allocated region if important because it allows us to mount the -same filesystem type more than once under the RTEMS system. -Each instance of the mounted filesystem has its own set of global -management information that is separate from the global -management information associated with the other instances of the -mounted filesystem type. - -rtems_filesystem_limits_and_options_t pathconf_info, - -The table contains the following set of values associated with the -mounted filesystem: - -@itemize @bullet - -@item link_max - -@item max_canon - -@item max_input - -@item name_max - -@item path_max - -@item pipe_buf - -@item posix_async_io - -@item posix_chown_restrictions - -@item posix_no_trunc - -@item posix_prio_io - -@item posix_sync_io - -@item posix_vdisable - -@end itemize - -These values are accessed with the pathconf() and the fpathconf () -functions. - -const char *dev - -The is intended to contain a string that identifies the device that contains -the filesystem information. The filesystems that are currently implemented -are memory based and don't require a device specification. - -If the mt_point_node.node_access is NULL then we are mounting the base file -system. - -The routine will create a directory node for the root of the IMFS file -system. - -The node will have read, write and execute permissions for owner, group and -others. - -The node's name will be a null string. - -A filesystem information structure(fs_info) will be allocated and -initialized for the IMFS filesystem. The fs_info pointer in the mount table -entry will be set to point the filesystem information structure. - -The pathconf_info element of the mount table will be set to the appropriate -table of path configuration constants (LIMITS_AND_OPTIONS). - -The fs_root_node structure will be filled in with the following: - -@itemize @bullet - -@item pointer to the allocated root node of the filesystem - -@item directory handlers for a directory node under the IMFS filesystem - -@item OPS table functions for the IMFS - -@end itemize - -A 0 will be returned to the calling routine if the process succeeded, -otherwise a 1 will be returned. - - -@c -@c -@c -@c @page - -@subsubsection unmount Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection fsunmount_me Handler - -@subheading Corresponding Structure Element: - -imfs_fsunmount_me() - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection utime Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection eval_link Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection symlink Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page -@subsection File Handler Table Functions - -Handler table functions are defined in a @code{rtems_filesystem_file_handlers_r} -structure. It defines functions that are specific to a node type in a given -filesystem. One table exists for each of the filesystem's node types. The -structure definition appears below. It is followed by general developmental -information on each of the functions associated with regular files contained -in this function management structure. - -@example -typedef struct @{ - rtems_filesystem_open_t open; - rtems_filesystem_close_t close; - rtems_filesystem_read_t read; - rtems_filesystem_write_t write; - rtems_filesystem_ioctl_t ioctl; - rtems_filesystem_lseek_t lseek; - rtems_filesystem_fstat_t fstat; - rtems_filesystem_fchmod_t fchmod; - rtems_filesystem_ftruncate_t ftruncate; - rtems_filesystem_fpathconf_t fpathconf; - rtems_filesystem_fsync_t fsync; - rtems_filesystem_fdatasync_t fdatasync; - rtems_filesystem_fcntl_t fcntl; -@} rtems_filesystem_file_handlers_r; -@end example - -@c -@c -@c -@c @page - -@subsubsection open Handler - -@subheading Corresponding Structure Element: - -open() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -const char *pathname, -unsigned32 flag, -unsigned32 mode -@end example - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection close Handler - -@subheading Corresponding Structure Element: - -close() - -@subheading Arguments: - -@example -rtems_libio_t *iop -@end example - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - - - -@c -@c -@c -@c @page - -@subsubsection read Handler - -@subheading Corresponding Structure Element: - -read() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -void *buffer, -unsigned32 count -@end example - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection write Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection ioctl Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -@example -rtems_libio_t *iop, -unsigned32 command, -void *buffer -@end example - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection lseek Handler - -@subheading Corresponding Structure Element: - -lseek() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -off_t offset, -int whence -@end example - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection fstat Handler - -@subheading Corresponding Structure Element: - -fstat() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *loc, -struct stat *buf -@end example - -@subheading Description: - -The following information is extracted from the filesystem -specific node and placed in the @code{stat} structure: - -@itemize @bullet - -@item st_mode - -@item st_nlink - -@item st_ino - -@item st_uid - -@item st_gid - -@item st_atime - -@item st_mtime - -@item st_ctime - -@end itemize - - -@subheading NOTES: - -Both the @code{stat()} and @code{lstat()} services are -implemented directly using the @code{fstat()} handler. The -difference in behavior is determined by how the path is evaluated -prior to this handler being called on a particular -file entity. - -The @code{fstat()} system call is implemented directly -on top of this filesystem handler. - -@c -@c -@c -@c @page - -@subsubsection fchmod Handler - -@subheading Corresponding Structure Element: - -fchmod() - -@subheading Arguments: - -@example -rtems_libio_t *iop -mode_t mode -@end example - -@subheading Description: - -XXX - - -@subheading NOTES: - -XXX - -@c -@c -@c -@c @page - -@subsubsection ftruncate Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - -@subsubsection fpathconf Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - -@c -@c -@c -@c @page - -@subsubsection fsync Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - -@c -@c -@c -@c @page - -@subsubsection fdatasync Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX - -@c -@c -@c -@c @page - -@subsubsection fcntl Handler - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading Description: - -XXX - -@subheading NOTES: - -XXX diff --git a/doc/filesystem/imfs.t b/doc/filesystem/imfs.t deleted file mode 100644 index 1ba18edb88..0000000000 --- a/doc/filesystem/imfs.t +++ /dev/null @@ -1,2038 +0,0 @@ -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter In-Memory Filesystem - -This chapter describes the In-Memory FileSystem (IMFS). The IMFS is a -full featured POSIX filesystem that keeps all information in memory. - -@section IMFS Per Node Data Structure - -Each regular file, device, hard link, and directory is represented by a data -structure called a @code{jnode}. The @code{jnode} is formally represented by the -structure: - -@example -struct IMFS_jnode_tt @{ - Chain_Node Node; /* for chaining them together */ - IMFS_jnode_t *Parent; /* Parent node */ - char name[NAME_MAX+1]; /* "basename" */ - mode_t st_mode; /* File mode */ - nlink_t st_nlink; /* Link count */ - ino_t st_ino; /* inode */ - - uid_t st_uid; /* User ID of owner */ - gid_t st_gid; /* Group ID of owner */ - time_t st_atime; /* Time of last access */ - time_t st_mtime; /* Time of last modification */ - time_t st_ctime; /* Time of last status change */ - IMFS_jnode_types_t type; /* Type of this entry */ - IMFS_typs_union info; -@}; -@end example - -The key elements of this structure are listed below together with a brief -explanation of their role in the filesystem. - -@table @b - -@item Node -exists to allow the entire @code{jnode} structure to be included in a chain. - -@item Parent -is a pointer to another @code{jnode} structure that is the logical parent of the -node in which it appears. This field may be NULL if the file associated with -this node is deleted but there are open file descriptors on this file or -there are still hard links to this node. - -@item name -is the name of this node within the filesystem hierarchical tree. Example: If -the fully qualified pathname to the @code{jnode} was @code{/a/b/c}, the -@code{jnode} name field would contain the null terminated string @code{"c"}. - -@item st_mode -is the standard Unix access permissions for the file or directory. - -@item st_nlink -is the number of hard links to this file. When a @code{jnode} is first created -its link count is set to 1. A @code{jnode} and its associated resources -cannot be deleted unless its link count is less than 1. - -@item st_ino -is a unique node identification number - -@item st_uid -is the user ID of the file's owner - -@item st_gid -is the group ID of the file's owner - -@item st_atime -is the time of the last access to this file - -@item st_mtime -is the time of the last modification of this file - -@item st_ctime -is the time of the last status change to the file - -@item type -is the indication of node type must be one of the following states: - -@itemize @bullet -@item IMFS_DIRECTORY -@item IMFS_MEMORY_FILE -@item IMFS_HARD_LINK -@item IMFS_SYM_LINK -@item IMFS_DEVICE -@end itemize - - -@item info -is this contains a structure that is unique to file type (See IMFS_typs_union -in imfs.h). - -@itemize @bullet - -@item IMFS_DIRECTORY - -An IMFS directory contains a dynamic chain structure that -records all files and directories that are subordinate to the directory node. - -@item IMFS_MEMORY_FILE - -Under the in memory filesystem regular files hold data. Data is dynamically -allocated to the file in 128 byte chunks of memory. The individual chunks of -memory are tracked by arrays of pointers that record the address of the -allocated chunk of memory. Single, double, and triple indirection pointers -are used to record the locations of all segments of the file. The -memory organization of an IMFS file are discussed elsewhere in this manual. - -@item IMFS_HARD_LINK - -The IMFS filesystem supports the concept of hard links to other nodes in the -IMFS filesystem. These hard links are actual pointers to other nodes in the -same filesystem. This type of link cannot cross-filesystem boundaries. - -@item IMFS_SYM_LINK - -The IMFS filesystem supports the concept of symbolic links to other nodes in -any filesystem. A symbolic link consists of a pointer to a character string -that represents the pathname to the target node. This type of link can -cross-filesystem boundaries. Just as with most versions of UNIX supporting -symbolic links, a symbolic link can point to a non-existent file. - -@item IMFS_DEVICE - -All RTEMS devices now appear as files under the in memory filesystem. On -system initialization, all devices are registered as nodes under the file -system. - -@end itemize - -@end table - -@section Miscellaneous IMFS Information - -@section Memory associated with the IMFS - -A memory based filesystem draws its resources for files and directories -from the memory resources of the system. When it is time to un-mount the -filesystem, the memory resources that supported filesystem are set free. -In order to free these resources, a recursive walk of the filesystems -tree structure will be performed. As the leaf nodes under the filesystem -are encountered their resources are freed. When directories are made empty -by this process, their resources are freed. - -@subsection Node removal constraints for the IMFS - -The IMFS conforms to the general filesystem requirements for node -removal. See @ref{File and Directory Removal Constraints}. - -@subsection IMFS General Housekeeping Notes - -The following is a list of odd housekeeping notes for the IMFS. - -@itemize @bullet - -@item If the global variable rtems_filesystem_current refers to the node that -we are trying to remove, the node_access element of this structure must be -set to NULL to invalidate it. - -@item If the node was of IMFS_MEMORY_FILE type, free the memory associated -with the memory file before freeing the node. Use the IMFS_memfile_remove() -function. - -@end itemize - -@section IMFS Operation Tables - -@subsection IMFS Filesystem Handler Table Functions - -OPS table functions are defined in a rtems_filesystem_operations_table -structure. It defines functions that are specific to a given filesystem. -One table exists for each filesystem that is supported in the RTEMS -configuration. The structure definition appears below and is followed by -general developmental information on each of the functions contained in this -function management structure. - -@example -rtems_filesystem_operations_table IMFS_ops = @{ - IMFS_eval_path, - IMFS_evaluate_for_make, - IMFS_link, - IMFS_unlink, - IMFS_node_type, - IMFS_mknod, - IMFS_rmnod, - IMFS_chown, - IMFS_freenodinfo, - IMFS_mount, - IMFS_initialize, - IMFS_unmount, - IMFS_fsunmount, - IMFS_utime, - IMFS_evaluate_link, - IMFS_symlink, - IMFS_readlink -@}; -@end example - -@c -@c -@c -@c @page - -@subsubsection IMFS_evalpath() - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_evalformake() - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_link() - -@subheading Corresponding Structure Element: - -link - -@subheading Arguments: - - -@example -rtems_filesystem_location_info_t *to_loc, /* IN */ -rtems_filesystem_location_info_t *parent_loc, /* IN */ -const char *token /* IN */ -@end example - -@subheading File: - -imfs_link.c - -@subheading Description: - - -This routine is used in the IMFS filesystem to create a hard-link. - -It will first examine the st_nlink count of the node that we are trying to. -If the link count exceeds LINK_MAX an error will be returned. - -The name of the link will be normalized to remove extraneous separators from -the end of the name. - -IMFS_create_node will be used to create a filesystem node that will have the -following characteristics: - -@itemize @bullet - -@item parent that was determined in the link() function in file link.c - -@item Type will be set to IMFS_HARD_LINK - -@item name will be set to the normalized name - -@item mode of the hard-link will be set to the mode of the target node - -@end itemize - -If there was trouble allocating memory for the new node an error will be -returned. - -The st_nlink count of the target node will be incremented to reflect the new -link. - -The time fields of the link will be set to reflect the creation time of the -hard-link. - - -@c -@c -@c -@c @page - -@subsubsection IMFS_unlink() - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_node_type() - -@subheading Corresponding Structure Element: - -IMFS_node_type() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -@end example - -@subheading File: - -imfs_ntype.c - -@subheading Description: - -This routine will locate the IMFS_jnode_t structure that holds ownership -information for the selected node in the filesystem. - -This structure is pointed to by pathloc->node_access. - -The IMFS_jnode_t type element indicates one of the node types listed below: - -@itemize @bullet - -@item RTEMS_FILESYSTEM_DIRECTORY - -@item RTEMS_FILESYSTEM_DEVICE - -@item RTEMS_FILESYSTEM_HARD_LINK - -@item RTEMS_FILESYSTEM_MEMORY_FILE - -@end itemize - -@c -@c -@c -@c @page - -@subsubsection IMFS_mknod() - -@subheading Corresponding Structure Element: - -IMFS_mknod() - -@subheading Arguments: - -@example -const char *token, /* IN */ -mode_t mode, /* IN */ -dev_t dev, /* IN */ -rtems_filesystem_location_info_t *pathloc /* IN/OUT */ -@end example - -@subheading File: - -imfs_mknod.c - -@subheading Description: - -This routine will examine the mode argument to determine is we are trying to -create a directory, regular file and a device node. The creation of other -node types is not permitted and will cause an assert. - -Memory space will be allocated for a @code{jnode} and the node will be set up -according to the nodal type that was specified. The IMFS_create_node() -function performs the allocation and setup of the node. - -The only problem that is currently reported is the lack of memory when we -attempt to allocate space for the @code{jnode} (ENOMEN). - - -@c -@c -@c -@c @page - -@subsubsection IMFS_rmnod() - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_chown() - -@subheading Corresponding Structure Element: - -IMFS_chown() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -uid_t owner /* IN */ -gid_t group /* IN */ -@end example - -@subheading File: - -imfs_chown.c - -@subheading Description: - -This routine will locate the IMFS_jnode_t structure that holds ownership -information for the selected node in the filesystem. - -This structure is pointed to by pathloc->node_access. - -The st_uid and st_gid fields of the node are then modified. Since this is a -memory based filesystem, no further action is required to alter the -ownership of the IMFS_jnode_t structure. - - -@c -@c -@c -@c @page - -@subsubsection IMFS_freenod() - -@subheading Corresponding Structure Element: - -IMFS_freenod() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -@end example - -@subheading File: - -imfs_free.c - -@subheading Description: - -This method is a private function to the IMFS. It is called by IMFS routines -to free nodes that have been allocated. Examples of where this routine -may be called from are unlink and rmnod. - -Note: This routine should not be confused with the filesystem callback -freenod. The IMFS allocates memory until the node no longer exists. - -@c -@c -@c -@c @page - -@subsubsection IMFS_freenodinfo() - -@subheading Corresponding Structure Element: - -IMFS_freenodinfo() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *pathloc /* IN */ -@end example - -@subheading File: - -imfs_free.c - -@subheading Description: - -The In-Memory File System does not need to allocate memory during the -evaluate routines. Therefore, this routine simply routines PASS. - - -@c -@c -@c -@c @page - -@subsubsection IMFS_mount() - -@subheading Corresponding Structure Element: - -IMFS_mount() - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading File: - -imfs_mount.c - -@subheading Description: - -This routine provides the filesystem specific processing required to mount a -filesystem for the system that contains the mount point. It will determine -if the point that we are trying to mount onto is a node of IMFS_DIRECTORY -type. - -If it is the node's info element is altered so that the info.directory.mt_fs -element points to the mount table chain entry that is associated with the -mounted filesystem at this point. The info.directory.mt_fs element can be -examined to determine if a filesystem is mounted at a directory. If it is -NULL, the directory does not serve as a mount point. A non-NULL entry -indicates that the directory does serve as a mount point and the value of -info.directory.mt_fs can be used to locate the mount table chain entry that -describes the filesystem mounted at this point. - - -@c -@c -@c -@c @page - -@subsubsection IMFS_fsmount_me() - -@subheading Corresponding Structure Element: - -IMFS_initialize() - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading File: - -imfs_init.c - -@subheading Description: - -This function is provided with a filesystem to take care of the internal -filesystem management details associated with mounting that filesystem -under the RTEMS environment. - -It is not responsible for the mounting details associated the filesystem -containing the mount point. - -The rtems_filesystem_mount_table_entry_t structure contains the key elements -below: - -rtems_filesystem_location_info_t *mt_point_node, - -This structure contains information about the mount point. This -allows us to find the ops-table and the handling functions -associated with the filesystem containing the mount point. - -rtems_filesystem_location_info_t *fs_root_node, - -This structure contains information about the root node in the file -system to be mounted. It allows us to find the ops-table and the -handling functions associated with the filesystem to be mounted. - -rtems_filesystem_options_t options, - -Read only or read/write access - -void *fs_info, - -This points to an allocated block of memory the will be used to -hold any filesystem specific information of a global nature. This -allocated region if important because it allows us to mount the -same filesystem type more than once under the RTEMS system. -Each instance of the mounted filesystem has its own set of global -management information that is separate from the global -management information associated with the other instances of the -mounted filesystem type. - -rtems_filesystem_limits_and_options_t pathconf_info, - -The table contains the following set of values associated with the -mounted filesystem: - -@itemize @bullet - -@item link_max - -@item max_canon - -@item max_input - -@item name_max - -@item path_max - -@item pipe_buf - -@item posix_async_io - -@item posix_chown_restrictions - -@item posix_no_trunc - -@item posix_prio_io - -@item posix_sync_io - -@item posix_vdisable - -@end itemize - -These values are accessed with the pathconf() and the fpathconf () -functions. - -const char *dev - -The is intended to contain a string that identifies the device that contains -the filesystem information. The filesystems that are currently implemented -are memory based and don't require a device specification. - -If the mt_point_node.node_access is NULL then we are mounting the base file -system. - -The routine will create a directory node for the root of the IMFS file -system. - -The node will have read, write and execute permissions for owner, group and -others. - -The node's name will be a null string. - -A filesystem information structure(fs_info) will be allocated and -initialized for the IMFS filesystem. The fs_info pointer in the mount table -entry will be set to point the filesystem information structure. - -The pathconf_info element of the mount table will be set to the appropriate -table of path configuration constants ( IMFS_LIMITS_AND_OPTIONS ). - -The fs_root_node structure will be filled in with the following: - -@itemize @bullet - -@item pointer to the allocated root node of the filesystem - -@item directory handlers for a directory node under the IMFS filesystem - -@item OPS table functions for the IMFS - -@end itemize - -A 0 will be returned to the calling routine if the process succeeded, -otherwise a 1 will be returned. - - -@c -@c -@c -@c @page - -@subsubsection IMFS_unmount() - -@subheading Corresponding Structure Element: - -IMFS_unmount() - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading File: - -imfs_unmount.c - -@subheading Description: - -This routine allows the IMFS to unmount a filesystem that has been -mounted onto a IMFS directory. - -The mount entry mount point node access is verified to be a mounted -directory. It's mt_fs is set to NULL. This identifies to future -calles into the IMFS that this directory node is no longer a mount -point. Additionally, it will allow any directories that were hidden -by the mounted system to again become visible. - -@c -@c -@c -@c @page - -@subsubsection IMFS_fsunmount() - -@subheading Corresponding Structure Element: - -imfs_fsunmount() - -@subheading Arguments: - -@example -rtems_filesystem_mount_table_entry_t *mt_entry -@end example - -@subheading File: - -imfs_init.c - -@subheading Description: - -This method unmounts this instance of the IMFS file system. It is the -counterpart to the IMFS_initialize routine. It is called by the generic -code under the fsunmount_me callback. - -All method loops finding the first encountered node with no children and -removing the node from the tree, thus returning allocated resources. This -is done until all allocated nodes are returned. - -@c -@c -@c -@c @page - -@subsubsection IMFS_utime() - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_eval_link() - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page -@subsection Regular File Handler Table Functions - -Handler table functions are defined in a rtems_filesystem_file_handlers_r -structure. It defines functions that are specific to a node type in a given -filesystem. One table exists for each of the filesystem's node types. The -structure definition appears below. It is followed by general developmental -information on each of the functions associated with regular files contained -in this function management structure. - -@example -rtems_filesystem_file_handlers_r IMFS_memfile_handlers = @{ - memfile_open, - memfile_close, - memfile_read, - memfile_write, - memfile_ioctl, - memfile_lseek, - IMFS_stat, - IMFS_fchmod, - memfile_ftruncate, - NULL, /* fpathconf */ - NULL, /* fsync */ - IMFS_fdatasync, - IMFS_fcntl -@}; -@end example - - -@c -@c -@c -@c @page - -@subsubsection memfile_open() for Regular Files - -@subheading Corresponding Structure Element: - -memfile_open() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -const char *pathname, -unsigned32 flag, -unsigned32 mode -@end example - -@subheading File: - -memfile.c - -@subheading Description: - -Currently this function is a shell. No meaningful processing is performed and -a success code is always returned. - -@c -@c -@c -@c @page - -@subsubsection memfile_close() for Regular Files - -@subheading Corresponding Structure Element: - -memfile_close() - -@subheading Arguments: - -@example -rtems_libio_t *iop -@end example - -@subheading File: - -memfile.c - -@subheading Description: - -This routine is a dummy for regular files under the base filesystem. It -performs a capture of the IMFS_jnode_t pointer from the file control block -and then immediately returns a success status. - - -@c -@c -@c -@c @page - -@subsubsection memfile_read() for Regular Files - -@subheading Corresponding Structure Element: - -memfile_read() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -void *buffer, -unsigned32 count -@end example - -@subheading File: - -memfile.c - -@subheading Description: - -This routine will determine the @code{jnode} that is associated with this file. - -It will then call IMFS_memfile_read() with the @code{jnode}, file position index, -buffer and transfer count as arguments. - -IMFS_memfile_read() will do the following: - -@itemize @bullet - -@item Verify that the @code{jnode} is associated with a memory file - -@item Verify that the destination of the read is valid - -@item Adjust the length of the read if it is too long - -@item Acquire data from the memory blocks associated with the file - -@item Update the access time for the data in the file - -@end itemize - -@c -@c -@c -@c @page - -@subsubsection memfile_write() for Regular Files - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection memfile_ioctl() for Regular Files - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -@example -rtems_libio_t *iop, -unsigned32 command, -void *buffer -@end example - -@subheading File: - -memfile.c - -@subheading Description: - -The current code is a placeholder for future development. The routine returns -a successful completion status. - -@c -@c -@c -@c @page - -@subsubsection memfile_lseek() for Regular Files - -@subheading Corresponding Structure Element: - -Memfile_lseek() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -off_t offset, -int whence -@end example - -@subheading File: - -memfile.c - -@subheading Description: - -This routine make sure that the memory based file is sufficiently large to -allow for the new file position index. - -The IMFS_memfile_extend() function is used to evaluate the current size of -the memory file and allocate additional memory blocks if required by the new -file position index. A success code is always returned from this routine. - -@c -@c -@c -@c @page - -@subsubsection IMFS_stat() for Regular Files - -@subheading Corresponding Structure Element: - -IMFS_stat() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *loc, -struct stat *buf -@end example - -@subheading File: - -imfs_stat.c - -@subheading Description: - -This routine actually performs status processing for both devices and regular -files. - -The IMFS_jnode_t structure is referenced to determine the type of node under -the filesystem. - -If the node is associated with a device, node information is extracted and -transformed to set the st_dev element of the stat structure. - -If the node is a regular file, the size of the regular file is extracted from -the node. - -This routine rejects other node types. - -The following information is extracted from the node and placed in the stat -structure: - -@itemize @bullet - -@item st_mode - -@item st_nlink - -@item st_ino - -@item st_uid - -@item st_gid - -@item st_atime - -@item st_mtime - -@item st_ctime - -@end itemize - -@c -@c -@c -@c @page - -@subsubsection IMFS_fchmod() for Regular Files - -@subheading Corresponding Structure Element: - -IMFS_fchmod() - -@subheading Arguments: - -@example -rtems_libio_t *iop -mode_t mode -@end example - -@subheading File: - -imfs_fchmod.c - -@subheading Description: - -This routine will obtain the pointer to the IMFS_jnode_t structure from the -information currently in the file control block. - -Based on configuration the routine will acquire the user ID from a call to -getuid() or from the IMFS_jnode_t structure. - -It then checks to see if we have the ownership rights to alter the mode of -the file. If the caller does not, an error code is returned. - -An additional test is performed to verify that the caller is not trying to -alter the nature of the node. If the caller is attempting to alter more than -the permissions associated with user group and other, an error is returned. - -If all the preconditions are met, the user, group and other fields are set -based on the mode calling parameter. - -@c -@c -@c -@c @page - -@subsubsection memfile_ftruncate() for Regular Files - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@subsubsection No pathconf() for Regular Files - -@subheading Corresponding Structure Element: - -NULL - -@subheading Arguments: - -Not Implemented - -@subheading File: - -Not Implemented - -@subheading Description: - -Not Implemented - - -@c -@c -@c -@c @page - -@subsubsection No fsync() for Regular Files - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_fdatasync() for Regular Files - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page -@subsection Directory Handler Table Functions - -Handler table functions are defined in a rtems_filesystem_file_handlers_r -structure. It defines functions that are specific to a node type in a given -filesystem. One table exists for each of the filesystem's node types. The -structure definition appears below. It is followed by general developmental -information on each of the functions associated with directories contained in -this function management structure. - -@example -rtems_filesystem_file_handlers_r IMFS_directory_handlers = @{ - IMFS_dir_open, - IMFS_dir_close, - IMFS_dir_read, - NULL, /* write */ - NULL, /* ioctl */ - IMFS_dir_lseek, - IMFS_dir_fstat, - IMFS_fchmod, - NULL, /* ftruncate */ - NULL, /* fpathconf */ - NULL, /* fsync */ - IMFS_fdatasync, - IMFS_fcntl -@}; -@end example - - -@c -@c -@c -@c @page -@subsubsection IMFS_dir_open() for Directories - -@subheading Corresponding Structure Element: - -imfs_dir_open() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -const char *pathname, -unsigned32 flag, -unsigned32 mode -@end example - -@subheading File: - -imfs_directory.c - -@subheading Description: - -This routine will look into the file control block to find the @code{jnode} that -is associated with the directory. - -The routine will verify that the node is a directory. If its not a directory -an error code will be returned. - -If it is a directory, the offset in the file control block will be set to 0. -This allows us to start reading at the beginning of the directory. - -@c -@c -@c -@c @page - -@subsubsection IMFS_dir_close() for Directories - -@subheading Corresponding Structure Element: - -imfs_dir_close() - -@subheading Arguments: - -@example -rtems_libio_t *iop -@end example - -@subheading File: - -imfs_directory.c - -@subheading Description: - -This routine is a dummy for directories under the base filesystem. It -immediately returns a success status. - -@c -@c -@c -@c @page - -@subsubsection IMFS_dir_read() for Directories - -@subheading Corresponding Structure Element: - -imfs_dir_read - -@subheading Arguments: - -@example -rtems_libio_t *iop, -void *buffer, -unsigned32 count -@end example - -@subheading File: - -imfs_directory.c - -@subheading Description: - -This routine will read a fixed number of directory entries from the current -directory offset. The number of directory bytes read will be returned from -this routine. - - -@c -@c -@c -@c @page - -@subsubsection No write() for Directories - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection No ioctl() for Directories - -@subheading Corresponding Structure Element: - -ioctl - -@subheading Arguments: - - -@subheading File: - -Not supported - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection IMFS_dir_lseek() for Directories - -@subheading Corresponding Structure Element: - -imfs_dir_lseek() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -off_t offset, -int whence -@end example - -@subheading File: - -imfs_directory.c - -@subheading Description: - -This routine alters the offset in the file control block. - -No test is performed on the number of children under the current open -directory. The imfs_dir_read() function protects against reads beyond the -current size to the directory by returning a 0 bytes transfered to the -calling programs whenever the file position index exceeds the last entry in -the open directory. - -@c -@c -@c -@c @page - -@subsubsection IMFS_dir_fstat() for Directories - -@subheading Corresponding Structure Element: - -imfs_dir_fstat() - -@subheading Arguments: - - -@example -rtems_filesystem_location_info_t *loc, -struct stat *buf -@end example - -@subheading File: - -imfs_directory.c - -@subheading Description: - -The node access information in the rtems_filesystem_location_info_t structure -is used to locate the appropriate IMFS_jnode_t structure. The following -information is taken from the IMFS_jnode_t structure and placed in the stat -structure: - -@itemize @bullet -@item st_ino -@item st_mode -@item st_nlink -@item st_uid -@item st_gid -@item st_atime -@item st_mtime -@item st_ctime -@end itemize - -The st_size field is obtained by running through the chain of directory -entries and summing the sizes of the dirent structures associated with each -of the children of the directory. - -@c -@c -@c -@c @page - -@subsubsection IMFS_fchmod() for Directories - -@subheading Corresponding Structure Element: - -IMFS_fchmod() - -@subheading Arguments: - -@example -rtems_libio_t *iop -mode_t mode -@end example - -@subheading File: - -imfs_fchmod.c - -@subheading Description: - -This routine will obtain the pointer to the IMFS_jnode_t structure from the -information currently in the file control block. - -Based on configuration the routine will acquire the user ID from a call to -getuid() or from the IMFS_jnode_t structure. - -It then checks to see if we have the ownership rights to alter the mode of -the file. If the caller does not, an error code is returned. - -An additional test is performed to verify that the caller is not trying to -alter the nature of the node. If the caller is attempting to alter more than -the permissions associated with user group and other, an error is returned. - -If all the preconditions are met, the user, group and other fields are set -based on the mode calling parameter. - -@c -@c -@c -@c @page - -@subsubsection No ftruncate() for Directories - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection No fpathconf() for Directories - -@subheading Corresponding Structure Element: - -fpathconf - -@subheading Arguments: - -Not Implemented - -@subheading File: - -Not Implemented - -@subheading Description: - -Not Implemented - - -@c -@c -@c -@c @page - -@subsubsection No fsync() for Directories - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection IMFS_fdatasync() for Directories - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page -@subsection Device Handler Table Functions - -Handler table functions are defined in a rtems_filesystem_file_handlers_r -structure. It defines functions that are specific to a node type in a given -filesystem. One table exists for each of the filesystem's node types. The -structure definition appears below. It is followed by general developmental -information on each of the functions associated with devices contained in -this function management structure. - -@example -typedef struct @{ - rtems_filesystem_open_t open; - rtems_filesystem_close_t close; - rtems_filesystem_read_t read; - rtems_filesystem_write_t write; - rtems_filesystem_ioctl_t ioctl; - rtems_filesystem_lseek_t lseek; - rtems_filesystem_fstat_t fstat; - rtems_filesystem_fchmod_t fchmod; - rtems_filesystem_ftruncate_t ftruncate; - rtems_filesystem_fpathconf_t fpathconf; - rtems_filesystem_fsync_t fsync; - rtems_filesystem_fdatasync_t fdatasync; -@} rtems_filesystem_file_handlers_r; -@end example - -@c -@c -@c -@c @page - -@subsubsection device_open() for Devices - -@subheading Corresponding Structure Element: - -device_open() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -const char *pathname, -unsigned32 flag, -unsigned32 mode -@end example - -@subheading File: - -deviceio.c - -@subheading Description: - -This routine will use the file control block to locate the node structure for -the device. - -It will extract the major and minor device numbers from the @code{jnode}. - -The major and minor device numbers will be used to make a rtems_io_open() -function call to open the device driver. An argument list is sent to the -driver that contains the file control block, flags and mode information. - -@c -@c -@c -@c @page - -@subsubsection device_close() for Devices - -@subheading Corresponding Structure Element: - -device_close() - -@subheading Arguments: - -@example -rtems_libio_t *iop -@end example - -@subheading File: - -deviceio.c - -@subheading Description: - -This routine extracts the major and minor device driver numbers from the -IMFS_jnode_t that is referenced in the file control block. - -It also forms an argument list that contains the file control block. - -A rtems_io_close() function call is made to close the device specified by the -major and minor device numbers. - - -@c -@c -@c -@c @page - -@subsubsection device_read() for Devices - -@subheading Corresponding Structure Element: - -device_read() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -void *buffer, -unsigned32 count -@end example - -@subheading File: - -deviceio.c - -@subheading Description: - -This routine will extract the major and minor numbers for the device from the - -jnode- associated with the file descriptor. - -A rtems_io_read() call will be made to the device driver associated with the file -descriptor. The major and minor device number will be sent as arguments as well -as an argument list consisting of: - -@itemize @bullet -@item file control block - -@item file position index - -@item buffer pointer where the data read is to be placed - -@item count indicating the number of bytes that the program wishes to read -from the device - -@item flags from the file control block - -@end itemize - -On return from the rtems_io_read() the number of bytes that were actually -read will be returned to the calling program. - - -@c -@c -@c -@c @page - -@subsubsection device_write() for Devices - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection device_ioctl() for Devices - -@subheading Corresponding Structure Element: - -ioctl - -@subheading Arguments: - -@example -rtems_libio_t *iop, -unsigned32 command, -void *buffer -@end example - -@subheading File: - -deviceio.c - -@subheading Description: - -This handler will obtain status information about a device. - -The form of status is device dependent. - -The rtems_io_control() function uses the major and minor number of the device -to obtain the status information. - -rtems_io_control() requires an rtems_libio_ioctl_args_t argument list which -contains the file control block, device specific command and a buffer pointer -to return the device status information. - -The device specific command should indicate the nature of the information -that is desired from the device. - -After the rtems_io_control() is processed, the buffer should contain the -requested device information. - -If the device information is not obtained properly a -1 will be returned to -the calling program, otherwise the ioctl_return value is returned. - -@c -@c -@c -@c @page - -@subsubsection device_lseek() for Devices - -@subheading Corresponding Structure Element: - -device_lseek() - -@subheading Arguments: - -@example -rtems_libio_t *iop, -off_t offset, -int whence -@end example - -@subheading File: - -deviceio.c - -@subheading Description: - -At the present time this is a placeholder function. It always returns a -successful status. - -@c -@c -@c -@c @page - -@subsubsection IMFS_stat() for Devices - -@subheading Corresponding Structure Element: - -IMFS_stat() - -@subheading Arguments: - -@example -rtems_filesystem_location_info_t *loc, -struct stat *buf -@end example - -@subheading File: - -imfs_stat.c - -@subheading Description: - -This routine actually performs status processing for both devices and regular files. - -The IMFS_jnode_t structure is referenced to determine the type of node under the -filesystem. - -If the node is associated with a device, node information is extracted and -transformed to set the st_dev element of the stat structure. - -If the node is a regular file, the size of the regular file is extracted from the node. - -This routine rejects other node types. - -The following information is extracted from the node and placed in the stat -structure: - -@itemize @bullet - -@item st_mode - -@item st_nlink - -@item st_ino - -@item st_uid - -@item st_gid - -@item st_atime - -@item st_mtime - -@item st_ctime - -@end itemize - - - -@c -@c -@c -@c @page - -@subsubsection IMFS_fchmod() for Devices - -@subheading Corresponding Structure Element: - -IMFS_fchmod() - -@subheading Arguments: - -@example -rtems_libio_t *iop -mode_t mode -@end example - -@subheading File: - -imfs_fchmod.c - -@subheading Description: - -This routine will obtain the pointer to the IMFS_jnode_t structure from the -information currently in the file control block. - -Based on configuration the routine will acquire the user ID from a call to -getuid() or from the IMFS_jnode_t structure. - -It then checks to see if we have the ownership rights to alter the mode of -the file. If the caller does not, an error code is returned. - -An additional test is performed to verify that the caller is not trying to -alter the nature of the node. If the caller is attempting to alter more than -the permissions associated with user group and other, an error is returned. - -If all the preconditions are met, the user, group and other fields are set -based on the mode calling parameter. - - -@c -@c -@c -@c @page - -@subsubsection No ftruncate() for Devices - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX -@subheading File: - -XXX - -@subheading Description: - -XXX - -@c -@c -@c -@c @page - -@subsubsection No fpathconf() for Devices - -@subheading Corresponding Structure Element: - -fpathconf - -@subheading Arguments: - -Not Implemented - -@subheading File: - -Not Implemented - -@subheading Description: - -Not Implemented - - -@c -@c -@c -@c @page - -@subsubsection No fsync() for Devices - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - - -@c -@c -@c -@c @page - -@subsubsection No fdatasync() for Devices - -Not Implemented - -@subheading Corresponding Structure Element: - -XXX - -@subheading Arguments: - -XXX - -@subheading File: - -XXX - -@subheading Description: - -XXX - diff --git a/doc/filesystem/init.t b/doc/filesystem/init.t deleted file mode 100644 index b4df2758b2..0000000000 --- a/doc/filesystem/init.t +++ /dev/null @@ -1,113 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter System Initialization - -After the RTEMS initialization is performed, the application's -initialization will be performed. Part of initialization is a call to -rtems_filesystem_initialize(). This routine will mount the `In Memory File -System' as the base filesystem. Mounting the base filesystem consists -of the following: - -@itemize @bullet - -@item Initialization of mount table chain control structure - -@item Allocation of a @code{jnode} structure that will server as the root node -of the `In Memory Filesystem' - -@item Initialization of the allocated @code{jnode} with the appropriate OPS, -directory handlers and pathconf limits and options. - -@item Allocation of a memory region for filesystem specific global -management variables - -@item Creation of first mount table entry for the base filesystem - -@item Initialization of the first mount table chain entry to indicate that -the mount point is NULL and the mounted filesystem is the base file -system - -@end itemize - - -After the base filesystem has been mounted, the following operations are -performed under its directory structure: - -@itemize @bullet - -@item Creation of the /dev directory - -@item Registration of devices under /dev directory - -@end itemize - -@section Base Filesystem - -RTEMS initially mounts a RAM based file system known as the base file system. -The root directory of this file system tree serves as the logical root of the -directory hierarchy (Figure 3). Under the root directory a `/dev' directory -is created under which all I/O device directories and files are registered as -part of the file system hierarchy. - -@example -Figure of the tree structure goes here. -@end example - -A RAM based file system draws its management resources from memory. File and -directory nodes are simply allocated blocks of memory. Data associated with -regular files is stored in collections of memory blocks. When the system is -turned off or restarted all memory-based components of the file system are -lost. - -The base file system serves as a starting point for the mounting of file -systems that are resident on semi-permanent storage media. Examples of such -media include non- volatile memory, flash memory and IDE hard disk drives -(Figure 3). File systems of other types will be mounted onto mount points -within the base file system or other file systems that are subordinate to the -base file system. The framework set up under the base file system will allow -for these new file system types and the unique data and functionality that is -required to manage the future file systems. - -@subsection Base Filesystem Mounting - -At present, the first file system to be mounted is the `In Memory File -System'. It is mounted using a standard MOUNT() command in which the mount -point is NULL. This flags the mount as the first file system to be -registered under the operating system and appropriate initialization of file -system management information is performed (See figures 4 and 5). If a -different file system type is desired as the base file system, alterations -must be made to base_fs.c. This routine handles the mount of the base file -system. - - -@example -Figure of the mount table chain goes here. -@end example - - -Once the root of the base file system has been established and it has been -recorded as the mount point of the base file system, devices are integrated -into the base file system. For every device that is configured into the -system (See ioman.c) a device registration process is performed. Device -registration produces a unique dev_t handle that consists of a major and -minor device number. In addition, the configuration information for each -device contains a text string that represents the fully qualified pathname to -that device's place in the base file system's hierarchy. A file system node -is created for the device along the specified registration path. - - -@example -Figure of the Mount Table Processing goes here. -@end example - - -Note: Other file systems can be mounted but they are mounted onto points -(directory mount points) in the base file system. - - diff --git a/doc/filesystem/miniimfs.t b/doc/filesystem/miniimfs.t deleted file mode 100644 index 6b65cab725..0000000000 --- a/doc/filesystem/miniimfs.t +++ /dev/null @@ -1,16 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Miniature In-Memory Filesystem - -This chapter describes the Miniature In-Memory FileSystem (miniIMFS). -The miniIMFS is a reduced feature version of the IMFS designed to -provide minimal functionality and have a low memory footprint. - -This chapter should be written after the IMFS chapter is completed -and describe the implementation of the mini-IMFS. diff --git a/doc/filesystem/mounting.t b/doc/filesystem/mounting.t deleted file mode 100644 index 4090991776..0000000000 --- a/doc/filesystem/mounting.t +++ /dev/null @@ -1,171 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Mounting and Unmounting Filesystems - -@section Mount Points - -The following is the list of the characteristics of a mount point: - -@itemize @bullet - -@item The mount point must be a directory. It may have files and other -directories under it. These files and directories will be hidden when the -filesystem is mounted. - -@item The task must have read/write/execute permissions to the mount point -or the mount attempt will be rejected. - -@item Only one filesystem can be mounted to a single mount point. - -@item The Root of the mountable filesystem will be referenced by the name -of the mount point after the mount is complete. - -@end itemize - -@section Mount Table Chain - -The mount table chain is a dynamic list of structures that describe -mounted filesystems a specific points in the filesystem hierarchy. It is -initialized to an empty state during the base filesystem initialization. -The mount operation will add entries to the mount table chain. The -un-mount operation will remove entries from the mount table chain. - -Each entry in the mount table chain is of the following type: - -@example -struct rtems_filesystem_mount_table_entry_tt -@{ - Chain_Node Node; - rtems_filesystem_location_info_t mt_point_node; - rtems_filesystem_location_info_t mt_fs_root; - int options; - void *fs_info; - - rtems_filesystem_limits_and_options_t pathconf_limits_and_options; - - /* - * When someone adds a mounted filesystem on a real device, - * this will need to be used. - * - * The best option long term for this is probably an - * open file descriptor. - */ - char *dev; -@}; -@end example - -@table @b -@item Node -The Node is used to produce a linked list of mount table entry nodes. - -@item mt_point_node -The mt_point_node contains all information necessary to access the -directory where a filesystem is mounted onto. This element may contain -memory that is allocated during a path evaluation of the filesystem -containing the mountpoint directory. The generic code allows this -memory to be returned by unmount when the filesystem identified by -mt_fs_root is unmounted. - -@item mt_fs_root -The mt_fs_root contains all information necessary to identify the root -of the mounted filesystem. The user is never allowed access to this -node by the generic code, but it is used to identify to the mounted -filesystem where to start evaluation of pathnames at. - -@item options -XXX - -@item fs_info -The fs_info element is a location available for use by the mounted file -system to identify unique things applicable to this instance of the file -system. For example the IMFS uses this space to provide node -identification that is unique for each instance (mounting) of the filesystem. - -@item pathconf_limits_and_options -XXX - -@item dev -This character string represents the device where the filesystem will reside. - -@end table - -@section Adding entries to the chain during mount - -When a filesystem is mounted, its presence and location in the file -system hierarchy is recorded in a dynamic list structure known as a chain. -A unique rtems_filesystem_mount_table_entry_tt structure is logged for -each filesystem that is mounted. This includes the base filesystem. - -@section Removing entries from the chain during unmount - -When a filesystem is dismounted its entry in the mount table chain is -extracted and the memory for this entry is freed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/doc/filesystem/patheval.t b/doc/filesystem/patheval.t deleted file mode 100644 index 6f1f638ed6..0000000000 --- a/doc/filesystem/patheval.t +++ /dev/null @@ -1,109 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Pathname Evaluation - -This chapter describes the pathname evaluation process for the -RTEMS Filesystem Infrastructure. - -@example -XXX Include graphic of the path evaluation process -@end example - -@section Pathname Evaluation Handlers - -There are two pathname evaluation routines. The handler patheval() -is called to find, verify privlages on and return information on a node -that exists. The handler evalformake() is called to find, verify -permissions, and return information on a node that is to become a parent. -Additionally, evalformake() returns a pointer to the start of the name of -the new node to be created. - -Pathname evaluation is specific to a filesystem. -Each filesystem is required to provide both a patheval() and an evalformake() -routine. Both of these routines gets a name to evaluate and a node indicating -where to start the evaluation. - -@section Crossing a Mount Point During Path Evaluation - -If the filesystem supports the mount command, the evaluate routines -must handle crossing the mountpoint. The evaluate routine should evaluate -the name upto the first directory node where the new filesystem is mounted. -The filesystem may process terminator characters prior to calling the -evaluate routine for the new filesystem. A pointer to the portion of the -name which has not been evaluated along with the root node of the new -file system ( gotten from the mount table entry ) is passed to the correct -mounted filesystem evaluate routine. - - -@section The rtems_filesystem_location_info_t Structure - -The @code{rtems_filesystem_location_info_t} structure contains all information -necessary for identification of a node. - -The generic rtems filesystem code defines two global -rtems_filesystem_location_info_t structures, the -@code{rtems_filesystem_root} and the @code{rtems_filesystem_current}. -Both are initially defined to be the root node of the base filesystem. -Once the chdir command is correctly used the @code{rtems_filesystem_current} -is set to the location specified by the command. - -The filesystem generic code peeks at the first character in the name to be -evaluated. If this character is a valid seperator, the -@code{rtems_filesystem_root} is used as the node to start the evaluation -with. Otherwise, the @code{rtems_filesystem_current} node is used as the -node to start evaluating with. Therefore, a valid -rtems_filesystem_location_info_t is given to the evaluate routine to start -evaluation with. The evaluate routines are then responsible for making -any changes necessary to this structure to correspond to the name being -parsed. - -@example -struct rtems_filesystem_location_info_tt @{ - void *node_access; - rtems_filesystem_file_handlers_r *handlers; - rtems_filesystem_operations_table *ops; - rtems_filesystem_mount_table_entry_t *mt_entry; -@}; -@end example - -@table @b - -@item node_access -This element is filesystem specific. A filesystem can define and store -any information necessary to identify a node at this location. This element -is normally filled in by the filesystem's evaluate routine. For the -filesystem's root node, the filesystem's initilization routine should -fill this in, and it should remain valid until the instance of the -filesystem is unmounted. - -@item handlers -This element is defined as a set of routines that may change within a -given filesystem based upon node type. For example a directory and a -memory file may have to completely different read routines. This element -is set to an initialization state defined by the mount table, and may -be set to the desired state by the evaluation routines. - -@item ops -This element is defined as a set of routines that remain static for the -filesystem. This element identifies entry points into the filesystem -to the generic code. - -@item mt_entry -This element identifies the mount table entry for this instance of the -filesystem. - -@end table - - - - - - - - diff --git a/doc/filesystem/preface.texi b/doc/filesystem/preface.texi deleted file mode 100644 index 20a975fdf3..0000000000 --- a/doc/filesystem/preface.texi +++ /dev/null @@ -1,83 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@ifinfo -@node Preface, , Top, Top -@end ifinfo -@unnumbered Preface - -This document describes the implementation of the RTEMS filesystem -infrastructure. This infrastructure supports the following -capabilities: - -@itemize @bullet - -@item Mountable file systems - -@item Hierarchical file system directory structure - -@item POSIX compliant set of routines for the manipulation of files and directories - -@item Individual file and directory support for the following: - -@enumerate - -@item Permissions for read, write and execute - -@item User ID - -@item Group ID - -@item Access time - -@item Modification time - -@item Creation time - -@end enumerate - -@item Hard links to files and directories - -@item Symbolic links to files and directories - -@end itemize - -This has been implemented to provide the framework for a UNIX-like -file system support. POSIX file and directory functions have been -implemented that allow a standard method of accessing file, device and -directory information within file systems. The file system concept that -has been implemented allows for expansion and adaptation of the file -system to a variety of existing and future data storage devices. To this -end, file system mount and unmount capabilities have been included in this -RTEMS framework. - -This framework slightly alters the manner in which devices are handled -under RTEMS from that of public release 4.0.0 and earlier. Devices that -are defined under a given RTEMS configuration will now be registered as -files in a mounted file system. Access to these device drivers and their -associated devices may now be performed through the traditional file system -open(), read(), write(), lseek(), fstat() and ioctl() functions in addition -to the interface provided by the IO Manager in the RTEMS Classic API. - -An In-Memory File System (IMFS) is included which provides full POSIX -filesystem functionality yet is RAM based. The IMFS maintains a -node structure for each file, device, and directory in each mounted -instantiation of its file system. The node structure is used to -manage ownership, access rights, access time, modification time, -and creation time. A union of structures within the IMFS nodal -structure provide for manipulation of file data, device selection, -or directory content as required by the nodal type. Manipulation of -these properties is accomplished through the POSIX set of file and -directory functions. In addition to being useful in its own right, -the IMFS serves as a full featured example filesystem. - -The intended audience for this document is those persons implementing -their own filesystem. Users of the filesystem may find information -on the implementation useful. But the user interface to the filesystem -is through the ISO/ANSI C Library and POSIX 1003.1b file and directory -APIs. diff --git a/doc/filesystem/syscalls.t b/doc/filesystem/syscalls.t deleted file mode 100644 index 238931d68b..0000000000 --- a/doc/filesystem/syscalls.t +++ /dev/null @@ -1,1130 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter System Call Development Notes - -This set of routines represents the application's interface to files and directories -under the RTEMS filesystem. All routines are compliant with POSIX standards if a -specific interface has been established. The list below represents the routines that have -been included as part of the application's interface. - -@enumerate -@item access() -@item chdir() -@item chmod() -@item chown() -@item close() -@item closedir() -@item dup() -@item dup2() -@item fchmod() -@item fcntl() -@item fdatasync() -@item fpathconf() -@item fstat() -@item ioctl() -@item link() -@item lseek() -@item mkdir() -@item mkfifo() -@item mknod() -@item mount() -@item open() -@item opendir() -@item pathconf() -@item read() -@item readdir() -@item unmount() -@end enumerate - -The sections that follow provide developmental information concerning each -of these functions. - - -@c @page -@section access - -@subheading File: - -access.c - -@subheading Processing: - -This routine is layered on the stat() function. It acquires the current -status information for the specified file and then determines if the -caller has the ability to access the file for read, write or execute -according to the mode argument to this function. - -@subheading Development Comments: - -This routine is layered on top of the stat() function. As long as the -st_mode element in the returned structure follow the standard UNIX -conventions, this function should support other filesystems without -alteration. - -@c @page -@section chdir - -@subheading File: - -chdir.c - - -@subheading Processing: - -This routine will determine if the pathname that we are attempting to make -that current directory exists and is in fact a directory. If these -conditions are met the global indication of the current directory -(rtems_filesystem_current) is set to the rtems_filesystem_location_info_t -structure that is returned by the rtems_filesystem_evaluate_path() -routine. - -@subheading Development Comments: - -This routine is layered on the rtems_filesystem_evaluate_path() routine -and the filesystem specific OP table function node_type(). - -The routine node_type() must be a routine provided for each filesystem -since it must access the filesystems node information to determine which -of the following types the node is: - -@itemize @bullet -@item RTEMS_FILESYSTEM_DIRECTORY -@item RTEMS_FILESYSTEM_DEVICE -@item RTEMS_FILESYSTEM_HARD_LINK -@item RTEMS_FILESYSTEM_MEMORY_FILE -@end itemize - -This acknowledges that the form of the node management information can -vary from one filesystem implementation to another. - -RTEMS has a special global structure that maintains the current directory -location. This global variable is of type rtems_filesystem_location_info_t -and is called rtems_filesystem_current. This structure is not always -valid. In order to determine if the structure is valid, you must first -test the node_access element of this structure. If the pointer is NULL, -then the structure does not contain a valid indication of what the current -directory is. - -@c @page -@section chmod - -@subheading File: - -chmod.c - -@subheading Processing: - -This routine is layered on the open(), fchmod() and close() functions. As -long as the standard interpretation of the mode_t value is maintained, -this routine should not need modification to support other filesystems. - -@subheading Development Comments: - -The routine first determines if the selected file can be open with -read/write access. This is required to allow modification of the mode -associated with the selected path. - -The fchmod() function is used to actually change the mode of the path -using the integer file descriptor returned by the open() function. - -After mode modification, the open file descriptor is closed. - -@c @page -@section chown - -@subheading File: - -chown.c - -@subheading Processing: - -This routine is layered on the rtems_filesystem_evaluate_path() and the -file system specific chown() routine that is specified in the OPS table -for the file system. - -@subheading Development Comments: - -rtems_filesystem_evaluate_path() is used to determine if the path -specified actually exists. If it does a rtems_filesystem_location_info_t -structure will be obtained that allows the shell function to locate the -OPS table that is to be used for this filesystem. - -It is possible that the chown() function that should be in the OPS table -is not defined. A test for a non-NULL OPS table chown() entry is performed -before the function is called. - -If the chown() function is defined in the indicated OPS table, the -function is called with the rtems_filesystem_location_info_t structure -returned from the path evaluation routine, the desired owner, and group -information. - -@c @page -@section close - -@subheading File: - -close.c - -@subheading Processing: - -This routine will allow for the closing of both network connections and -file system devices. If the file descriptor is associated with a network -device, the appropriate network function handler will be selected from a -table of previously registered network functions (rtems_libio_handlers) -and that function will be invoked. - -If the file descriptor refers to an entry in the filesystem, the -appropriate handler will be selected using information that has been -placed in the file control block for the device (rtems_libio_t structure). - -@subheading Development Comments: - -rtems_file_descriptor_type examines some of the upper bits of the file -descriptor index. If it finds that the upper bits are set in the file -descriptor index, the device referenced is a network device. - -Network device handlers are obtained from a special registration table -(rtems_libio_handlers) that is set up during network initialization. The -network handler invoked and the status of the network handler will be -returned to the calling process. - -If none of the upper bits are set in the file descriptor index, the file -descriptor refers to an element of the RTEMS filesystem. - -The following sequence will be performed for any filesystem file -descriptor: - -@enumerate - -@item Use the rtems_libio_iop() function to obtain the rtems_libio_t -structure for the file descriptor - -@item Range check the file descriptor using rtems_libio_check_fd() - -@item Determine if there is actually a function in the selected handler -table that processes the close() operation for the filesystem and node -type selected. This is generally done to avoid execution attempts on -functions that have not been implemented. - -@item If the function has been defined it is invoked with the file control -block pointer as its argument. - -@item The file control block that was associated with the open file -descriptor is marked as free using rtems_libio_free(). - -@item The return code from the close handler is then passed back to the -calling program. - -@end enumerate - -@c @page -@section closedir - -@subheading File: - -closedir.c - -@subheading Processing: - -The code was obtained from the BSD group. This routine must clean up the -memory resources that are required to track an open directory. The code is -layered on the close() function and standard memory free() functions. It -should not require alterations to support other filesystems. - -@subheading Development Comments: - -The routine alters the file descriptor and the index into the DIR -structure to make it an invalid file descriptor. Apparently the memory -that is about to be freed may still be referenced before it is -reallocated. - -The dd_buf structure's memory is reallocated before the control structure -that contains the pointer to the dd_buf region. - -DIR control memory is reallocated. - -The close() function is used to free the file descriptor index. - - -@c @page -@section dup() Unimplemented - -@subheading File: - -dup.c - -@subheading Processing: - - -@subheading Development Comments: - - - - - -@c @page -@section dup2() Unimplemented - -@subheading File: - -dup2.c - -@subheading Processing: - - -@subheading Development Comments: - - - - - - -@c @page -@section fchmod - -@subheading File: - -fchmod.c - -@subheading Processing: - -This routine will alter the permissions of a node in a filesystem. It is -layered on the following functions and macros: - -@itemize @bullet -@item rtems_file_descriptor_type() - -@item rtems_libio_iop() - -@item rtems_libio_check_fd() - -@item rtems_libio_check_permissions() - -@item fchmod() function that is referenced by the handler table in the -file control block associated with this file descriptor - -@end itemize - -@subheading Development Comments: - -The routine will test to see if the file descriptor index is associated -with a network connection. If it is, an error is returned from this -routine. - -The file descriptor index is used to obtain the associated file control -block. - -The file descriptor value is range checked. - -The file control block is examined to determine if it has write -permissions to allow us to alter the mode of the file. - -A test is made to determine if the handler table that is referenced in the -file control block contains an entry for the fchmod() handler function. If -it does not, an error is returned to the calling routine. - -If the fchmod() handler function exists, it is called with the file -control block and the desired mode as parameters. - -@c @page -@section fcntl() - -@subheading File: - -fcntl.c - -@subheading Processing: - -This routine currently only interacts with the file control block. If the -structure of the file control block and the associated meanings do not -change, the partial implementation of fcntl() should remain unaltered for -other filesystem implementations. - -@subheading Development Comments: - -The only commands that have been implemented are the F_GETFD and F_SETFD. -The commands manipulate the LIBIO_FLAGS_CLOSE_ON_EXEC bit in the -@code{flags} element of the file control block associated with the file -descriptor index. - -The current implementation of the function performs the sequence of -operations below: - -@enumerate - -@item Test to see if we are trying to operate on a file descriptor -associated with a network connection - -@item Obtain the file control block that is associated with the file -descriptor index - -@item Perform a range check on the file descriptor index. - -@end enumerate - - - -@c @page -@section fdatasync - -@subheading File: - -fdatasync.c - -@subheading Processing: - -This routine is a template in the in memory filesystem that will route us to the -appropriate handler function to carry out the fdatasync() processing. In the in -memory filesystem this function is not necessary. Its function in a disk based file -system that employs a memory cache is to flush all memory based data buffers to -disk. It is layered on the following functions and macros: - -@itemize @bullet - -@item rtems_file_descriptor_type() - -@item rtems_libio_iop() - -@item rtems_libio_check_fd() - -@item rtems_libio_check_permissions() - -@item fdatasync() function that is referenced by the handler table in the -file control block associated with this file descriptor - -@end itemize - -@subheading Development Comments: - -The routine will test to see if the file descriptor index is associated -with a network connection. If it is, an error is returned from this -routine. - -The file descriptor index is used to obtain the associated file control -block. - -The file descriptor value is range checked. - -The file control block is examined to determine if it has write -permissions to the file. - -A test is made to determine if the handler table that is referenced in the -file control block contains an entry for the fdatasync() handler function. -If it does not an error is returned to the calling routine. - -If the fdatasync() handler function exists, it is called with the file -control block as its parameter. - -@c @page -@section fpathconf - -@subheading File: - -fpathconf.c - -@subheading Processing: - -This routine is layered on the following functions and macros: - -@itemize @bullet - -@item rtems_file_descriptor_type() - -@item rtems_libio_iop() - -@item rtems_libio_check_fd() - -@item rtems_libio_check_permissions() - -@end itemize - -When a filesystem is mounted, a set of constants is specified for the -filesystem. These constants are stored with the mount table entry for the -filesystem. These constants appear in the POSIX standard and are listed -below. - -@itemize @bullet - -@item PCLINKMAX - -@item PCMAXCANON - -@item PCMAXINPUT - -@item PCNAMEMAX - -@item PCPATHMAX - -@item PCPIPEBUF - -@item PCCHOWNRESTRICTED - -@item PCNOTRUNC - -@item PCVDISABLE - -@item PCASYNCIO - -@item PCPRIOIO - -@item PCSYNCIO - - -@end itemize - -This routine will find the mount table information associated the file -control block for the specified file descriptor parameter. The mount table -entry structure contains a set of filesystem specific constants that can -be accessed by individual identifiers. - -@subheading Development Comments: - -The routine will test to see if the file descriptor index is associated -with a network connection. If it is, an error is returned from this -routine. - -The file descriptor index is used to obtain the associated file control -block. - -The file descriptor value is range checked. - -The file control block is examined to determine if it has read permissions -to the file. - -Pathinfo in the file control block is used to locate the mount table entry -for the filesystem associated with the file descriptor. - -The mount table entry contains the pathconf_limits_and_options element. -This element is a table of constants that is associated with the -filesystem. - -The name argument is used to reference the desired constant from the -pathconf_limits_and_options table. - - -@c @page -@section fstat - -@subheading File: - -fstat.c - -@subheading Processing: - -This routine will return information concerning a file or network -connection. If the file descriptor is associated with a network -connection, the current implementation of @code{fstat()} will return a -mode set to @code{S_IFSOCK}. In a later version, this routine will map the -status of a network connection to an external handler routine. - -If the file descriptor is associated with a node under a filesystem, the -fstat() routine will map to the fstat() function taken from the node -handler table. - -@subheading Development Comments: - -This routine validates that the struct stat pointer is not NULL so that -the return location is valid. - -The struct stat is then initialized to all zeros. - -rtems_file_descriptor_type() is then used to determine if the file -descriptor is associated with a network connection. If it is, network -status processing is performed. In the current implementation, the file -descriptor type processing needs to be improved. It currently just drops -into the normal processing for file system nodes. - -If the file descriptor is associated with a node under a filesystem, the -following steps are performed: - -@enumerate - -@item Obtain the file control block that is associated with the file descriptor -index. - -@item Range check the file descriptor index. - -@item Test to see if there is a non-NULL function pointer in the handler -table for the fstat() function. If there is, invoke the function with the -file control block and the pointer to the stat structure. - -@end enumerate - -@c @page -@section ioctl - -@subheading File: - -ioctl.c - -@subheading Processing: - -Not defined in the POSIX 1003.1b standard but commonly supported in most -UNIX and POSIX system. Ioctl() is a catchall for I/O operations. Routine -is layered on external network handlers and filesystem specific handlers. -The development of new filesystems should not alter the basic processing -performed by this routine. - -@subheading Development Comments: - - -The file descriptor is examined to determine if it is associated with a -network device. If it is processing is mapped to an external network -handler. The value returned by this handler is then returned to the -calling program. - -File descriptors that are associated with a filesystem undergo the -following processing: - -@enumerate - -@item The file descriptor index is used to obtain the associated file -control block. - -@item The file descriptor value is range checked. - -@item A test is made to determine if the handler table that is referenced -in the file control block contains an entry for the ioctl() handler -function. If it does not, an error is returned to the calling routine. - -@item If the ioctl() handler function exists, it is called with the file -control block, the command and buffer as its parameters. - -@item The return code from this function is then sent to the calling -routine. - -@end enumerate - - -@c @page -@section link - -@subheading File: - -link.c - -@subheading Processing: - -This routine will establish a hard link to a file, directory or a device. -The target of the hard link must be in the same filesystem as the new link -being created. A link to an existing link is also permitted but the -existing link is evaluated before the new link is made. This implies that -links to links are reduced to links to files, directories or devices -before they are made. - -@subheading Development Comments: - -Calling parameters: -const char *existing - const char *new - -link() will determine if the target of the link actually exists using -rtems_filesystem_evaluate_path() - -rtems_filesystem_get_start_loc() is used to determine where to start the -path evaluation of the new name. This macro examines the first characters -of the name to see if the name of the new link starts with a -rtems_filesystem_is_separator. If it does the search starts from the root -of the RTEMS filesystem; otherwise the search will start from the current -directory. - -The OPS table evalformake() function for the parent's filesystem is used -to locate the node that will be the parent of the new link. It will also -locate the start of the new path's name. This name will be used to define -a child under the parent directory. - -If the parent is found, the routine will determine if the hard link that -we are trying to create will cross a filesystem boundary. This is not -permitted for hard-links. - -If the hard-link does not cross a filesystem boundary, a check is -performed to determine if the OPS table contains an entry for the link() -function. - -If a link() function is defined, the OPS table link() function will be -called to establish the actual link within the filesystem. - -The return code from the OPS table link() function is returned to the -calling program. - -@c @page -@section lseek - -@subheading File: - -lseek.c - -@subheading Processing: - -This routine is layered on both external handlers and filesystem / node -type specific handlers. This routine should allow for the support of new -filesystems without modification. - -@subheading Development Comments: - -This routine will determine if the file descriptor is associated with a -network device. If it is lseek will map to an external network handler. -The handler will be called with the file descriptor, offset and whence as -its calling parameters. The return code from the external handler will be -returned to the calling routine. - -If the file descriptor is not associated with a network connection, it is -associated with a node in a filesystem. The following steps will be -performed for filesystem nodes: - -@enumerate - -@item The file descriptor is used to obtain the file control block for the -node. - -@item The file descriptor is range checked. - -@item The offset element of the file control block is altered as indicated -by the offset and whence calling parameters - -@item The handler table in the file control block is examined to determine -if it contains an entry for the lseek() function. If it does not an error -is returned to the calling program. - -@item The lseek() function from the designated handler table is called -with the file control block, offset and whence as calling arguments - -@item The return code from the lseek() handler function is returned to the -calling program - -@end enumerate - - -@c @page -@section mkdir - -@subheading File: - -mkdir.c - -@subheading Processing: - -This routine attempts to create a directory node under the filesystem. The -routine is layered the mknod() function. - -@subheading Development Comments: - -See mknod() for developmental comments. - -@c @page -@section mkfifo - -@subheading File: - -mkfifo.c - -@subheading Processing: - -This routine attempts to create a FIFO node under the filesystem. The -routine is layered the mknod() function. - -@subheading Development Comments: - -See mknod() for developmental comments - -@c @page -@section mknod - -@subheading File: - -mknod.c - -@subheading Processing: - -This function will allow for the creation of the following types of nodes -under the filesystem: - -@itemize @bullet - -@item directories - -@item regular files - -@item character devices - -@item block devices - -@item fifos - -@end itemize - -At the present time, an attempt to create a FIFO will result in an ENOTSUP -error to the calling function. This routine is layered the filesystem -specific routines evalformake and mknod. The introduction of a new -filesystem must include its own evalformake and mknod function to support -the generic mknod() function. Under this condition the generic mknod() -function should accommodate other filesystem types without alteration. - -@subheading Development Comments: - -Test for nodal types - I thought that this test should look like the -following code: - -@example -if ( (mode & S_IFDIR) = = S_IFDIR) || - (mode & S_IFREG) = = S_IFREG) || - (mode & S_IFCHR) = = S_IFCHR) || - (mode & S_IFBLK) = = S_IFBLK) || - (mode & S_IFIFO) = = S_IFIFO)) - Set_errno_and_return_minus_one (EINVAL); - -@end example - -Where: - -@itemize @bullet -@item S_IFREG (0100000) - Creation of a regular file -@item S_IFCHR (0020000) - Creation of a character device -@item S_IFBLK (0060000) - Creation of a block device -@item S_IFIFO (0010000) - Creation of a FIFO -@end itemize - -Determine if the pathname that we are trying to create starts at the root -directory or is relative to the current directory using the -rtems_filesystem_get_start_loc() function. - -Determine if the pathname leads to a valid directory that can be accessed -for the creation of a node. - -If the pathname is a valid location to create a node, verify that a -filesystem specific mknod() function exists. - -If the mknod() function exists, call the filesystem specific mknod() -function. Pass the name, mode, device type and the location information -associated with the directory under which the node will be created. - -@c @page -@section mount - -@subheading File: - -mount.c - - -Arguments (Not a standard POSIX call): - -rtems_filesystem_mount_table_entry_t **mt_entry, - -If the mount operation is successful, this pointer to a pointer will be -set to reference the mount table chain entry that has been allocated for -this file system mount. - -rtems_filesystem_operations_table *fs_ops, - -This is a pointer to a table of functions that are associated with the -file system that we are about to mount. This is the mechanism to selected -file system type without keeping a dynamic database of all possible file -system types that are valid for the mount operation. Using this method, it -is only necessary to configure the filesystems that we wish to use into -the RTEMS build. Unused filesystems types will not be drawn into the -build. - -char *fsoptions, - -This argument points to a string that selects mounting for read only -access or read/write access. Valid states are "RO" and "RW" - -char *device, - -This argument is reserved for the name of a device that will be used to -access the filesystem information. Current filesystem implementations are -memory based and do not require a device to access filesystem information. - -char *mount_point - -This is a pathname to a directory in a currently mounted filesystem that -allows read, write and execute permissions. If successful, the node found -by evaluating this name, is stored in the mt_entry. - -@subheading Processing: - -This routine will handle the mounting of a filesystem on a mount point. If -the operation is successful, a pointer to the mount table chain entry -associated with the mounted filesystem will be returned to the calling -function. The specifics about the processing required at the mount point -and within the filesystem being mounted is isolated in the filesystem -specific mount() and fsmount_me() functions. This allows the generic -mount() function to remain unaltered even if new filesystem types are -introduced. - - - -@subheading Development Comments: - -This routine will use get_file_system_options() to determine if the mount -options are valid ("RO" or "RW"). - -It confirms that a filesystem ops-table has been selected. - -Space is allocated for a mount table entry and selective elements of the -temporary mount table entry are initialized. - -If a mount point is specified: The mount point is examined to determine -that it is a directory and also has the appropriate permissions to allow a -filesystem to be mounted. - -The current mount table chain is searched to determine that there is not -another filesystem mounted at the mount point we are trying to mount onto. - -If a mount function is defined in the ops table for the filesystem -containing the mount point, it is called at this time. - -If no mount point is specified: Processing if performed to set up the -mount table chain entry as the base filesystem. - -If the fsmount_me() function is specified for ops-table of the filesystem -being mounted, that function is called to initialize for the new -filesystem. - -On successful completion, the temporary mount table entry will be placed -on the mount table chain to record the presence of the mounted filesystem. - -@c @page -@section open - -@subheading File: - -open.c - -@subheading Processing: - -This routine is layered on both RTEMS calls and filesystem specific -implementations of the open() function. These functional interfaces should -not change for new filesystems and therefore this code should be stable as -new file systems are introduced. - -@subheading Development Comments: - -This routine will allocate a file control block for the file or device -that we are about to open. - -It will then test to see if the pathname exists. If it does a -rtems_filesystem_location_info_t data structure will be filled out. This -structure contains information that associates node information, -filesystem specific functions and mount table chain information with the -pathname. - -If the create option has been it will attempt to create a node for a -regular file along the specified path. If a file already exists along this -path, an error will be generated; otherwise, a node will be allocated for -the file under the filesystem that contains the pathname. When a new node -is created, it is also evaluated so that an appropriate -rtems_filesystem_location_info_t data structure can be filled out for the -newly created node. - -If the file exists or the new file was created successfully, the file -control block structure will be initialized with handler table -information, node information and the rtems_filesystem_location_info_t -data structure that describes the node and filesystem data in detail. - -If an open() function exists in the filesystem specific handlers table for -the node that we are trying to open, it will be called at this time. - -If any error is detected in the process, cleanup is performed. It consists -of freeing the file control block structure that was allocated at the -beginning of the generic open() routine. - -On a successful open(), the index into the file descriptor table will be -calculated and returned to the calling routine. - -@c @page -@section opendir - -@subheading File: - -opendir.c - -@subheading Processing: - -This routine will attempt to open a directory for read access. It will -setup a DIR control structure that will be used to access directory -information. This routine is layered on the generic open() routine and -filesystem specific directory processing routines. - -@subheading Development Comments: - -The BSD group provided this routine. - -@c @page -@section pathconf - -@subheading File: - -pathconf.c - -@subheading Processing: - -This routine will obtain the value of one of the path configuration -parameters and return it to the calling routine. It is layered on the -generic open() and fpathconf() functions. These interfaces should not -change with the addition of new filesystem types. - -@subheading Development Comments: - -This routine will try to open the file indicated by path. - -If successful, the file descriptor will be used to access the pathconf -value specified by @code{name} using the fpathconf() function. - -The file that was accessed is then closed. - -@c @page -@section read - -@subheading File: - -deviceio.c - -@subheading Processing: - -This routine is layered on a set of RTEMS calls and filesystem specific -read operations. The functions are layered in such a way as to isolate -them from change as new filesystems are introduced. - -@subheading Development Comments: - -This routine will examine the type of file descriptor it is sent. - -If the file descriptor is associated with a network device, the read -function will be mapped to a special network handler. The return code from -the network handler will then be sent as the return code from generic -read() function. - -For file descriptors that are associated with the filesystem the following -sequence will be performed: - -@enumerate - -@item Obtain the file control block associated with the file descriptor - -@item Range check the file descriptor - -@item Determine that the buffer pointer is not invalid - -@item Check that the count is not zero - -@item Check the file control block to see if we have permissions to read - -@item If there is a read function in the handler table, invoke the handler -table read() function - -@item Use the return code from the handler table read function(number of -bytes read) to increment the offset element of the file control block - -@item Return the number of bytes read to the calling program - -@end enumerate - -@c @page -@section readdir - -@subheading File: - -readdir.c - -@subheading Processing: - -This routine was acquired from the BSD group. It has not been altered from -its original form. - -@subheading Development Comments: - -The routine calls a customized getdents() function that is provided by the -user. This routine provides the filesystem specific aspects of reading a -directory. - -It is layered on the read() function in the directory handler table. This -function has been mapped to the Imfs_dir_read() function. - -@c @page -@section unmount - -@subheading File: - -unmount.c - -@subheading Processing: - -This routine will attempt to dismount a mounted filesystem and then free -all resources that were allocated for the management of that filesystem. - -@subheading Development Comments: - -@itemize @bullet - -@item This routine will determine if there are any filesystems currently -mounted under the filesystem that we are trying to dismount. This would -prevent the dismount of the filesystem. - -@item It will test to see if the current directory is in the filesystem -that we are attempting to dismount. This would prevent the dismount of the -filesystem. - -@item It will scan all the currently open file descriptors to determine is -there is an open file descriptor to a file in the filesystem that we are -attempting to unmount(). - -@end itemize - -If the above preconditions are met then the following sequence is -performed: - -@enumerate - -@item Call the filesystem specific unmount() function for the filesystem -that contains the mount point. This routine should indicate that the mount -point no longer has a filesystem mounted below it. - -@item Call the filesystem specific fsunmount_me() function for the mounted -filesystem that we are trying to unmount(). This routine should clean up -any resources that are no longer needed for the management of the file -system being un-mounted. - -@item Extract the mount table entry for the filesystem that was just -dismounted from the mount table chain. - -@item Free the memory associated with the extracted mount table entry. - -@end enumerate - -@c @page -@section eval - -@subheading File: - -XXX - -@subheading Processing: - -XXX - -@subheading Development Comments: - -XXX - -@c @page -@section getdentsc - -@subheading File: - -XXX - -@subheading Processing: - -XXX - -@subheading Development Comments: - -XXX - diff --git a/doc/filesystem/tftp.t b/doc/filesystem/tftp.t deleted file mode 100644 index 82c4764d4e..0000000000 --- a/doc/filesystem/tftp.t +++ /dev/null @@ -1,14 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Trivial FTP Client Filesystem - -This chapter describes the Trivial FTP (TFTP) Client Filesystem. - -This chapter should be written after the IMFS chapter is completed -and describe the implementation of the TFTP. diff --git a/doc/gnu_docs/Tool_Doc_Instructions b/doc/gnu_docs/Tool_Doc_Instructions deleted file mode 100644 index 37f861d523..0000000000 --- a/doc/gnu_docs/Tool_Doc_Instructions +++ /dev/null @@ -1,32 +0,0 @@ -# -# $Id$ -# - -Apparently, the tool documentation is tough to build without configuring -in the tool source directory. So you need to do some magic to make -this happen. In addition, the makefiles only support building dvi -and info. - -mkdir doc_build -cp -r binutils-XXX gcc-XXX gdb-XXX newlib-XXX doc_build - -# for each tool -cd binutils-XXX -./configure --target=i386-rtems --prefix=/usr3/tmp/DOCTMP -make info dvi - -# for newlib we have to do the build differently -mkdir b -cd b -../newlib-1.8.2/./configure --target=i386-rtems --prefix=/usr3/tmp/DOCTMP -make -make info dvi -cd ../newlib-1.8.2 -find newlib/ -name "*.t*" | cpio -pdum ../b/i386-rtems/ -find etc/ -name "*.t*" | cpio -pdum ../b - - -NOTE: The actual target is not relevant since the documentation is -always the same. - - diff --git a/doc/gnu_docs/gen_docs b/doc/gnu_docs/gen_docs deleted file mode 100644 index 1e9ba9eb83..0000000000 --- a/doc/gnu_docs/gen_docs +++ /dev/null @@ -1,125 +0,0 @@ -#! /bin/sh -# -# This script is intended to be run in the build directory of a software -# package including documentation in texinfo format. The basic operation -# of this script is to: -# + find all ".dvi" files from the current directory down, -# + for each dvi file -# + install the dvi file -# + generate PostScript files for the dvi file -# + install the PostScript file -# + if there is texinfo source for this dvi file -# install the info files -# generate PDF from the texinfo source -# install the PDF file -# generate HTML from the texinfo source -# install the HTML file -# -# - -texi2www=/usr1/rtems/rtemsdoc-work/tools/texi2www/texi2www -install=/usr3/rtems_cds/test_cd/doc/tools/html - -#if [ $? -ne 1 ] ; then -# echo "Usage: $0 install_directory" -# exit 1 -#fi - -if [ ! -d ${install} ] ; then - echo "${install} is not a directory" - exit 1 -fi - -#ECHO=echo - -STARTDIR=`pwd` -find . -name "*.dvi" | while read file -do - cd $STARTDIR - cd `dirname $file` - echo $file - i=`basename $file` -#### - b=`echo $i | cut -d'.' -f1` - echo $b - - if [ -d ${install}/${b} ] ; then - echo "Cleaning install point for ${b}" - ${ECHO} rm -rf ${install}/${b} - fi - ${ECHO} mkdir ${install}/${b} - - echo "Copying DVI for ${b}" - ${ECHO} cp ${b}.dvi ${install}/${b} - - echo "Generating PS for ${b}" - ${ECHO} dvips -o ${install}/${b}/${b}.ps ${b}.dvi - - # unfortunately the .dvi names are not always the same. :( - case ${b} in - history) tsrc=hist ;; - readline) tsrc=rlman ;; - *) tsrc=${b} ;; - esac - - case ${b} in - refcard) - cp $d/gnu_docs/refcard.html ${install}/${b} - ;; - *) - if [ -r ${tsrc}.texi ] ; then - ext=texi - elif [ -r ${tsrc}.texinfo ] ; then - ext=texinfo - else - echo "*** - echo "*** Cannot find a texi or texinfo file for ${b}" - echo "*** -exit 1 - fi - - echo "Copying INFO for ${b}" - ${ECHO} cp ${b}.info* ${install}/../info - - case ${b} in - g77) bad_for_pdf="yes" ;; - *) bad_for_pdf="no" ;; - esac - - case ${b} in - gdb) extraargs_for_pdf="-I ../../readline/doc" ;; - *) extraargs_for_pdf="" ;; - esac - if [ ${bad_for_pdf} = "yes" ] ; then - echo "*** " - echo "*** Skipping PDF for ${b}" - echo "*** " - else - echo "Generating PDF for ${b}" - ${ECHO} texi2pdf ${extraargs_for_pdf} ${tsrc}.${ext} && \ - ${ECHO} cp ${tsrc}.pdf ${install}/${b}/${b}.pdf - fi - - # until texi2www is modified to take a search path - case ${b} in - gdb) - sed -e 's/^ @/@/' <../../readline/doc/rluser.texinfo >rluser.texinfo - cp ../../readline/doc/inc-hist.texi . - ;; - readline) - cp rluser.texinfo rluser.texinfo.tmp - sed -e 's/^ @/@/' <../../readline/doc/rluser.texinfo >rluser.texinfo - rm -f rluser.texinfo.tmp - ;; - *) ;; - esac - echo "Generating HTML for ${b}" - ${ECHO} ${texi2www} \ - -dirfile ../index.html \ - -header $d/gnu_docs/gnu_header.html \ - -footer $d/gnu_docs/gnu_footer.html \ - -icons .. -dir ${install}/${b} \ - ${tsrc}.${ext} - ;; - esac -done diff --git a/doc/gnu_docs/gnu_footer.html b/doc/gnu_docs/gnu_footer.html deleted file mode 100644 index 037261ac58..0000000000 --- a/doc/gnu_docs/gnu_footer.html +++ /dev/null @@ -1,2 +0,0 @@ -

    Packaging copyright © 1988-1999 OAR Corporation
    -Context copyright by each document's author. See Free Software Foundation for information. diff --git a/doc/gnu_docs/gnu_header.html b/doc/gnu_docs/gnu_header.html deleted file mode 100644 index 6bd6009147..0000000000 --- a/doc/gnu_docs/gnu_header.html +++ /dev/null @@ -1,5 +0,0 @@ - - - OAR -

    RTEMS Tools On-Line Library

    -
    diff --git a/doc/gnu_docs/index.html b/doc/gnu_docs/index.html deleted file mode 100644 index 03bd3de4b3..0000000000 --- a/doc/gnu_docs/index.html +++ /dev/null @@ -1,143 +0,0 @@ - -RTEMS On-Line Library - - - OAR -

    RTEMS Tools On-Line Library

    -
    - - -
  • GNU Compiler Collection (GCC) 2.95.1 - -
  • - - - - Using and Porting the GNU Compiler Collection (GCC)
    • -
  • - - - - The C Preprocessor
    • -
  • - - - - Guide to GNU Chill
    • -
  • - - - - Using and Porting GNU Fortran
    • -     -
    • - -
  • GNU binutils 990901 - -
  • - - - - - - - GNU Binary Utilities
    • -
  • - - - - Using the GNU Assembler
    • -
  • - - - - GNU Preprocessor for Assembly Programs (gasp)
    • -
  • - - - - Using the GNU Linker (ld)
    • -     -
    • - -
  • GNU gdb 4.18 - -
  • - - - - Debugging with GDB
    • -
  • - - - - GDB Internals
    • -
  • - - - - STABS Debugging Format
    • -
  • - - - - GDB Quick Reference Card
    • -     -
    • - -
  • Newlib 1.8.2 - -
  • - - - - libc
    • -
  • - - - - libm
    • -     -
    • - -
  • GNU Libraries Used by Multiple Tools - -
  • - - - - GNU History Library
    • -
  • - - - - GNU Readline Library
    • -
  • - - - - GNU Memory-Mapped Malloc Library (mmalloc)
    • -
  • - - - - GNU Binary File Descriptor (libbfd)
    • -     - -
    • -
  • General GNU Project Documentation - -
  • - - - - - - - GNU Coding Standards
    • -     -
    • -     -
    -Copyright © 1988-1999 OAR Corporation - diff --git a/doc/gnu_docs/mk_install_dir b/doc/gnu_docs/mk_install_dir deleted file mode 100644 index 52ef35287b..0000000000 --- a/doc/gnu_docs/mk_install_dir +++ /dev/null @@ -1,29 +0,0 @@ -#! /bin/sh -# -# This script creates the install infrastructure for the GNU tools -# documentation. -# - -install=/usr3/rtems_cds/test_cd/doc/tools - -#if [ $? -ne 1 ] ; then -# echo "Usage: $0 install_directory" -# exit 1 -#fi - -rm -rf ${install} -mkdir ${install} -mkdir ${install}/info -mkdir ${install}/html - -cp rtems_tools_index.html ${install}/../index.html -cp index.html ${install}/html -cp ../BAD.html ${install}/html -cp ../tools/texi2www/*.gif ${install}/html -cp ../common/*arrow.gif ${install}/html -cp ../common/up-arrow.gif ${install}/html -cp ../common/oaronly.jpg ${install}/html -cp ../common/dvi.gif ${install}/html -cp ../common/pdf.gif ${install}/html -cp ../common/pdf1.gif ${install}/html -cp ../common/ps.gif ${install}/html diff --git a/doc/gnu_docs/refcard.html b/doc/gnu_docs/refcard.html deleted file mode 100644 index 0e96d95ac2..0000000000 --- a/doc/gnu_docs/refcard.html +++ /dev/null @@ -1,13 +0,0 @@ - -GDB Reference Card - - - OAR -

    RTEMS On-Line Library

    -
    - -The GDB Reference card is not written in texinfo file. There is currently -no HTML or PDF version of this file. -
    -Copyright © 1988-1999 OAR Corporation - diff --git a/doc/gnu_docs/rtems_tools_index.html b/doc/gnu_docs/rtems_tools_index.html deleted file mode 100644 index 38f83be513..0000000000 --- a/doc/gnu_docs/rtems_tools_index.html +++ /dev/null @@ -1,15 +0,0 @@ - -RTEMS and Tools On-Line Library - - - OAR -

    RTEMS and Tools On-Line Library

    -
    - - -
  • RTEMS Documentation
    • -
  • GNU Documentation
    • -     -
    -Copyright © 1988-1999 OAR Corporation - diff --git a/doc/index.html b/doc/index.html deleted file mode 100644 index 4ad742870f..0000000000 --- a/doc/index.html +++ /dev/null @@ -1,275 +0,0 @@ - -RTEMS RTEMS_VERSION On-Line Library - - - OAR -

    RTEMS RTEMS_VERSION On-Line Library

    -
    - - -
  • - - - - - - - RTEMS FAQ -
    • -
  • C/C++ Manuals
    • - -
  • - - - - - - - Getting Started with RTEMS for C/C++ Users -
    • - -
  • - - - - - - - RTEMS Applications C User's Guide -
    • - -
  • - - - - - - - RTEMS POSIX API User's Guide -
    • - -
  • - - - - - - - RTEMS ITRON 3.0 API User's Guide -
    • - -
  • - - - - - - - RTEMS Network Supplement -
    • -     -
  • Ada Manuals
    • - -
  • - - - - - - - Getting Started with GNAT/RTEMS -
    • -
  • - - - - - - - RTEMS Applications Ada User's Guide -
    • -     -
  • Miscellaneous Manuals
    • - -
  • - - - - - - - RTEMS Development Environment Guide -
    • - -
  • - - - - - - - RTEMS/GDB User's Guide -
    • - -
  • - - - - - - - RTEMS Remote Debugger Server Specifications -
    • - -
  • - - - - - - - RTEMS BSP and Device Driver Development Guide -
    • - -
  • - - - - - - - RTEMS Porting Guide -
    • - -
  • - - - - - - - RTEMS Filesystem Design Guide -
    • - -
  • - - - - - - - RTEMS POSIX 1003.1 Compliance Guide -
    • -     - - -
  • CPU Supplements - - -
  • - - - - - - - RTEMS AMD 29K Applications Supplement -
    • - -
  • - - - - - - - RTEMS Hitachi SH Applications Supplement -
    • - -
  • - - - - - - - RTEMS Intel i386 Applications Supplement -
    • - -
  • - - - - - - - RTEMS Intel i960 Applications Supplement -
    • - -
  • - - - - - - - RTEMS MIPS64 ORION Applications Supplement -
    • - -
  • - - - - - - - RTEMS Motorola MC68xxx Applications Supplement -
    • - -
  • - - - - - - - RTEMS PowerPC Applications Supplement -
    • - -
  • - - - - - - - RTEMS SPARC Applications Supplement -
    • - -
  • - - - - - - - RTEMS Hewlett Packard PA-RISC Applications Supplement -
    • - -
  • - - - - - - - RTEMS UNIX Port Applications Supplement -
    • - -     -
    • - -     -
    -Copyright © 1988-2000 OAR Corporation - diff --git a/doc/itron3.0/Makefile b/doc/itron3.0/Makefile deleted file mode 100644 index d3defd1fb8..0000000000 --- a/doc/itron3.0/Makefile +++ /dev/null @@ -1,133 +0,0 @@ -# -# COPYRIGHT (c) 1988-1999. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=itron - -include ../Make.config - -all: html info ps pdf - -dirs: - $(make-dirs) - -COMMON_FILES= - -GENERATED_FILES= \ - status.texi \ - task.texi tasksync.texi semaphore.texi eventflags.texi mailbox.texi \ - msgbuffer.texi rendezvous.texi interrupt.texi memorypool.texi \ - fixedblock.texi time.texi config.texi network.texi - -FILES= $(PROJECT).texi \ - $(COMMON_FILES) preface.texi $(GENERATED_FILES) - -INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*) - -info: $(FILES) $(PROJECT) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: $(PROJECT).dvi -ps: $(PROJECT).ps -pdf: $(PROJECT).pdf - -$(PROJECT).pdf: $(FILES) - $(TEXI2PDF) $(PROJECT).texi - cp $(PROJECT).pdf $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).ps: $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(WWW_INSTALL)/$(PROJECT) - -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - cp $(PROJECT).dvi $(WWW_INSTALL)/$(PROJECT) - -html: $(FILES) - -mkdir -p html - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -clean: - rm -f *.o $(PROG) *.txt core *.html - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* _* $(GENERATED_FILES) $(PROJECT).pdf - rm -rf html - -status.texi: status.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -task.texi: task.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -tasksync.texi: tasksync.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -semaphore.texi: semaphore.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -eventflags.texi: eventflags.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -mailbox.texi: mailbox.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -msgbuffer.texi: msgbuffer.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -rendezvous.texi: rendezvous.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -interrupt.texi: interrupt.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -memorypool.texi: memorypool.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -fixedblock.texi: fixedblock.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -time.texi: time.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -config.texi: config.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - -network.texi: network.t Makefile - $(BMENU) -p "" \ - -u "Top" \ - -n "" ${*}.t - diff --git a/doc/itron3.0/config.t b/doc/itron3.0/config.t deleted file mode 100644 index 8ce07e88d2..0000000000 --- a/doc/itron3.0/config.t +++ /dev/null @@ -1,187 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c This is the chapter from the RTEMS ITRON User's Guide that -@c documents the services provided by the system -@c manager. -@c -@c $Id$ -@c - -@chapter System Manager - -@section Introduction - -The -system manager is ... - -The services provided by the system manager are: - -@itemize @bullet -@item @code{get_ver} - Get Version Information -@item @code{ref_sys} - Reference Semaphore Status -@item @code{ref_cfg} - Reference Configuration Information -@item @code{def_svc} - Define Extended SVC Handler -@item @code{def_exc} - Define Exception Handler -@end itemize - -@section Background - -@section Operations - -@section System Calls - -This section details the system manager's services. -A subsection is dedicated to each of this manager's services -and describes the calling sequence, related constants, usage, -and status codes. - - -@c -@c get_ver -@c - -@page -@subsection get_ver - Get Version Information - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER get_ver( - T_VER *pk_ver -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{EXXX} - - -@subheading DESCRIPTION: - -@subheading NOTES: - - -@c -@c ref_sys -@c - -@page -@subsection ref_sys - Reference Semaphore Status - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER ref_sys( - T_RSYS *pk_rsys -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{EXXX} - - -@subheading DESCRIPTION: - -@subheading NOTES: - - -@c -@c ref_cfg -@c - -@page -@subsection ref_cfg - Reference Configuration Information - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER ref_cfg( - T_RCFG *pk_rcfg -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{EXXX} - - -@subheading DESCRIPTION: - -@subheading NOTES: - - -@c -@c def_svc -@c - -@page -@subsection def_svc - Define Extended SVC Handler - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER def_svc( - FN s_fncd, - T_DSVC *pk_dsvc -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{EXXX} - - -@subheading DESCRIPTION: - -@subheading NOTES: - - -@c -@c def_exc -@c - -@page -@subsection def_exc - Define Exception Handler - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER def_exc( - UINT exckind, - T_DEXC *pk_dexc -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{EXXX} - - -@subheading DESCRIPTION: - -@subheading NOTES: - diff --git a/doc/itron3.0/eventflags.t b/doc/itron3.0/eventflags.t deleted file mode 100644 index 00ef21d72f..0000000000 --- a/doc/itron3.0/eventflags.t +++ /dev/null @@ -1,860 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c This is the chapter from the RTEMS ITRON User's Guide that -@c documents the services provided by the eventflags -@c manager. -@c -@c $Id$ -@c - -@chapter Eventflags Manager - -@section Introduction - -The eventflag manager provides a high performance method of intertask communication and synchronization. The directives provided by the eventflag manager are: - -The services provided by the eventflags manager are: - -@itemize @bullet -@item @code{cre_flg} - Create Eventflag -@item @code{del_flg} - Delete Eventflag -@item @code{set_flg} - Set Eventflag -@item @code{clr_flg} - Clear Eventflag -@item @code{wai_flg} - Wait on Eventflag -@item @code{pol_flg} - Wait for Eventflag (Polling) -@item @code{twai_flg} - Wait on Eventflag with Timeout -@item @code{ref_flg} - Reference Eventflag Status -@end itemize - -@section Background - -@subsection Event sets - -An eventflag is used by a task (or ISR) to inform another task of the -occurrence of a significant situation. One word bit-field is associated with each eventflags. The application developer should remember the -following key characteristics of event operations when utilizing the event -manager: - -@itemize @bullet -@item Events provide a simple synchronization facility. -@item Events are aimed at tasks. -@item Tasks can wait on more than one event simultaneously. -@item Events are independent of one another. -@item Events do not hold or transport data. -@item Events are not queued. In other words, if an event is sent more than once to a task before being received, the second and subsequent send operations to that same task have no effect. -@end itemize - -A pending event is an event that has been set. An -event condition is used to specify the events which the task desires to -receive and the algorithm which will be used to determine when the request -is satisfied. An event condition is satisfied based upon one of two -algorithms which are selected by the user. The @code{TWF_ORW} algorithm -states that an event condition is satisfied when at least a single -requested event is posted. The @code{TWF_ANDW} algorithm states that an -event condition is satisfied when every requested event is posted. - -An eventflags or condition is built by a bitwise OR of the desired events. -If an event is not explicitly specified in the set or condition, then it -is not present. Events are specifically designed to be mutually exclusive, -therefore bitwise OR and addition operations are equivalent as long as -each event appears exactly once in the event set list. - -@subsection T_CFLG Structure - -The T_CFLG structire is used to define the characteristics of an eventflag -and passed as an argument to the @code{cre_flg} service. The structure is -defined as follows: - -@example - -/* - * Create Eventflags (cre_flg) Structure - */ - -typedef struct t_cflg @{ - VP exinf; /* extended information */ - ATR flgatr; /* eventflag attribute */ - UINT iflgptn; /* initial eventflag */ - /* additional implementation dependent information may be included */ -@} T_CFLG; - -/* - * flgatr - Eventflag Attribute Values - */ - - -/* multiple tasks are not allowed to wait (Wait Single Task)*/ - -#define TA_WSGL 0x00 - -/* multiple tasks are allowed to wait (Wait Multiple Task) */ - -#define TA_WMUL 0x08 - -/* wfmode */ -#define TWF_ANDW 0x00 /* AND wait */ -#define TWF_ORW 0x02 /* OR wait */ -#define TWF_CLR 0x01 /* clear specification */ -@end example - -where the meaning of each field is: - -@table @b - -@item exinf - -may be used freely by the user for including extended information about -the eventflag to be created. Information set here may be accessed by -@code{ref_flg}. If a larger region is desired for including user information, or -if the user wishes to change the contents of this information, the usr -should allocate memory area and set the address of this memory packet to -@code{exinf}. The OS does not take care of the contents of @code{exinf}. This -implementation does not use this field. - -@item flgatr - -is the attributes for this eventflag. The lower bits of flgatr represent -system attributes, while the upper bits represent implementation-dependent -attributes. - -@item iflgptn - -is the initial eventflag pattern. -(CPU and/or implementation-dependent information may also be included) - -@end table - -@subsection T_RFLG Structure - -The T_RFLG structire is used to define the characteristics of an eventflag -and passed as an argument to the @code{ref_flg} service. The structure is -defined as follows: - -@example -/* Reference Eventflags (ref_flg) Structure */ -typedef struct t_rflg @{ - VP exinf; /* extended information */ - BOOL_ID wtsk; /* indicates whether or not there is a waiting task */ - UINT flgptn; /* eventflag bit pattern */ - /* additional implementation dependent information may be included */ -@} T_RFLG; -@end example - -@table @b - -@item exinf - -see @code{T_CFLG}. - -@item wtsk - -indicates whether or not there is a task waiting for the eventflag in -question. If there is no waiting task, @code{wtsk} is returned as FALSE = 0. -If there is a waiting task, @code{wtsk} is returned as a value other than 0. - -@item flgptn - -is the eventflag pattern. - -@end table - -@section Operations - -@section System Calls - -This section details the eventflags manager's services. A subsection is -dedicated to each of this manager's services and describes the calling -sequence, related constants, usage, and status codes. - - -@c -@c cre_flg -@c - -@page -@subsection cre_flg - Create Eventflag - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER cre_flg( - ID flgid, - T_CFLG *pk_cflg -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_NOMEM} - Insufficient memory (Memory for control block cannot be -allocated) - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_RSATR} - Reserved attribute (flgatr was invalid or could not be -used) - -@code{E_OBJ} - Invalid object state (an eventflag of the same ID already -exists) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (pk_cflg is invalid) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_CTXID} - Specified an object on another node when the system call -was issued from a task in dispatch disabled state or from a -task-independent portion - -@code{EN_PAR}- A value outside the range supported by the target node -and/or transmission packet format was specified as a parameter (a value -outside supported range was specified for exinf, flgatr and/or iflgptn) - -@subheading DESCRIPTION: - -This system call creates the eventflag specified by @code{flgid}. -Specifically, a control block for the eventflag to be created is allocated -and the associated flag pattern is initialized using @code{iflgptn}. A -single eventflag handles one word's worth of bits of the processor in -question as a group. All operations are done in single word units. - -User eventflags have positive ID numbers, while system eventflags have -negative ID numbers. User tasks (tasks having positive task IDs) cannot -access system eventflags. An @code{E_OACV} error will result if a user -task issues a system call on a system eventflag, but error detection is -implementation dependent. - -Eventflags having ID numbers from -4 through 0 cannot be created. An -@code{E_ID} error will result if a value in this range is specified for -@code{flgid}. - -The system attribute part of @code{flgatr} may be specified as @code{TA_WSGL} -(Wait Single Task) or @code{TA_WMUL} (Wait Multiple Tasks) - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - -All memory is preallocated for @code{RTEMS ITRON} objects. Thus, no -dynamic memory allocation is performed by @code{cre_flg} and the -@code{E_NOMEM} error can not be returned. - -@c -@c del_flg -@c - -@page -@subsection del_flg - Delete Eventflag - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER del_flg( - ID flgid -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_CTXID} - Specified an object on another node when the system call -was issued from a task in dispatch disabled state or from a -task-independent portion - -@subheading DESCRIPTION: - -This system call deletes the eventflag specified by @code{flgid}. - -Issuing this system call causes memory used for the control block of the -associated eventflag to be released. After this system call is invoked, -another eventflag having the same ID number can be created. - -This system call will complete normally even if there are tasks waiting -for the eventflag. In that case, an @code{E_DLT} error will be returned -to each waiting task. - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - -When an eventflag being waited for by more than one tasks is deleted, the -order of tasks on the ready queue after the WAIT state is cleared is -implementation dependent in the case of tasks having the same priority. - -@c -@c set_flg -@c - -@page -@subsection set_flg - Set Eventflag - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER set_flg( - ID flgid, - UINT setptn -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_CTXID} - Specified an object on another node when the system call -was issued from a task in dispatch disabled state or from a -task-independent portion - -@code{EN_PAR} - A value outside the range supported by the target node -and/or transmission packet format was specified as a parameter (a value -outside supported range was specified for setptn or clrptn) - -@subheading DESCRIPTION: - -The @code{set_flg} system call sets the bits specified by @code{setptn} of the -one word eventflag specified by @code{flgid}. In other words, a logical -sum is taken for the values of the eventflag specified by @code{flgid} with the -value of @code{setptn}. - -If the eventflag value is changed by @code{set_flg} and the new eventflag -value satisfies the condition to release the WAIT state of the task which -issued @code{wai_flg} on the eventflag, the WAIT state of that task will -be released and the task will be put into RUN or READY state (or SUSPEND -state if the task was in WAIT-SUSPEND). - -Nothing will happen to the target eventflag if all bits of @code{setptn} -are specified as 0 with @code{set_flg}. No error will result in either -case. - -Multiple tasks can wait for a single eventflag if that eventflags has the -@code{TA_WMUL} attribute. This means that even eventflags can make queues -for tasks to wait on. When such eventflags are used, a single -@code{set_flg} call may result in the release of multiple waiting tasks. -In this case, the order of tasks on the ready queue after the WAIT state -is cleared is preserved for tasks having the same priority. - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - -@c -@c clr_flg -@c - -@page -@subsection clr_flg - Clear Eventflag - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER clr_flg( - ID flgid, - UINT clrptn -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_CTXID} - Specified an object on another node when the system call -was issued from a task in dispatch disabled state or from a -task-independent portion - -@code{EN_PAR} - A value outside the range supported by the target node -and/or transmission packet format was specified as a parameter (a value -outside supported range was specified for setptn or clrptn) - -@subheading DESCRIPTION: - -The @code{clr_flg} system call clears the bits of the one word eventflag -based on the corresponding zero bits of @code{clrptn}. In other words, a -logical product is taken for the values of the eventflag specified by -@code{flgid} with the value of @code{clrptn}. - -Issuing @code{clr_flg} never results in wait conditions being released on -a task waiting for the specified eventflag. In other words, dispatching -never occurs with @code{clr_flg}. - -Nothing will happen to the target eventflag if all bits of @code{clrptn} -are specified as 1 with @code{clr_flg}. No error will result. - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - -@c -@c wai_flg -@c - -@page -@subsection wai_flg - Wait on Eventflag - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER wai_flg( - UINT *p_flgptn, - ID flgid, - UINT waiptn, - UINT wfmode -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (waiptn = 0, wfmode invalid, or tmout is -2 -or less) - -@code{E_OBJ} - Invalid object state (multiple tasks waiting for an -eventflag with the TA_WSGL attribute) - -@code{E_DLT} - The object being waited for was deleted (the specified -eventflag was deleted while waiting) - -@code{E_RLWAI} - WAIT state was forcibly released (rel_wai was received -while waiting) - -@code{E_TMOUT} - Polling failure or timeout exceeded - -@code{E_CTX} - Context error (issued from task-independent portions or a -task in dispatch disabled state) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_PAR} - A value outside the range supported by the target node -and/or transmission packet format was specified as a parameter (a value -outside supported range was specified for waiptn and tmout) - -@code{EN_RPAR} - A value outside the range supported by the requesting -node and/or transmission packet format was specified as a parameter (a -value exceeding the range for the requesting node was specified for -flgptn) - -@subheading DESCRIPTION: - -The @code{wai_flg} system call waits for the eventflag specified by -@code{flgid} to be set to satisfy the wait release condition specified by -@code{wfmode}. The Eventflags bit-pattern will be returned with a pointer @code{p_flgptn}. - -If the eventflag specified by @code{flgid} already satisfies the wait -release conditions given by @code{wfmode}, the issuing task will continue -execution without waiting. @code{wfmode} may be specified as follows. - -@example - wfmode = TWF_ANDW (or TWF_ORW) | TWF_CLR(optional) -@end example - -If @code{TWF_ORW} is specified, the issuing task will wait for any of the -bits specified by @code{waiptn} to be set for the eventflag given by -@code{flgid} (OR wait). If @code{TWF_ANDW} is specified, the issuing task -will wait for all of the bits specified by @code{waiptn} to be set for the -eventflag given by @code{flgid} (AND wait). - -If the @code{TWF_CLR} specification is not present, the eventflag value -will remain unchanged even after the wait conditions have been satisfied -and the task has been released from the WAIT state. If @code{TWF_CLR} is -specified, all bits of the eventflag will be cleared to 0 once the wait -conditions of the waiting task have been satisfied. - -The return parameter @code{flgptn} returns the value of the eventflag after the -wait state of a task has been released due to this system call. If -@code{TWF_CLR} was specified, the value before eventflag bits were cleared -is returned. The value returned by @code{flgptn} fulfills the wait -release conditions of this system call. - -An @code{E_PAR} parameter error will result if @code{waiptn} is 0. - -A task can not execute any of @code{wai_flg, twai_flg} or @code{pol_flg} -on an eventflag having the @code{TA_WSGL} attribute if another task is -already waiting for that eventflag. An @code{E_OBJ} error will be -returned to a task which executes @code{wai_flg} at a later time -regardless as to whether or not the task that executes @code{wai_flg} or -@code{twai_flg} later will be placed in a WAIT state (conditions for -releasing wait state be satisfied). An @code{E_OBJ} error will be -returned even to tasks which just execute @code{pol_flg}, again regardless -as to whether or not wait release conditions for that task were satisfied. - -On the other hand, multiple tasks can wait at the same time for the same -eventflag if that eventflag has the @code{TA_WMUL} attribute. This means -that event flags can make queues for tasks to wait on. When such -eventflags are used, a single @code{set_flg} call may release multiple -waiting tasks. - -The following processing takes place if a queue for allowing multiple -tasks to wait has been created for an eventflag with the @code{TA_WMUL} -attribute. - -@itemize @bullet - -@item The waiting order on the queue is FIFO. (However, depending on -@code{waiptn} and @code{wfmode}, task at the head of the queue will not -always be released from waiting.) - -@item If a task specifying that the eventflag be cleared is on the queue, -the flag is cleared when that task is released from waiting. - -@item Since any tasks behind a task which clears the eventflag (by -specifying @code{TWF_CLR}) will check the eventflag after it is cleared, -they will not be released from waiting. - -@end itemize - -If multiple tasks having the same priority are released from waiting -simultaneously due to @code{set_flg}, the order of tasks on the ready -queue after release will be the same as their original order on the -eventflag queue. - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - - -@c -@c pol_flg -@c - -@page -@subsection pol_flg - Wait for Eventflag (Polling) - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER pol_flg( - UINT *p_flgptn, - ID flgid, - UINT waiptn, - UINT wfmode -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (waiptn = 0, wfmode invalid, or tmout is -2 -or less) - -@code{E_OBJ} - Invalid object state (multiple tasks waiting for an -eventflag with the TA_WSGL attribute) - -@code{E_DLT} - The object being waited for was deleted (the specified -eventflag was deleted while waiting) - -@code{E_RLWAI} - WAIT state was forcibly released (rel_wai was received -while waiting) - -@code{E_TMOUT} - Polling failure or timeout exceeded - -@code{E_CTX} - Context error (issued from task-independent portions or a -task in dispatch disabled state) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_PAR} - A value outside the range supported by the target node -and/or transmission packet format was specified as a parameter (a value -outside supported range was specified for waiptn and tmout) - -@code{EN_RPAR} - A value outside the range supported by the requesting -node and/or transmission packet format was specified as a parameter (a -value exceeding the range for the requesting node was specified for -flgptn) - -@subheading DESCRIPTION: - -The @code{pol_flg} system call has the same function as @code{wai_flg} -except for the waiting feature. @code{pol_flg} polls whether or not the -task should wait if @code{wai_flg} is executed. The meanings of -parameters to @code{pol_flg} are the same as for @code{wai_flg}. The -specific operations by @code{pol_flg} are as follows. - -@itemize @bullet - -@item If the target eventflag already satisfies the conditions for -releasing wait given by @code{wfmode}, processing is the same as -@code{wai_flg}: the eventflag is cleared if @code{TWF_CLR} is specified -and the system call completes normally. - -@item If the target eventflag does not yet satisfy the conditions for -releasing wait given by @code{wfmode}, an @code{E_TMOUT} error is returned to -indicate polling failed and the system call finishes. Unlike -@code{wai_flg}, the issuing task does not wait in this case. The eventflag -is not cleared in this case even if @code{TWF_CLR} has been specified. - -@end itemize - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - - -@c -@c twai_flg -@c - -@page -@subsection twai_flg - Wait on Eventflag with Timeout - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER twai_flg( - UINT *p_flgptn, - ID flgid, - UINT waiptn, - UINT wfmode, - TMO tmout -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (waiptn = 0, wfmode invalid, or tmout is -2 -or less) - -@code{E_OBJ} - Invalid object state (multiple tasks waiting for an -eventflag with the TA_WSGL attribute) - -@code{E_DLT} - The object being waited for was deleted (the specified -eventflag was deleted while waiting) - -@code{E_RLWAI} - WAIT state was forcibly released (rel_wai was received -while waiting) - -@code{E_TMOUT} - Polling failure or timeout exceeded - -@code{E_CTX} - Context error (issued from task-independent portions or a -task in dispatch disabled state) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_PAR} - A value outside the range supported by the target node -and/or transmission packet format was specified as a parameter (a value -outside supported range was specified for waiptn and tmout) - -@code{EN_RPAR} - A value outside the range supported by the requesting -node and/or transmission packet format was specified as a parameter (a -value exceeding the range for the requesting node was specified for -flgptn) - -@subheading DESCRIPTION: - -The @code{twai_flg} system call has the same function as @code{wai_flg} -with an additional timeout feature. A maximum wait time (timeout value) -can be specified using the parameter @code{tmout}. When a timeout is specified, -a timeout error, @code{E_TMOUT}, will result and the system call will -finish if the period specified by @code{tmout} elapses without conditions for -releasing wait being satisfied. - -Specifying @code{TMO_POL = 0} to @code{twai_flg} for @code{tmout} indicates that -a timeout value of 0 be used, resulting in exactly the same processing as -@code{pol_flg}. Specifying @code{TMO_FEVR = -1} to @code{twai_flg} for -@code{tmout} indicates that an infinite timeout value be used, resulting in -exactly the same processing as @code{wai_flg}. - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - - -@code{Pol_flg} and @code{wai_flg} represent the same processing as -specifying certain values (@code{TMO_POL} or @code{TMO_FEVR}) to -@code{twai_flg} for tmout. As such, only @code{twai_flg} is implemented -in the kernel; @code{pol_flg} and @code{wai_flg} should be implemented as macros -which call @code{twai_flg}. - -@c -@c ref_flg -@c - -@page -@subsection ref_flg - Reference Eventflag Status - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER ref_flg( - T_RFLG *pk_rflg, - ID flgid ); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (flgid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the eventflag specified by flgid -does not exist) - -@code{E_OACV} - Object access violation (A flgid less than -4 was -specified from a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (the packet address for the return -parameters could not be used) - -@code{EN_OBJNO} - An object number which could not be accessed on the -target node is specified. - -@code{EN_CTXID} - Specified an object on another node when the system call -was issued from a task in dispatch disabled state or from a -task-independent portion - -@code{EN_RPAR} - A value outside the range supported by the requesting -node and/or transmission packet format was returned as a parameter (a -value outside supported range was specified for exinf, wtsk and/or flgptn) - -@subheading DESCRIPTION: - -This system call refers to the state of the eventflag specified by -@code{flgid}, and returns its current flag pattern (@code{flgptn}), -waiting task information (@code{wtsk}), and its extended information -(@code{exinf}). - -Depending on the implementation, @code{wtsk} may be returned as the ID -(non-zero) of the task waiting for the eventflag. If there are multiple -tasks waiting for the eventflag (only when attribute is @code{TA_WMUL}), -the ID of the task at the head of the queue is returned. - -An @code{E_NOEXS} error will result if the eventflag specified to -@code{ref_flg} does not exist. - -@subheading NOTES: - -Multiprocessing is not supported. Thus none of the "@code{EN_}" status -codes will be returned. - -Although both @code{ref_flg} and @code{pol_flg} can be used to find an -eventflag's pattern (@code{flgptn}) without causing the issuing task to -wait, @code{ref_flg} simply reads the eventflag's pattern (@code{flgptn}) -while @code{pol_flg} functions is identical to @code{wai_flg} when wait -release conditions are satisfied (it clears the eventflag if -@code{TWF_CLR} is specified). - -Depending on the implementation, additional information besides -@code{wtsk} and @code{flgptn} (such as eventflag attributes, -@code{flgatr}) may also be referred. diff --git a/doc/itron3.0/fixedblock.t b/doc/itron3.0/fixedblock.t deleted file mode 100644 index aeea19d40b..0000000000 --- a/doc/itron3.0/fixedblock.t +++ /dev/null @@ -1,389 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c This is the chapter from the RTEMS ITRON User's Guide that -@c documents the services provided by the fixed block -@c manager. -@c -@c $Id$ -@c - -@chapter Fixed Block Manager - -@section Introduction - -The fixed block manager provides functions for creating, deleting, getting, polling, getting with timeout, releasing, and referencing the fixed-sized memorypool. This manager is based on ITRON 3.0 standard. - -The services provided by the fixed block manager are: - -@itemize @bullet -@item @code{cre_mpf} - Create Fixed-Size Memorypool -@item @code{del_mpf} - Delete Fixed-Size Memorypool -@item @code{get_blf} - Get Fixed-Size Memory Block -@item @code{pget_blf} - Poll and Get Fixed-Size Memory Block -@item @code{tget_blf} - Get Fixed-Size Memory Block with Timeout -@item @code{rel_blf} - Release Fixed-Size Memory Block -@item @code{ref_mpf} - Reference Fixed-Size Memorypool Status -@end itemize - -@section Background - -@section Operations - -@section System Calls - -This section details the fixed block manager's services. -A subsection is dedicated to each of this manager's services -and describes the calling sequence, related constants, usage, -and status codes. - - -@c -@c cre_mpf -@c - -@page -@subsection cre_mpf - Create Fixed-Size Memorypool - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER cre_mpf( - ID mpfid, - T_CMPF *pk_cmpf -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_NOMEM} - Insufficient memory (Memory for control block and/or for -memorypool cannot be allocated) - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_RSATR} - Reserved attribute (mpfatr was invalid or could not be used) - -@code{E_OBJ} - Invalid object state (a memorypool of the same ID already exists) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from -a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (pk_cmpf is invalid or mpfsz and/or blfsz is -negative or invalid) - -@subheading DESCRIPTION: - -This system call creates a fixed-size memorypool having the ID number specified by mpfid. Specifically, a memory area of a size based on values of mpfcnt and blfsz is reserved for use as a memorypool. A control block for the memorypool being created is also allocated. The get_blf system call specifying the memorypool created by this call can be issued to allocate memory blocks of the size given by blfsz (in bytes). - -@subheading NOTES: - -The memory area required for creating memorypools and for allocating control blocks for each object is allocated while system initialization. Associated parameters are therefore specified at system configuration. - -@c -@c del_mpf -@c - -@page -@subsection del_mpf - Delete Fixed-Size Memorypool - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER del_mpf( - ID mpfid -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the memorypool specified by mpfid does not exist) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from a user task. This is implementation dependent.) - -@subheading DESCRIPTION: - -This system call deletes the fixed-size memorypool specified by mpfid. No check or error report is performed even if there are tasks using memory from the memorypool to be deleted. This system call completes normally even if some of the memory blocks are not returned. Issuing this system call causes memory used for the control block of the associated memorypool and the memory area making up the memorypool itself to be released. After this system call is invoked, another memorypool having the same ID number can be created. This system call will complete normally even if there are tasks waiting to get memory blocks from the memorypool. In that case, an E_DLT error will be returned to each waiting task. - -@subheading NOTES: - -When a memorypool being waited for by more than one tasks is deleted, the order of tasks on the ready queue after the WAIT state is cleared is implementation dependent in the case of tasks having the same priority. - - -@c -@c get_blf -@c - -@page -@subsection get_blf - Get Fixed-Size Memory Block - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER get_blf( - VP *p_blf, - ID mpfid -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the memorypool specified by mpfid does not exist) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from -a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (tmout is -2 or less) - -@code{E_DLT} - The object being waited for was deleted (the specified memorypool -was deleted while waiting) - -@code{E_RLWAI} - WAIT state was forcibly released (rel_wai was received while -waiting) - -@code{E_TMOUT} - Polling failure or timeout exceeded - -@code{E_CTX} - Context error (issued from task-independent portions or a -task in dispatch disabled state; implementation dependent for pget_blf and tget_blf(tmout=TMO_POL)) - -@subheading DESCRIPTION: - -A memory block is allocated from the fixed-size memorypool specified by mpfid. The start address of the memory block allocated is returned to blf. The size of the memory block allocated is specified by the blfsz parameter when the fixed-size memorypool was created. The allocated memory block is not cleared to zero. The contents of the allocated memory block are undefined. If the memory block cannot be obtained from the specified memorypool when get_blf is issued, the task issuing get_blf will be placed on the memory allocation queue of the specified memorypool, and wait until it can get the memory it requires. If the object being waited for is deleted (the specified memorypool is deleted while waiting), an E_DLT error will be returned. - -@subheading NOTES: - -NONE - - -@c -@c pget_blf -@c - -@page -@subsection pget_blf - Poll and Get Fixed-Size Memory Block - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER ercd =pget_blf( - VP *p_blf, - ID mpfid -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the memorypool specified by mpfid does not exist) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from -a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (tmout is -2 or less) - -@code{E_DLT} - The object being waited for was deleted (the specified memorypool -was deleted while waiting) - -@code{E_RLWAI} - WAIT state was forcibly released (rel_wai was received while -waiting) - -@code{E_TMOUT} - Polling failure or timeout exceeded - -@code{E_CTX} - Context error (issued from task-independent portions or a -task in dispatch disabled state; implementation dependent for pget_blf and tget_blf(tmout=TMO_POL)) - -@subheading DESCRIPTION: - -The pget_blf system call has the same function as get_blf except for the waiting feature. Pget_blf polls whether or not the task should wait if get_blf is executed. The meaning of parameters to pget_blf are the same with get_blf. The specific operations by pget_blf are as follows. - - - If there is a free memory block available, processing is the same as - get_blf: that is, the requested memory is allocated and the system call - completes normally. - - - If there is no free memory block, an E_TMOUT error is returned to - indicate polling failed and the system call finishes. Unlike get_blf, - the issuing task does not wait in this case. Also, the issuing task - does not get any memory. - -@subheading NOTES: - -NONE - - -@c -@c tget_blf -@c - -@page -@subsection tget_blf - Get Fixed-Size Memory Block with Timeout - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER ercd =tget_blf( - VP *p_blf, - ID mpfid, - TMO tmout -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the memorypool specified by mpfid does not exist) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from -a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (tmout is -2 or less) - -@code{E_DLT} - The object being waited for was deleted (the specified memorypool -was deleted while waiting) - -@code{E_RLWAI} - WAIT state was forcibly released (rel_wai was received while -waiting) - -@code{E_TMOUT} - Polling failure or timeout exceeded - -@code{E_CTX} - Context error (issued from task-independent portions or a -task in dispatch disabled state; implementation dependent for pget_blf and tget_blf(tmout=TMO_POL)) - -@subheading DESCRIPTION: - -The tget_blf system call has the same function as get_blf with an additional timeout feature. A maximum wait time (timeout value) can be specified using the parameter tmout. When a timeout is specified, a timeout error, E_TMOUT, will result and the system call will finish if the period specified by tmout elapses without conditions for releasing wait being satisfied (i.e. without free memory becoming available). - -@subheading NOTES: - -NONE - -@c -@c rel_blf -@c - -@page -@subsection rel_blf - Release Fixed-Size Memory Block - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER rel_blf( - ID mpfid, - VP blf -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist (the memorypool specified by mpfid does not exist) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from -a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (blf is invalid or an attempt was made to return -the memory block to the wrong memorypool) - -@subheading DESCRIPTION: - -This system call releases the memory block specified by blf and returns it to the fixed-size memorypool specified by mpfid. Executing rel_blf allows memory to be allocated to the next task waiting for memory allocation from the memorypool given by mpfid, thus releasing that task from its WAIT state. - -@subheading NOTES: - -The fixed-size memorypool to which the memory block is returned must be the same memorypool from which it was originally allocated. An E_PAR error will result if an attempt is made to return a memory block to another memorypool than that from which it was originally allocated. - -@c -@c ref_mpf -@c - -@page -@subsection ref_mpf - Reference Fixed-Size Memorypool Status - -@subheading CALLING SEQUENCE: - -@ifset is-C -@example -ER ref_mpf( - T_RMPF *pk_rmpf, - ID mpfid -); -@end example -@end ifset - -@ifset is-Ada -@end ifset - -@subheading STATUS CODES: - -@code{E_OK} - Normal Completion - -@code{E_ID} - Invalid ID number (mpfid was invalid or could not be used) - -@code{E_NOEXS} - Object does not exist \(the memorypool specified by mpfid does -not exist.) - -@code{E_OACV} - Object access violation (A mpfid less than -4 was specified from -a user task. This is implementation dependent.) - -@code{E_PAR} - Parameter error (the packet address for the return parameters -could not be used) - -@subheading DESCRIPTION: - -This system call refers to the state of the fixed-size memorypool specified by mpfid, and returns the current number of free blocks (frbcnt), information of a task waiting to be allocated memory (wtsk), and its extended information (exinf). Wtsk indicates whether or not there is a task waiting to be allocated memory from the fixed-size memorypool specified. If there is no waiting task, wtsk is returned as FALSE = 0. If there is a waiting task, wtsk is returned as a value other than 0. - -@subheading NOTES: - -While the frsz return parameter of ref_mpl returns the total size of free memory, the frbcnt return parameter of ref_mpf returns the number of free blocks. - -Depending on the implementation, additional information besides wtsk and frbcnt (such as memorypool attributes, mpfatr) may also be referred. - diff --git a/doc/itron3.0/gen_all b/doc/itron3.0/gen_all deleted file mode 100644 index 6e4e66893f..0000000000 --- a/doc/itron3.0/gen_all +++ /dev/null @@ -1,4 +0,0 @@ -for i in config eventflags fixedblock interrupt mailbox memorypool msgbuffer network rendezvous task tasksync time -do - sh ./gen_section $i | tr -d "\r" >${i}.t -done diff --git a/doc/itron3.0/gen_section b/doc/itron3.0/gen_section deleted file mode 100644 index cdc1c80f2c..0000000000 --- a/doc/itron3.0/gen_section +++ /dev/null @@ -1,191 +0,0 @@ -# -# This shell script generates the starting template for a manager chapter. -# - - -# Set this based on which chapter you want to generate a template for. -chapter=$1 - -case ${chapter} in - task) - CHAPTER_CAPS="Task" - CHAPTER_LOWER="task" - ROUTINES=" cre_tsk del_tsk sta_tsk ext_tsk exd_tsk ter_tsk \ - dis_dsp ena_dsp chg_pri rot_rdq rel_wai get_tid ref_tsk" - ;; - - tasksync) - CHAPTER_CAPS="Task-Dependent Synchronization" - CHAPTER_LOWER="task-dependent synchronization" - ROUTINES=" sus_tsk rsm_tsk frsm_tsk \ - slp_tsk tslp_tsk wup_tsk can_wup" - ;; - - semaphore) - CHAPTER_CAPS="Semaphore" - CHAPTER_LOWER="semaphore" - ROUTINES="cre_sem del_sem sig_sem wai_sem preq_sem twai_sem ref_sem " - ;; - - eventflags) - CHAPTER_CAPS="Eventflags" - CHAPTER_LOWER="eventflags" - ROUTINES=" cre_flg del_flg set_flg clr_flg wai_flg pol_flg \ - twai_flg ref_flg " - ;; - - mailbox) - CHAPTER_CAPS="Mailbox" - CHAPTER_LOWER="mailbox" - ROUTINES="cre_mbx del_mbx snd_msg rcv_msg prcv_msg trcv_msg ref_mbx" - ;; - - msgbuffer) - CHAPTER_CAPS="Message Buffer" - CHAPTER_LOWER="message buffer" - ROUTINES=" cre_mbf del_mbf snd_mbf psnd_mbf tsnd_mbf rcv_mbf prcv_mbf \ - trcv_mbf ref_mbf " - ;; - - rendezvous) - CHAPTER_CAPS="Rendezvous" - CHAPTER_LOWER="rendezvous" - ROUTINES=" cre_por del_por cal_por pcal_por tcal_por acp_por pacp_por \ - tacp_por fwd_por rpl_rdv ref_por" - ;; - - interrupt) - CHAPTER_CAPS="Interrupt" - CHAPTER_LOWER="interrupt" - ROUTINES=" def_int ret_int ret_wup loc_cpu unl_cpu dis_int ena_int - chg_iXX ref_iXX" - ;; - - memorypool) - CHAPTER_CAPS="Memory Pool" - CHAPTER_LOWER="memory pool" - ROUTINES=" cre_mpl del_mpl get_blk pget_blk tget_blk rel_blk ref_mpl" - ;; - - fixedblock) - CHAPTER_CAPS="Fixed Block" - CHAPTER_LOWER="fixed block" - ROUTINES=" cre_mpf del_mpf get_blf pget_blf tget_blf rel_blf ref_mpf" - ;; - - - time) - CHAPTER_CAPS="Time" - CHAPTER_LOWER="time" - ROUTINES=" get_tim set_tim dly_tsk \ - def_cyc act_cyc ref_cyc \ - def_alm ref_alm ret_tmr" - ;; - - config) - CHAPTER_CAPS="System" - CHAPTER_LOWER="system" - ROUTINES=" get_ver ref_sys ref_cfg def_svc def_exc" - ;; - - network) - CHAPTER_CAPS="Network Support" - CHAPTER_LOWER="network support" - ROUTINES=" nrea_dat nwri_dat nget_nod nget_ver" - ;; - psxtimer) - CHAPTER_CAPS="Timer" - CHAPTER_LOWER="timer" - ROUTINES="timer_create timer_delete timer_settime timer_gettime timer_getoverrun" - ;; - *) - echo "Unknown chapter name" - exit 1 - ;; -esac - -if [ "x${CHAPTER_CAPS}" = "x" -o "x${CHAPTER_LOWER}" = "x" \ - -o "x${ROUTINES}" = "x" ] ; then - echo "initialization problem" - exit 1 -fi - -echo "@c" -echo "@c This is the chapter from the RTEMS ITRON User's Guide that" -echo "@c documents the services provided by the ${CHAPTER_LOWER}" -echo "@c manager." -echo "@c" -echo "@c \$Id\$" -echo "@c" -echo "" -echo "@chapter ${CHAPTER_CAPS}" Manager -echo "" -echo "@section Introduction" -echo "" -echo "The " -echo "${CHAPTER_LOWER} manager is ..." -echo "" -echo "The services provided by the ${CHAPTER_LOWER} manager are:" -echo "" -echo "@itemize @bullet" - -for routine in ${ROUTINES} -do - description=`grep " ${routine} " ../../itron_spec/itron3-1.txt | grep "]" | cut -d']' -f2 ` - description=`echo ${description}` - echo "@item @code{${routine}} - ${description}" -done -echo "@end itemize" - -echo "" -echo "@section Background" -echo "" -echo "@section Operations" -echo "" -echo "@section System Calls" -echo "" -echo "This section details the ${CHAPTER_LOWER} manager's services." -echo "A subsection is dedicated to each of this manager's services" -echo "and describes the calling sequence, related constants, usage," -echo "and status codes." -echo "" - -for routine in ${ROUTINES} -do - description=`grep ${routine} ../../itron_spec/itron3-1.txt | grep "]" | cut -d']' -f2` - description=`echo -n ${description}` - echo "" - echo "@c" - echo "@c ${routine}" - echo "@c" - echo "" - echo "@page" - echo "@subsection ${routine} - " ${description} - echo "" - echo "@subheading CALLING SEQUENCE:" - echo "" - echo "@ifset is-C" - echo "@example" - proto=`grep "${routine} (" ../../itron_spec/itron3-6.txt | sed -e 's/ercd = //'` # | sed -e 's/ \\(/(/'` - - echo `echo -n ${proto} | cut -d'(' -f1`"(" - echo ${proto} | cut -d'(' -f2 | sed -e 's/ .;//' - echo ");" - # echo "int ${routine}(" - # echo ");" - echo "@end example" - echo "@end ifset" - echo "" - echo "@ifset is-Ada" - echo "@end ifset" - echo "" - echo "@subheading STATUS CODES:" - echo "" - echo "@code{EXXX} - " - echo "" - echo "@subheading DESCRIPTION:" - echo "" - echo "@subheading NOTES:" - echo "" -done - diff --git a/doc/itron3.0/gen_status_shell b/doc/itron3.0/gen_status_shell deleted file mode 100644 index 1f3f8e4c47..0000000000 --- a/doc/itron3.0/gen_status_shell +++ /dev/null @@ -1,230 +0,0 @@ -# -# This shell script generates the starting template for a manager chapter. -# - -FILES="task tasksync semaphore eventflags mailbox msgbuffer rendezvous interrupt memorypool fixedblock time config network" - - -cat <