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

Martine Lenders notifications at github.com
Tue Feb 26 18:24:34 CET 2019


miri64 requested changes on this pull request.



> +modular as possible so unused features don't use up precious RAM or flash.
+Almost all features are provided as optional modules that have to be enabled
+explicitly at compile time.  A minimal RIOT configuration starts at around
+<2KiB flash and <1.5KiB RAM (including stack space for one thread and ISRs).
+
+Starting from there, the memory usage depends on the enabled features:
+
+- Non-networked control loop / sensing applications can fit on very small MCUs
+(eg., an Atmega328P with 2KiB RAM)
+- 6lowPAN networking currently starts at ~40KiB ROM and ~10KiB RAM
+- A 6lowpan enabled CoAP server requires ~60KiB ROM and ~15KiB RAM
+- a file system adds ~15 KiB ROM and ~2 KiB RAM
+
+#### Constrained networking
+
+RIOT should deliver best-in-class communication robustness and

I'm not sure about this economist-linguo "best-in-class". At least I had to look it up (though the meaning turned out to be pretty self-explanatory I wanted to make sure there is no technical meaning to it). Why use this superlative at all (we had criticism of over-claiming in the past already ;-))?

```suggestion
RIOT should deliver communication robustness and
```

> +  - Sense temperature, light, humidity, pressure, current, etc.
+  - Control temperature, light, ventilation, etc.
+  - Connect to the building management system, via wired or wireless connectors.
+  - Deliver data with controllable timing and accuracy.
+
+## 2.6. Smart home devices
+
+Easy to use devices can let consumers monitor and control their home
+automatically. The devices need to be able to:
+
+  - Sense temperature, light, humidity, smoke, etc.
+  - Integrate with home appliances to control temperature, light, power usage,
+    etc.
+  - Be usable but secure for people with no technical knowledge.
+  - Connect to a commercial home gateway.
+  - Communicate over common home IoT protocols such as ZigBee, Bluetooth, Wi-Fi,

With this sentence from section 3 in mind

> RIOT should support standards once they have reached a certain level of
maturity and popularity.

I guess it is about high time we write a ZigBee stack then ;-). Question is are we able / allowed to do that (I remember there was some paywall thingy)?

> +  - Sense temperature, light, humidity, pressure, current, etc.
+  - Control temperature, light, ventilation, etc.
+  - Connect to the building management system, via wired or wireless connectors.
+  - Deliver data with controllable timing and accuracy.
+
+## 2.6. Smart home devices
+
+Easy to use devices can let consumers monitor and control their home
+automatically. The devices need to be able to:
+
+  - Sense temperature, light, humidity, smoke, etc.
+  - Integrate with home appliances to control temperature, light, power usage,
+    etc.
+  - Be usable but secure for people with no technical knowledge.
+  - Connect to a commercial home gateway.
+  - Communicate over common home IoT protocols such as ZigBee, Bluetooth, Wi-Fi,

I actually was asked about this at 35C3 by @Drakulix. His use-case is to have a non-intrusive but open integration with his TRÅDFRI home automation setup.

-- 
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#pullrequestreview-208052166
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190226/614ee975/attachment.html>


More information about the notifications mailing list