sched/: Remove the option CONFIG_BOARD_INITTHREAD. Now, if CONFIG_BOARD_INITIALIZE is selected, then the board_initialize() logic will ALWAYS run on an internal kernel thread. This will prevent the problems people have had doing inappropriate board_initialization on the IDLE thread.

This commit is contained in:
Gregory Nutt
2019-02-12 19:13:22 -06:00
parent a2406c1ac8
commit 967dc523bb
9 changed files with 6 additions and 80 deletions
+1 -10
View File
@@ -336,15 +336,13 @@ static inline void nx_start_application(void)
*
****************************************************************************/
#ifdef CONFIG_BOARD_INITTHREAD
static int nx_start_task(int argc, FAR char **argv)
static inline int nx_start_task(int argc, FAR char **argv)
{
/* Do the board/application initialization and exit */
nx_start_application();
return OK;
}
#endif
/****************************************************************************
* Name: nx_create_initthread
@@ -365,7 +363,6 @@ static int nx_start_task(int argc, FAR char **argv)
static inline void nx_create_initthread(void)
{
#ifdef CONFIG_BOARD_INITTHREAD
int pid;
/* Do the board/application initialization on a separate thread of
@@ -377,12 +374,6 @@ static inline void nx_create_initthread(void)
(main_t)nx_start_task, (FAR char * const *)NULL);
DEBUGASSERT(pid > 0);
UNUSED(pid);
#else
/* Do the board/application initialization on this thread of execution. */
nx_start_application();
#endif
}
/****************************************************************************