From 2858939a2ccb3cf1918dadd9cda1fd1d8ab5a9ef Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 9 Dec 2015 12:03:49 +0100 Subject: bsps: Delete superfluous bsp_pretasking_hook() Use the bsp_predriver_hook() instead. Update #2408. --- doc/bsp_howto/init.t | 22 ++++------------------ doc/bsp_howto/support.t | 3 --- 2 files changed, 4 insertions(+), 21 deletions(-) (limited to 'doc/bsp_howto') diff --git a/doc/bsp_howto/init.t b/doc/bsp_howto/init.t index d557df6254..1c0cd09113 100644 --- a/doc/bsp_howto/init.t +++ b/doc/bsp_howto/init.t @@ -171,9 +171,6 @@ enabled. the C Library. Usually the default implementation in @code{c/src/lib/libbsp/shared/bsplibc.c} should be sufficient. -@item It invokes the BSP specific routine @code{bsp_pretasking_hook}. On -most BSPs which utilize the framework, this routine does nothing. - @item It invokes the RTEMS directive @code{rtems_initialize_before_drivers()} to initialize the MPCI Server thread in a multiprocessor configuration and execute API specific @@ -244,22 +241,11 @@ After completing execution, this routine returns to the @code{boot_card()} routine. In case of errors, the initialization should be terminated via @code{bsp_fatal()}. -@subsection RTEMS Pretasking Callback - -The method @code{bsp_pretasking_hook()} is the BSP specific routine invoked -once RTEMS API initialization is complete but before interrupts and tasking are -enabled. The idle thread exists at this time. The pretasking hook is optional -and the user may use the shared version. - -The @code{bsp_pretasking_hook()} routine is the appropriate place to initialize -any BSP specific support components which depend on the RTEMS APIs. - -@subsection RTEMS Predriver Callback +@subsection bsp_predriver_hook() - BSP Specific Predriver Hook -The @code{bsp_predriver_hook()} method is the BSP specific routine that -is is invoked immediately before the the device drivers and MPCI are -initialized. RTEMS initialization is complete but interrupts and tasking -are disabled. +The @code{bsp_predriver_hook()} method is the BSP specific routine that is +invoked immediately before the the device drivers are initialized. RTEMS +initialization is complete but interrupts and tasking are disabled. The BSP may use the shared version of this routine which is empty. Most BSPs do not provide a specific implementation of this callback. diff --git a/doc/bsp_howto/support.t b/doc/bsp_howto/support.t index 4441636d9f..47ec92b2be 100644 --- a/doc/bsp_howto/support.t +++ b/doc/bsp_howto/support.t @@ -171,9 +171,6 @@ void * sbrk(size_t increment) The @code{increment} amount is based upon the @code{sbrk_amount} parameter passed to the @code{bsp_libc_init} during system initialization. -Historically initialization of the C Library was done as part of the -BSP's Pretasking Hook but now the BSP Boot Card Framework can perform -this operation. @findex CONFIGURE_MALLOC_BSP_SUPPORTS_SBRK If your BSP does not want to support dynamic heap extension, then you do not have to do anything special. However, if you want to support @code{sbrk}, you must provide an implementation of this method and define @code{CONFIGURE_MALLOC_BSP_SUPPORTS_SBRK} in @code{bsp.h}. This informs @code{rtems/confdefs.h} to configure the Malloc Family Extensions which support @code{sbrk}. -- cgit v1.2.3