[riot-notifications] [RIOT-OS/RIOT] doc/rdm: RFC - design goals (#10162)

Thomas C. Schmidt notifications at github.com
Wed Jan 30 20:51:12 CET 2019

tcschmidt commented on this pull request.

> +
+Modules outside the core should leverage the benefits and address the
+programming challenges of such a scheduler. They shouldn't demand that users do
+the same.  They should, however, allow users to manage power through different
+modes and functions.
+#### Small memory footprint
+Most of RIOT's targeted use cases are well addressed by devices in class 1 of
+the taxonomy presented in [1]. If small price differences are important or the
+energy budget is particularly tight, the available memory might be near the
+bottom of this class. Over-the-air updating currently reduces the available ROM
+by over half.
+RIOT should provide out-of-the-box support for devices with ~10 KiB of
+available RAM and ~100 KiB of ROM. It should be just as possible to address

There is no aversion against small memory footprint or the like - if RIOT achieves highest efficiency that's great. Still I'm hesitant with raising the wrong expectations - and manually optimized specialized modules sound like bare-metal firmware to me. 
Maybe a good solution here is to state that the RIOT kernel consumes 1.5kB RAM and - depending on the application and the modules loaded - the overall size of the system can be below 10kB.   

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/20190130/6093e10e/attachment.html>

More information about the notifications mailing list