Changeset 2bf21fc8 in rtems


Ignore:
Timestamp:
Dec 1, 2008, 4:07:40 PM (11 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, master
Children:
86c3d41
Parents:
2b90266
Message:

2008-12-01 Joel Sherrill <joel.sherrill@…>

  • ada_user/Makefile.am, user/Makefile.am, user/concepts.t: Add 16 bit object Id format information.
  • user/ObjectId-16Bits.eps, user/ObjectId-16Bits.png: New files.
Location:
doc
Files:
2 added
4 edited

Legend:

Unmodified
Added
Removed
  • doc/ChangeLog

    r2b90266 r2bf21fc8  
     12008-12-01      Joel Sherrill <joel.sherrill@oarcorp.com>
     2
     3        * ada_user/Makefile.am, user/Makefile.am, user/concepts.t: Add 16 bit
     4        object Id format information.
     5        * user/ObjectId-16Bits.eps, user/ObjectId-16Bits.png: New files.
     6
    172008-12-01      Joel Sherrill <joel.sherrill@OARcorp.com>
    28
  • doc/ada_user/Makefile.am

    r2b90266 r2bf21fc8  
    2525    $(top_builddir)/user/preface.texi $(top_builddir)/user/region.texi \
    2626    $(top_builddir)/user/rtmon.texi $(top_builddir)/user/schedule.texi \
    27     $(top_builddir)/user/sem.texi $(top_builddir)/user/signal.texi \
     27    $(top_builddir)/user/sem.textexii $(top_builddir)/user/signal.texi \
    2828    $(top_builddir)/user/task.texi $(top_builddir)/user/timer.texi \
    2929    $(top_builddir)/user/userext.texi $(top_builddir)/user/stackchk.texi \
     
    3333FILES = example.texi
    3434
     35ObjectId-16Bits.eps: $(top_srcdir)/user/ObjectId-16Bits.eps
     36        $(LN_S) $<
    3537ObjectId-32Bits.eps: $(top_srcdir)/user/ObjectId-32Bits.eps
    3638        $(LN_S) $<
     
    4244    ObjectId-32Bits.png
    4345
     46ObjectId-16Bits.png: $(top_srcdir)/user/ObjectId-16Bits.png
     47        $(LN_S) $<
    4448ObjectId-32Bits.png: $(top_srcdir)/user/ObjectId-32Bits.png
    4549        $(LN_S) $<
     
    5559
    5660if USE_HTML
    57 html_project_DATA += rtemsarc.png rtemspie.png states.png ObjectId-32Bits.png
     61html_project_DATA += rtemsarc.png rtemspie.png states.png \
     62    ObjectId-16Bits.png ObjectId-32Bits.png
    5863endif
    5964
    60 $(PROJECT).dvi: rtemspie.eps states.eps ObjectId-32Bits.eps
     65$(PROJECT).dvi: rtemspie.eps states.eps ObjectId-16Bits.eps \
     66    ObjectId-32Bits.eps
    6167PDF_IMAGES = rtemspie.pdf states.pdf
    6268
  • doc/user/Makefile.am

    r2b90266 r2bf21fc8  
    2828TXT_FILES = rtemsarc.txt rtemspie.txt states.txt
    2929
    30 PNG_FILES = rtemsarc.png rtemspie.png states.png ObjectId-32Bits.png
     30PNG_FILES = rtemsarc.png rtemspie.png states.png ObjectId-32Bits.png \
     31    ObjectId-16Bits.png
    3132
    32 EPS_IMAGES = rtemspie.eps states.eps
     33EPS_IMAGES = rtemspie.eps states.eps ObjectId-32Bits.eps \
     34    ObjectId-32Bits.eps
    3335$(PROJECT).dvi: $(EPS_IMAGES)
    3436
    35 PDF_IMAGES = rtemspie.pdf states.pdf
     37PDF_IMAGES = rtemspie.pdf states.pdf ObjectId-16Bits.pdf \
     38    ObjectId-32Bits.pdf
    3639CLEANFILES += $(PDF_IMAGES)
    3740
  • doc/user/concepts.t

    r2b90266 r2bf21fc8  
    119119@need 3000
    120120
    121 An object ID is a unique unsigned thirty-two bit
    122 entity composed of three parts: API, object class, node, and index.
    123 The data type @code{@value{DIRPREFIX}id} is used to store object IDs.
     121An object ID is a unique unsigned integer value which uniquely identifies
     122an object instance.  Object IDs are passed as arguments to many directives
     123in RTEMS and RTEMS translates the ID to an internal object pointer. The
     124efficient manipulation of object IDs is critical to the performance
     125of RTEMS services.  Because of this, there are two object Id formats
     126defined.  Each target architecture specifies which format it will use.
     127There is a thirty-two bit format which is used for most of the supported
     128architectures and supports multiprocessor configurations.  There is also
     129a simpler sixteen bit format which is appropriate for smaller target
     130architectures and does not support multiprocessor configurations.
     131
     132@subsubsection Thirty-Two Object ID Format
     133
     134The thirty-two bit format for an object ID is composed of four parts: API,
     135object class, node, and index.  The data type @code{@value{DIRPREFIX}id}
     136is used to store object IDs.
    124137
    125138
     
    158171number of objects configured for this object type.
    159172
    160 The four components of an object ID make it possible
     173@subsubsection Sixteen Bit Object ID Format
     174
     175The sixteen bit format for an object ID is composed of three parts: API,
     176object class, and index.  The data type @code{@value{DIRPREFIX}id}
     177is used to store object IDs.
     178
     179
     180@ifset use-ascii
     181@example
     182@group
     183     15      11 10    8 7            0
     184     +---------+-------+--------------+
     185     |         |       |              |
     186     |  Class  |  API  |    Index     |
     187     |         |       |              |
     188     +---------+-------+--------------+
     189@end group
     190@end example
     191@end ifset
     192
     193@ifset use-tex
     194@sp1
     195@center{@image{ObjectId-16Bits,,2in}}
     196@end ifset
     197
     198@ifset use-html
     199@html
     200<P ALIGN="center"><IMG SRC="ObjectId-16Bits.png"
     201     WIDTH=550 HEIGHT=400 ALT="16 Bit Object Id"></P>
     202@end html
     203@end ifset
     204
     205The sixteen-bit format is designed to be as similar as possible to the
     206thrity-two bit format.  The differences are limited to the eliminatation
     207of the node field and reduction of the index field from sixteen-bits
     208to 8-bits.  Thus the sixteen bit format only supports up to 255 object
     209instances per API/Class combination and single processor systems.
     210As this format is typically utilized by sixteen-bit processors with
     211limited address space, this is more than enough object instances.
     212
     213@subsection Object ID Description
     214
     215The components of an object ID make it possible
    161216to quickly locate any object in even the most complicated
    162217multiprocessor system.  Object ID's are associated with an
Note: See TracChangeset for help on using the changeset viewer.