acassis commented on issue #11321: URL: https://github.com/apache/nuttx/issues/11321#issuecomment-3926778310
> > [@linguini1](https://github.com/linguini1) is the boot process is a mess, there are originally the xxx_boot.c and later xxx_bringup.c. Later xxx_appinit.c and finally there is only one xxx_init.c: avr/avrdx/breadxavr/src/avrdx_init.c > > I think we need some consensus before changing it! For visibility: [@raiden00pl](https://github.com/raiden00pl) [@simbit18](https://github.com/simbit18) [@hartmannathan](https://github.com/hartmannathan) [@xiaoxiang781216](https://github.com/xiaoxiang781216) [@lupyuen](https://github.com/lupyuen) [@jerpelea](https://github.com/jerpelea) [@cederom](https://github.com/cederom) (sorry if I missed another people interested on it) > > Hi all, > > 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!!! @hartmannathan I agree that we need to worry about how people are keeping theirs out of tree boards, but instead of creating hooks, it is better to Document how to change to use board_late_initialize or the other alternatives. If I'm not wrong, there is already a "hook" for board early initialize. If we keep many hooks in the kernel, the chaos will continue. The board initialization on NuttX is already very complex, we need to simplify keeping the most common use cases. -- 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]
