[riot-devel] pm_reboot

and we would have to duplicate existing code (bad idea!). Best, Robert -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für Betriebssysteme und Rechnerverbund Mühlenpfordtstr. 23, Raum 115 38106 Braunschweig Fon: +49 (531) 391 - 3264 Fax: +49 (531) 391 - 5936 E-Mail: hart

Re: [riot-devel] pm_reboot

in a single module to make it easier to develop PM for other cpus. - Robert On 08.09.2017 10:20, Robert Hartung wrote: > Hi *, > > I am working on the pm (power management) module of RIOT. Can anyone > tell me why pm_reboot is (often) part of this module? > > If no one votes again

Re: [riot-devel] pm_reboot

pm_reboot() from pm_fallback implementation and create additional modules if needed (at some points pm_reboot is defined outside of pm anyway). - Robert On 08.09.2017 11:03, Robert Hartung wrote: > After a short discussion offline we decided to keep it as it is. As the > nucleo board for e

Re: [riot-devel] pm_reboot

/pm_fallback.c [2] https://github.com/roberthartung/RIOT/blob/hartung/power-management/cpu/cortexm_common/pm/pm.c [3] https://github.com/roberthartung/RIOT/blob/hartung/power-management/cpu/stm32_common/pm/pm.c On 13.09.2017 15:09, Kaspar Schleiser wrote: > Hi, > > On 09/13/2017 03:06 PM, Rober

Re: [riot-devel] pm_reboot

to get rid of all #ifdef stuff which is really ugly! Would that be fine? When do you plan to be finished with the submodules? I would really like to finish the pm architecture and finally use it! - Robert On 11.09.2017 09:01, Kaspar Schleiser wrote: > Hi, > > On 09/08/2017 11:28 AM, Rober

Re: [riot-devel] pm_reboot

asn't able to setup a working version. Your PR does not compile for me, almost 50% of the boards in examples/default/ are not compiling anymore. At least the first few I checked are missing pm_reboot (undefined reference). - Robert -- Robert Hartung, M.Sc. Technische Universität Braunschweig I

[riot-devel] Discussion of Power Management

+= periph_pm_set_lowest I thought that maybe features can be used to describe which functions are provided. Later on based on include/compile order, missing functions can be added if needed. Any opinions on this? Best Regards, Robert -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für

Re: [riot-devel] Discussion of Power Management

lback modules across CPUs and RIOT in general and I will take care of this. - Robert -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für Betriebssysteme und Rechnerverbund Mühlenpfordtstr. 23, Raum 115 38106 Braunschweig Fon: +49 (531) 391 - 3264 Fax: +

Re: [riot-devel] Discussion of Power Management

Hi Kaspar, On 31.08.2017 17:02, Kaspar Schleiser wrote: > Hi Robert, > > On 08/31/2017 04:37 PM, Robert Hartung wrote: >>> - if not, possibly e.g., kinetis_common has pm_set(), then that should >>> depend on pm_layered >> >> This means that

Re: [riot-devel] Discussion of Power Management

> Maybe the periph_common directory doesn't get selected. But we can't > make periph_common_pm_fallback depend on periph_common, that might have > side effects. > > How about drivers/pm_fallback/... for now? Then I'd vote for moving pm_layered to drivers as well? Or should be make it sys/

Re: [riot-devel] GNRC with sleepy nodes

Xtimer is not guaranteed to be based on timers that keep running in low power modes. Therefore sleeping is not supported on most devices. Am 20.11.2017 um 21:05 schrieb Francisco Molina: > >Hi, > > > >since the timers you mentioned are dependent on xtimer and since xtimer has > >some known

Re: [riot-devel] GNRC with sleepy nodes

wer 32khz > oscillator on SAMR21, it just needs a little reconfiguration. We have > duty cycling nodes working ok with gnrc. > > On Nov 21, 2017 8:26 AM, "Robert Hartung" <hart...@ibr.cs.tu-bs.de > <mailto:hart...@ibr.cs.tu-bs.de>> wrote: > > That's t

Re: [riot-devel] GNRC with sleepy nodes

> > I saw those issues but they only refer to the fact that xtimer doesn't > run during sleep modes, is that the only issue? Cheers > > Francisco > > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-o

