Thanks Mr Nutt.
Em qua., 7 de abr. de 2021 às 19:31, Gregory Nutt
escreveu:
> PR #3476 removes the unused variable from all other architectures.
>
> On 4/7/2021 3:59 PM, Sara da Cunha Monteiro de Souza wrote:
> > Yes, I agree.
> >
> > Because I took a look at some codes that
> > are using the f
PR #3476 removes the unused variable from all other architectures.
On 4/7/2021 3:59 PM, Sara da Cunha Monteiro de Souza wrote:
Yes, I agree.
Because I took a look at some codes that
are using the freerun driver (tickless, dhtxx and hcsr)
and no one use this var.
I think I will "deviate", save
Yes, I agree.
Because I took a look at some codes that
are using the freerun driver (tickless, dhtxx and hcsr)
and no one use this var.
I think I will "deviate", save some bytes and not create it.
Em qua., 7 de abr. de 2021 às 18:53, Alan Carvalho de Assis <
acas...@gmail.com> escreveu:
> Hi Sa
Hi Sara,
Good question, I think the "running" variable is not used. Probably it
is a new living being that evolved from the oneshot timer driver where
the "running" makes sense to exist. :-D
BR,
Alan
On 4/7/21, Sara da Cunha Monteiro de Souza
wrote:
> Hi all,
>
> I've been implementing the fre
Hi all,
I've been implementing the freerun wrapper and I took a look at
the multiple implementations in other chips and I realized that
they initialize the running variable as false in their respective
_freerun_initialize() function.
I can't understand. It should be true, shouldn't it? Because
Hi Erick,
Right, we can do a meeting (I, You and Brennan) to discuss about it.
Brennan, did you have the chance to read Erick's proposal document?
Is there something you want to add/modify?
BR,
Alan
On 4/6/21, Erick Rodrigues wrote:
> That's great news, Brennan!
>
> Would you mind reading th
