Hello,
First, thanks to your quick reply, Hauke and Kaspar.
I indeed understood that these changes were made to enhance reliability
and code quality.
* For the tickless part, I am now totally reassured : a wake-up every
overflow is no big deal (at least for me in the current situation). RIOT
Hello everyone , I hope you guys can help me out ... I'm gonna try to port
riot to the smaller variations of atmel processors ( I'm thinking atmega16
) .. I'm more of a software guy , I haven't worked with embedded stuff a
lot .. hope you guys help me out ..
Thanks
On 09-Dec-2015 6:21 pm, "Kaspar
Hey,
On 12/09/15 12:57, ROUSSEL Kévin wrote:
> 1] Is RIOT OS kernel still *tickless*?
> Does it mean that there will be an interrupt every microsecond when
> 'xtimer' is used, or will we still have only an interrupt when a
> time-related event actually happens (which means RIOT still qualifies a
Hi Kevin,
let me try to answer your questions (see inline).
On 09.12.2015 12:57, ROUSSEL Kévin wrote:
Hello everyone,
As (I suppose) everybody here knows, the 'hwtimer' kernel feature has
been replaced by the 'xtimer' module.
Consequently, I'm wondering about some features that were specifi
Hello everyone,
As (I suppose) everybody here knows, the 'hwtimer' kernel feature has
been replaced by the 'xtimer' module.
Consequently, I'm wondering about some features that were specific to
RIOT OS, and how they have evolved. More precisely, I have questions to ask:
1] Is RIOT OS kernel
