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

danpetry notifications at github.com
Thu Jan 31 16:47:20 CET 2019


danpetry 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

If the size of the kernel is now relatively stable and at a size we're happy with, it could be helpful to state the size along with a statement that it shouldn't grow more than this size in its default configuration. We could also be more specific about the kinds of applications that can be run on devices with 2KiB RAM and 10 KiB ROM? Some of the aspects mentioned:
- no networking support
- support for sensors and actuators with straightforward (not much control logic in the driver, for example) functionality
- space for simple control and sensing application logic
If anyone can think of any more detail or refine these statements further, that would be useful

-- 
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_r252721483
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190131/c68e9949/attachment.html>


More information about the notifications mailing list