diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2014-04-07 14:50:37 +0200 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2014-04-10 12:37:40 +0200 |
commit | 263f4beceae0ec5602cb41e792c25ebe3ec49c97 (patch) | |
tree | 7941a5035b4834597e9cdb855e92b4a9d8b5ac27 /doc/user | |
parent | documentation: Clarify (diff) | |
download | rtems-263f4beceae0ec5602cb41e792c25ebe3ec49c97.tar.bz2 |
score: Statically initialize IO manager
This simplifies the RTEMS initialization and helps to avoid a memory
overhead. The workspace demands of the IO manager were not included in
the <rtems/confdefs.h> workspace size estimate. This is also fixed as a
side-effect.
Update documentation and move "Specifying Application Defined Device
Driver Table" to the section end. This sub-section is not that
important for the user. Mentioning this at the beginning may lead to
confusion.
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/conf.t | 68 |
1 files changed, 35 insertions, 33 deletions
diff --git a/doc/user/conf.t b/doc/user/conf.t index 68b62463b4..c0bb35ac43 100644 --- a/doc/user/conf.t +++ b/doc/user/conf.t @@ -3836,39 +3836,6 @@ custom device drivers. Note that network device drivers are not configured in the Device Driver Table. @c -@c === CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE === -@c -@subsection Specifying Application Defined Device Driver Table - -@findex CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE - -@table @b -@item CONSTANT: -@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE} - -@item DATA TYPE: -List of device driver initializers (@code{rtems_driver_address_table}). - -@item RANGE: -Undefined or array of device drivers. - -@item DEFAULT VALUE: -This is not defined by default, indicating the @code{<rtems/confdefs.h>} -is providing the device driver table. - -@end table - -@subheading DESCRIPTION: -@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE} is defined if the application -wishes to provide their own Device Driver Table. - -The table must be an array of @code{rtems_driver_address_table} entries -named @code{Device_drivers}. - -@subheading NOTES: -It is expected that there the application would only rarely need to do this. - -@c @c === CONFIGURE_MAXIMUM_DRIVERS === @c @subsection Specifying the Maximum Number of Device Drivers @@ -4297,6 +4264,41 @@ device driver. This device driver is supported by all BSPs. @c +@c === CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE === +@c +@subsection Specifying Application Defined Device Driver Table + +@findex CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE + +@table @b +@item CONSTANT: +@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE} + +@item DATA TYPE: +Boolean feature macro. + +@item RANGE: +Defined or undefined. + +@item DEFAULT VALUE: +This is not defined by default, indicating the @code{<rtems/confdefs.h>} +is providing the device driver table. + +@end table + +@subheading DESCRIPTION: +@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE} is defined if the application +wishes to provide their own Device Driver Table. + +The table must be an array of @code{rtems_driver_address_table} entries named +@code{_IO_Driver_address_table}. The application must also provide a const +variable @code{_IO_Number_of_drivers} of type @code{size_t} indicating the +number of entries in the @code{_IO_Driver_address_table}. + +@subheading NOTES: +It is expected that there the application would only rarely need to do this. + +@c @c === Multiprocessing Configuration === @c @section Multiprocessing Configuration |