Changeset 263f4bec in rtems for doc


Ignore:
Timestamp:
04/07/14 12:50:37 (10 years ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
4.11, 5, master
Children:
4bc8d2e
Parents:
3a4d28a
git-author:
Sebastian Huber <sebastian.huber@…> (04/07/14 12:50:37)
git-committer:
Sebastian Huber <sebastian.huber@…> (04/10/14 10:37:40)
Message:

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.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/user/conf.t

    r3a4d28a r263f4bec  
    38373837
    38383838@c
    3839 @c === CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE ===
    3840 @c
    3841 @subsection Specifying Application Defined Device Driver Table
    3842 
    3843 @findex CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE
    3844 
    3845 @table @b
    3846 @item CONSTANT:
    3847 @code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE}
    3848 
    3849 @item DATA TYPE:
    3850 List of device driver initializers (@code{rtems_driver_address_table}).
    3851 
    3852 @item RANGE:
    3853 Undefined or array of device drivers.
    3854 
    3855 @item DEFAULT VALUE:
    3856 This is not defined by default, indicating the @code{<rtems/confdefs.h>}
    3857 is providing the device driver table.
    3858 
    3859 @end table
    3860 
    3861 @subheading DESCRIPTION:
    3862 @code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE} is defined if the application
    3863 wishes to provide their own Device Driver Table.
    3864 
    3865 The table must be an array of @code{rtems_driver_address_table} entries
    3866 named @code{Device_drivers}.
    3867 
    3868 @subheading NOTES:
    3869 It is expected that there the application would only rarely need to do this.
    3870 
    3871 @c
    38723839@c === CONFIGURE_MAXIMUM_DRIVERS ===
    38733840@c
     
    42984265
    42994266@c
     4267@c === CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE ===
     4268@c
     4269@subsection Specifying Application Defined Device Driver Table
     4270
     4271@findex CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE
     4272
     4273@table @b
     4274@item CONSTANT:
     4275@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE}
     4276
     4277@item DATA TYPE:
     4278Boolean feature macro.
     4279
     4280@item RANGE:
     4281Defined or undefined.
     4282
     4283@item DEFAULT VALUE:
     4284This is not defined by default, indicating the @code{<rtems/confdefs.h>}
     4285is providing the device driver table.
     4286
     4287@end table
     4288
     4289@subheading DESCRIPTION:
     4290@code{CONFIGURE_HAS_OWN_DEVICE_DRIVER_TABLE} is defined if the application
     4291wishes to provide their own Device Driver Table.
     4292
     4293The table must be an array of @code{rtems_driver_address_table} entries named
     4294@code{_IO_Driver_address_table}.  The application must also provide a const
     4295variable @code{_IO_Number_of_drivers} of type @code{size_t} indicating the
     4296number of entries in the @code{_IO_Driver_address_table}.
     4297
     4298@subheading NOTES:
     4299It is expected that there the application would only rarely need to do this.
     4300
     4301@c
    43004302@c === Multiprocessing Configuration ===
    43014303@c
Note: See TracChangeset for help on using the changeset viewer.