sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
34,109 Commits 1 Branch 0 Tags 291 MiB
28115504ec
Commit Graph

7 Commits

Author SHA1 Message Date
Alan Carvalho de Assis
7133f89cc2 tools/Makefile.unix, .win, and all defconfig files: Modify tools/Makefiles to add warning on defconfig files 2019-03-03 08:31:03 -06:00
Gregory Nutt
a76e137ce2 Squashed commit of the following: 
sched/init/nx_start.c:  Add support for CONFIG_BOARD_DRIVER_INITIALIZE.  If this option is selected then nx_start() will call a board-provided function board_driver_initialize() immediately after calling up_initialize().

    Rename CONFIG_BOARD_INITIALIZE to CONFIG_BOARD_LATE_INITIALIZE.

    Raname board_initialize() to board_late_initialize()
 2019-02-18 15:32:00 -06:00
Gregory Nutt
967dc523bb 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. 2019-02-12 19:13:22 -06:00
Gregory Nutt
920bb9dec8 Commit fd68d74264 breaks all STM32 board configurations that use STM32 USB host. That is because that commit requires CONFIG_STM_USBHOST to be set to build in USB host support, but did not update the necessary board defconfig files to add that required configuration. 2018-12-30 14:45:16 -06:00
Gregory Nutt
1802145604 Trivial fixes to spelling errors. 2018-09-20 06:53:13 -06:00
Gregory Nutt
a2428db499 configs/olimex-stm32_p407: Add logic to support initialization of the kernel module symbol table installed in the pass2/ directory during the application phase of the build. The kmodule configuration appears to be fully functional. 2018-08-07 10:50:25 -06:00
Gregory Nutt
9726352d7a configs/olimex-stm32-p407/kmodule: Add a configuration that can be used for testing installation of kernel modules in the protected build. This configuration is useless in its present state, not due to any problem with the OS itself, but rather with the current apps/ build system. The symbol table is built by apps/examples/module/drivers/Makefile in user space. The problem with that is that the kernel module does reference internal kernel symbols which are not available in the user space build context. A mechanism is needed in the build system to build the symbol table in the context of the kernel. There is currently no way to do that. 2018-08-05 15:42:11 -06:00