Hi,
I was just literally about to send an email with pretty much the same arguments
Kaspar wrote right now. So I skip them and throw in a +1 instead.
> Below that, context switching takes the bulk of the time, so spinning (not
> using a callback) is probably preferable.
I think that the ws281x
Hey,
On 12/9/19 10:32 PM, Oleg Hahm wrote:
> Hm, to be honest, I'm not so sure of what kind of efficiency we're speaking
> here. CPU time or memory? Probably both, right? Regarding the CPU efficiency,
> I would assume that this also dictates the maximum precision, right?
I don't think so. The
Hey!
On Mon, Dec 09, 2019 at 10:07:16PM +0100, Kaspar Schleiser wrote:
> > Anyway, I think we need to define what "very efficient timers for use in
> > time-critical drivers" means in order to being able to check whether the
> > proposal fulfills the requirement or not.
>
> We can try. What
Hi Oleg et all,
On 12/9/19 9:25 PM, Oleg Hahm wrote:
> I think the problem statement and the requirements could indeed be more
> precise - while I must admit that a lack of precise requirements is a failure
> of the RIOT community.
Yes, that could be. I intentionally did not add requirements. I
Folks!
Can we get back to the actual problem at hand, please?
Let me recap:
Kaspar came up with a proposal for a new timer API, since xtimer has flaws (as
identified by multiple members of the RIOT community during the last ~4 years)
and is apparently not fixable (at least no one came up with a
Hi Marian,
On 09/12/2019 21:00, Marian Buschsieweke wrote:
I'd like to point out that the research community has largely dismissed Karl
Poppers contribution to the demarcation problem, as largely accepted fields of
research are not falsifiable. E.g. the evolution theory cannot be falsified.
Dear Thomas,
I'd like to point out that the research community has largely dismissed Karl
Poppers contribution to the demarcation problem, as largely accepted fields of
research are not falsifiable. E.g. the evolution theory cannot be falsified.
Maybe it is time for you to move on as well?
Kind
Hi Marian,
On 09/12/2019 20:06, Marian Buschsieweke wrote:
Also, a clear and falsifiable problem statement should be given.
could you elaborate on what you mean by a problem statement being falsifiable?
"falsifiable" is a standard principle in science: It is sometimes
difficult to verify
Hi Thomas,
> Also, a clear and falsifiable problem statement should be given.
could you elaborate on what you mean by a problem statement being falsifiable?
Do you want to be able to check that a given problem cannot be solved by
existing features?
> This should IMO address the question, why
Hi,
if this is a "problem statement and design document", then concise and
measurable requirements on power management should go into the
corresponding section.
Also, a clear and falsifiable problem statement should be given. This
should IMO address the question, why timer problems cannot
Hi,
On 12/9/19 4:52 PM, Kaspar Schleiser wrote:
> Hi Robert,
>
> On 12/9/19 4:25 PM, Robert Hartung wrote:
>> Do we need to put any thoughts in power management / low_power /
>> integration with pm_layered? Or are the possible issues addreses /
>> already talked about?
>
> Yes and yes. ;)
>
>
Hi,
On 12/9/19 5:02 PM, José Ignacio Alamos wrote:
> No, I wouldn't consider those lost interrupts (because messages are
> lost, not IRQs).
Ok, thanks for clarifying!
Kaspar
___
devel mailing list
devel@riot-os.org
Hi Robert,
On 12/9/19 4:25 PM, Robert Hartung wrote:
> Do we need to put any thoughts in power management / low_power /
> integration with pm_layered? Or are the possible issues addreses /
> already talked about?
Yes and yes. ;)
I'll my thoughts so far.
Thanks!
Kaspar
Hi Robert,
On 12/9/19 4:19 PM, Robert Hartung wrote:
> why are 8-bit timers not listed? Intentional or unintentional?
Unintentional!
Kaspar
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Hey Jose,
On 12/9/19 3:46 PM, José Ignacio Alamos wrote:
> The main question here is, how should we handle lost interrupts in
> general? Let's say:
What do you mean by "lost interrupt"?
GNRC uses messages to pass an ISR from the interrupt handler to
"userspace". Those can be lost. Are you
Hey again ;)
Do we need to put any thoughts in power management / low_power /
integration with pm_layered? Or are the possible issues addreses /
already talked about?
Regards
Robert
On 09.12.19 14:49, Kaspar Schleiser wrote:
> Hey everyone,
>
> since the RIOT Summit in Helsinki, I've put quite
Hi Kaspar,
why are 8-bit timers not listed? Intentional or unintentional?
Regards,
Robert
On 09.12.19 14:49, Kaspar Schleiser wrote:
> Hey everyone,
>
> since the RIOT Summit in Helsinki, I've put quite some work into ztimer,
> a possible successor to xtimer.
>
> If you're interested, please
Hey everyone,
since the RIOT Summit in Helsinki, I've put quite some work into ztimer,
a possible successor to xtimer.
If you're interested, please see an updated design document here: [1]
Cheers,
Kaspar
[1]
https://github.com/RIOT-OS/RIOT/wiki/ztimer-problem-statement-and-design-document
18 matches
Mail list logo
