linguini1 commented on issue #11321: URL: https://github.com/apache/nuttx/issues/11321#issuecomment-3924757688
> I'm in favor of improving the boot process. Just please remember that 3rd party developers may have private, out-of-tree boards that utilize some of these functions in their initialization. (My boards use board_late_initialize, but others may have done differently.) So whatever approach we take to simplify and clean up the boot process, we need to make sure that developers can have the hooks they need to initialize their stuff properly. And we need to make sure that any changes people will need to make, will be properly documented in the release notes!!! I agree. Right now the idea is to gut the BOARDIOC_INIT and NSH_ARCHINIT stuff. All users should then be able to choose between two options: 1. Just enable CONFIG_BOARD_LATE_INITIALIZE and let the NuttX kernel handle the initialization (the elegant solution) 2. For cases like raiden pointed out where app developers _really_ need userspace control over initialization, disable CONFIG_BOARD_LATE_INITIALIZE and implement a custom `board_finalinitialization` to call from userspace via `boardctl(BOARDIOC_FINALINIT)`. As @cederom suggested (I think somewhere on the mailing list) I also plan to include a "quick fix" message in both the PR descriptions and commit messages that indicate to the end user what they need to change in their defconfig/custom board logic/custom app to fix any breakages. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
