[riot-notifications] [RIOT-OS/RIOT] boot: Moved stdio_init() into periph_init() (#10806)

Marian Buschsieweke notifications at github.com
Tue Mar 26 12:48:57 CET 2019


maribu commented on this pull request.



>  void periph_init(void)
 {
+    /* initialize stdio first to allow DEBUG() during later stages */
+#ifdef CPU_NATIVE

Maybe it is best to split off the mips32 changes, as any PR trying to reduce the hardware specific differences will depend on that. Maybe @francois-berder could open an PR for that, as he authored those commits anyway?

And maybe it would be a good idea to add get a general picture how the boot up process in an *ideal* RIOT board look like. Maybe a sequence diagram like [this one](https://api.riot-os.org/riot-netdev-rx.svg) in the [doc of the Network Device Driver API](https://api.riot-os.org/group__drivers__netdev__api.html) could help. In that diagram the hardware specific part could be color coded, as those will likely still differ in various ways due to specific hardware dependent requirements.

Here is the sequence diagram I linked above (sadly with broken style):

![seq_diagram](https://api.riot-os.org/riot-netdev-rx.svg)

Such a diagram might help to a lot to at least have new added boards/architectures behave in a similar way and might be a good starting point to refactor and work out the differences of the existing boards.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10806#discussion_r269062950
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190326/2c2d1038/attachment.html>


More information about the notifications mailing list