[riot-notifications] [RIOT-OS/RIOT] boot: Moved stdio_init() into periph_init() (#10806)
notifications at github.com
Tue Mar 26 20:45:51 CET 2019
I'd like to take a step back and focus on the core problem at hand: a clear definition of the point in time in the boot sequence, from which it is safe to use STDIO. We all agree, that this should as soon as possible, to allow for using STDIO early on during boot. If this is 'standardized', IMO there is no need for additional checking code if STDIO is available or not.
So what are the challenges:
- (a) different `stdio` implementations have diverging dependencies on `periph` and other libraries (`stdio_uart` uses `periph_uart`, while `stdio_rtt` uses `xtimer` and with this `periph_timer`). So this is not something we can easily generalize.
- (b) depending on the used platform, there are potential some prerequisites, that have to be done before stdio can be initialized
- (c) ?
(b) is easy to solve by moving the init code into the platform specific init before `periph_init()`.
For (a) it is not quite as trivial -> using `stdio_uart` one can use DEBUG in the timer driver, if using `stdio_rtt` one can clearly not. Calling it from `periph_init` does also not really solve this, right?!
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications