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

Hauke Petersen notifications at github.com
Tue Mar 26 15:34:57 CET 2019


I agree with @kaspar030, that just because `stdio` is using a periph driver, it is not a periph module on its own.

But one important point: the `periph_common/init` is there for initializing peripherals, that can be statically configured without taking any 'using module's' needs into account (e.g. i2c, spi, ...). 'timer' and 'uart' are a little different, as they are under full control if their users (e.g. xtimer, stdio, ...), and so these periph drivers are initialized by those modules directly, and are therefore independent from the `periph_common` module.

So again, we all agree, that `stdio` needs some extra care when it comes to initialization order. So I don't see a reason not to include its initialization in the platform specific code, especially considering the potential stdlib differences.

Side note (revisiting the discussion above): the `segger_rtt` mapping was not broken, it was my local python that prevented it from working. So now I can test those platforms in question again (at least when back in the office).

-- 
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#issuecomment-476674324
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190326/6ceea41f/attachment.html>


More information about the notifications mailing list