Re: [riot-devel] SAMD21 Configuration ( was Monthly meetings for organisation purposes)

ot-os.org/mailman/listinfo/devel > <https://lists.riot-os.org/mailman/listinfo/devel> > > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Garanti sans virus. www.avast.com > <https://www.avast.com/sig-email?

Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes

>>> >>>>>>> Jup, provide a working mic for the FU's PlaceCam laptop >>>>>>> this time (: >>>>>> >>>>>> We had... the problem was that the machine we ran placecam on >>>>>> was so slow and old that ALSA wasn't able to stream that >>>>>&g

Re: [riot-devel] What definitions/configuration belong into to what file

nlernen willst, dann lauf Marathon. (Emil Zatopek) >> >> >> > Cheers, > Sebastian > > [mail]: s...@mlng.net > [code]: https://github.com/smlng > > > ___ > devel mailing list > devel@riot-os.org > https

Re: [riot-devel] General configuration Task Force

rested to work in this topic? > > > Cheers, > > José > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für Betriebssysteme und Rechnerverbund Mühlenpfo

Re: [riot-devel] RIOT policy on hardware support without example board

Hi Matthew, I already ported the atmega1284p to RIOT: https://github.com/RIOT-OS/RIOT/pull/7604 Best Regards, Robert > Am 14.03.2018 um 18:49 schrieb Matthew Blue : > > Hello all, > > I am building mesh networking

[riot-devel] Integration of the ATmega4809

to create a new base cpu it. Is there anyone interested in collaborating on the integration? Best Regards Robert -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für Betriebssysteme und Rechnerverbund Mühlenpfordtstr. 23, Raum 115 38106 Braunschweig Fon: +49 (531) 391 - 3264

Re: [riot-devel] just got my Vega

ery looking forward to see > messages floating between the cores! ;) > > Who's interested in collaborating on bringing RIOT onto the thing? > > Kaspar > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.o

Re: [riot-devel] How to properly use cortexm_sleep

>> https://lists.riot-os.org/mailman/listinfo/devel >> >>   >> >> _______ >> devel mailing list >> devel@riot-os.org <mailto:devel@riot-os.org> >> https://lists.riot-os.org/mailman/listinfo/devel >> &g

Re: [riot-devel] tests compiler policy

t; Gero >>> >> >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel > > > ___ > de

Re: [riot-devel] ztimer - a new high-level timer for RIOT

https://lists.riot-os.org/mailman/listinfo/devel > -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für Betriebssysteme und Rechnerverbund Mühlenpfordtstr. 23, Raum 115 38106 Braunschweig Fon: +49 (531) 391 - 3246 Fax: +49 (531) 391 - 5936 E-Mail: hart...@ibr.cs.tu-b

Re: [riot-devel] ztimer - a new high-level timer for RIOT

roblem-statement-and-design-document > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > -- Robert Hartung, M.Sc. Technische Universität Braunschweig Institut für Betriebssysteme und Rechnerverbund Mühlenpfordtstr. 23, Raum 115 38106 Braunsc

Re: [riot-devel] Release [2020.01] - dates and feature requests

riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > -- Robert Hartung, M.Sc. Technische Universität Braunschwei

[riot-devel] Driver for the at86rf215

. The Idea would then be to have a meta device for the interrupt handling and then calling the actual isr for the radio that the interrupt was ment for. Any one having a similar problem or any ideas how to solve this issue? Best Regards Robert -- Robert Hartung, M.Sc. Technische Universität

Re: [riot-devel] Driver for the at86rf215

andling each radio. > > Maybe you can sync there and contribute with feedback and testing. > > Best, > José > > [1]: https://github.com/RIOT-OS/RIOT/pull/12128 > On Thu, 2019-10-24 at 16:20 +0200, Robert Hartung wrote: >> Hello fellow developers, >> >> I am t

Re: [riot-devel] 802.15.4 Radio HAL RDM

Good morning RIOT developers, Before giving a review in the mentioned PR, I would like to give some shorts comments on here, that wouldn't fit in the PR. While I really like the new approach to access lower levels directly and making the integration of new network stacks a lot easier, I feel