On 04/10/2019 00:08, Joel Sherrill wrote:
This adds back the capability for the BSP to configure an initial extension that is specific to itself. The parameter BSP_INITIAL_EXTENSION was taken over by having a standard fatal extension installed using the same name. --- cpukit/include/rtems/confdefs.h | 3 +++ 1 file changed, 3 insertions(+)diff --git a/cpukit/include/rtems/confdefs.h b/cpukit/include/rtems/confdefs.h index 5eb5425..e1a255a 100644 --- a/cpukit/include/rtems/confdefs.h +++ b/cpukit/include/rtems/confdefs.h @@ -2136,6 +2136,9 @@ extern rtems_initialization_tasks_table Initialization_tasks[]; #if defined(CONFIGURE_INITIAL_EXTENSIONS) CONFIGURE_INITIAL_EXTENSIONS, #endif + #if defined(BSP_INITIAL2_EXTENSIONS) + BSP_INITIAL2_EXTENSIONS, + #endif #if defined(BSP_INITIAL_EXTENSION) BSP_INITIAL_EXTENSION #endif
I don't think this patch is necessary. A BSP is free to provide its own initial extension. Just don't add the
#include <bsp/default-initial-extension.h> to the bsp.h. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
