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

danpetry notifications at github.com
Tue Jan 29 18:24:30 CET 2019


danpetry commented on this pull request.



> +RIOT nodes sometimes need to last for several years without external power, so
+they need to manage energy carefully. RIOT's tickless scheduler lets devices
+sleep while they aren't collecting data.
+
+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.

I think this is important to consider in the context of this section, which should serve as a rough guideline for our memory footprint. I've rephrased it as "Over-the-air updating facilities may also reduce the available RIOT by over half, depending on the architecture". Is this more suitable?

-- 
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/10162#discussion_r251935104
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190129/f1178b13/attachment-0001.html>


More information about the notifications mailing list