[riot-notifications] [RIOT-OS/RIOT] API change, uart input not working anymore on previously working setups (#11525)

Alexandre Abadie notifications at github.com
Tue May 14 17:54:29 CEST 2019

Regarding the actual state of low-power management on STM32, it works well and is easy to use as it is know with `uart_stdio_rx` being disabled by default and when not using the shell in an application: for an autonomous application (like a trendy LoRaWAN application), calling unblock from the application code or simply setting PM_BLOCKER_INITIAL macro from the Makefile does the job pretty well. I have good examples for this.

Enabling `uart_stdio_rx` by default would break that and from the users perspective this is not good IMHO as it will require them to explicitly disable something not directly related to make low power work out of the box.

If you need to read some characters from stdin (over UART or whatever) but don't need the shell, then you could just pull `uart_stdio_rx` explicitly.

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...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190514/b567c8c5/attachment-0001.html>

More information about the notifications mailing list