Remove swtimer #4

OlegHahm · 2013-02-28T17:57:28Z

vtimer replaced swtimer which is therefore marked as deprecated. But swtimer is still available in the repository and used by some libraries and projects.

miri64 · 2013-04-02T13:02:21Z

That should do it

OlegHahm · 2013-04-09T11:48:03Z

Looks good at a first glance. Could you make a pull request?

see #4

miri64 · 2013-04-11T13:30:01Z

Rebased it to the current HEAD

chronos support updated

Kinetis SPI configuration granularity

Closes RIOT-OS#4

Improve OT_JOB + auto-init improved

newlib: use RIOT dependency system for _GNU_SOURCE instead

added GNU parallel

pr/nanocoap/block2 fixes 2

The test randomly fails on `native` due to timers being not accurate but it cannot be otherwise. So better disable it than raising fake errors. main(): This is RIOT! (Version: buildtest) Testing generic evtimer This should list 2 items ev #1 offset=1000 ev #2 offset=500 This should list 4 items ev #1 offset=659 ev #2 offset=341 ev RIOT-OS#3 offset=500 ev RIOT-OS#4 offset=2454 Are the reception times of all 4 msgs close to the supposed values? At 662 ms received msg 0: "#2 supposed to be 659" At 1009 ms received msg 1: "#0 supposed to be 1000" At 1511 ms received msg 2: "#1 supposed to be 1500" Traceback (most recent call last): File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/tests/evtimer_msg/tests/01-run.py", line 33, in <module> sys.exit(run(testfunc)) File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/dist/pythonlibs/testrunner/__init__.py", line 29, in run testfunc(child) File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/tests/evtimer_msg/tests/01-run.py", line 26, in testfunc assert(actual in range(expected - ACCEPTED_ERROR, expected + ACCEPTED_ERROR)) AssertionError

add PS module to Kconfig and app

Create compilation_check.yml

18392: drivers/servo: reimplement with high level interface r=benpicco a=maribu ### Contribution description The previous servo driver didn't provide any benefit over using PWM directly, as users controlled the servo in terms of PWM duty cycles. This changes the interface to provide a high level interface that abstracts the gory PWM details. In addition, a SAUL layer and auto-initialization is provided. ### Testing procedure The test application provides access to the servo driver via the `saul` shell command. ``` > saul 2022-08-02 22:12:31,826 # saul 2022-08-02 22:12:31,827 # ID Class Name 2022-08-02 22:12:31,830 # #0 ACT_SWITCH LD1(green) 2022-08-02 22:12:31,832 # #1 ACT_SWITCH LD2(blue) 2022-08-02 22:12:31,834 # #2 ACT_SWITCH LD3(red) 2022-08-02 22:12:31,837 # #3 SENSE_BTN B1(User button) 2022-08-02 22:12:31,838 # #4 ACT_SERVO servo > saul write 4 0 2022-08-02 22:12:41,443 # saul write 4 0 2022-08-02 22:12:41,445 # Writing to device #4 - servo 2022-08-02 22:12:41,447 # Data: 0 2022-08-02 22:12:41,450 # [servo] setting 0 to 2949 (0 / 255) 2022-08-02 22:12:41,453 # data successfully written to device #4 > saul write 4 256 2022-08-02 22:12:45,343 # saul write 4 256 2022-08-02 22:12:45,346 # Writing to device #4 - servo 2022-08-02 22:12:45,347 # Data: 256 2022-08-02 22:12:45,351 # [servo] setting 0 to 6865 (255 / 255) 2022-08-02 22:12:45,354 # data successfully written to device #4 ``` Each write resulted in the MG90S servo that I connected to move to the corresponding position. ### Issues/PRs references 19292: sys/phydat: Fix unit confusion r=benpicco a=maribu ### Contribution description Previously, `UNIT_G` was used for g-force with the correct symbol `g`, `UNIT_GR` for gram (as in kilogram) with the incorrect symbol `G` (which would be correct for Gauss), and `UNIT_GS` for Gauss with symbol `Gs` (which is an alternative correct symbol). To avoid confusion between G-Force, Gauss, and Gram the units have been renamed to `UNIT_G_FORCE`, `UNIT_GRAM`, and `UNIT_GAUSS`. In addition, gram now uses the correct symbol `g`; which sadly is the same as for g-force. But usually there is enough context to tell them apart. ### Testing procedure Green CI ### Issues/PRs references None 19294: sys/shell: don't include suit command by default r=benpicco a=benpicco 19295: gcoap: Finish the gcoap_get_resource_list_tl -> gcoap_get_resource_list renaming r=benpicco a=chrysn ### Contribution description In #16688, an argument was added to the `gcoap_get_resource_list` function by creating a new function `gcoap_get_resource_list_tl` with a deprecation and roll-over plan. This plan has not been acted on so far. This PR shortens the original plan by just adding the argument to `gcoap_get_resource_list` and removing `gcoap_get_resource_list_tl` in a single go. The rationale for this deviation is that while it's a public API, its only two practical consumers are the (built-in) well-known/core implementation, and the (built-in) CoRE Resource Directory (cord) endpoint. Moreover, a further change to this API (switching over to `coap_block_slicer_t`) is expected to happen within this release cycle, which would take something like 4 total releases to get through otherwise, which is unrealistic for an API that there are no known external users of. A second commit clean up ToDo items (in the changed function's documentation) that referred to a IETF draft that has long been abandoned by the CoRE WG. ### Testing procedure Plain inspection and CI passing should suffice. ### AOB There is a second analogous pair left over from #16688, `gcoap_req_send` / `gcoap_req_send_tl`. As that *is* expected to be used widely, I prefer not to mix these two concerns, and get the present one through without unnecessary hold-up. Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de> Co-authored-by: Benjamin Valentin <benjamin.valentin@bht-berlin.de> Co-authored-by: chrysn <chrysn@fsfe.org>

18392: drivers/servo: reimplement with high level interface r=benpicco a=maribu ### Contribution description The previous servo driver didn't provide any benefit over using PWM directly, as users controlled the servo in terms of PWM duty cycles. This changes the interface to provide a high level interface that abstracts the gory PWM details. In addition, a SAUL layer and auto-initialization is provided. ### Testing procedure The test application provides access to the servo driver via the `saul` shell command. ``` > saul 2022-08-02 22:12:31,826 # saul 2022-08-02 22:12:31,827 # ID Class Name 2022-08-02 22:12:31,830 # #0 ACT_SWITCH LD1(green) 2022-08-02 22:12:31,832 # #1 ACT_SWITCH LD2(blue) 2022-08-02 22:12:31,834 # #2 ACT_SWITCH LD3(red) 2022-08-02 22:12:31,837 # #3 SENSE_BTN B1(User button) 2022-08-02 22:12:31,838 # #4 ACT_SERVO servo > saul write 4 0 2022-08-02 22:12:41,443 # saul write 4 0 2022-08-02 22:12:41,445 # Writing to device #4 - servo 2022-08-02 22:12:41,447 # Data: 0 2022-08-02 22:12:41,450 # [servo] setting 0 to 2949 (0 / 255) 2022-08-02 22:12:41,453 # data successfully written to device #4 > saul write 4 256 2022-08-02 22:12:45,343 # saul write 4 256 2022-08-02 22:12:45,346 # Writing to device #4 - servo 2022-08-02 22:12:45,347 # Data: 256 2022-08-02 22:12:45,351 # [servo] setting 0 to 6865 (255 / 255) 2022-08-02 22:12:45,354 # data successfully written to device #4 ``` Each write resulted in the MG90S servo that I connected to move to the corresponding position. ### Issues/PRs references 19292: sys/phydat: Fix unit confusion r=benpicco a=maribu ### Contribution description Previously, `UNIT_G` was used for g-force with the correct symbol `g`, `UNIT_GR` for gram (as in kilogram) with the incorrect symbol `G` (which would be correct for Gauss), and `UNIT_GS` for Gauss with symbol `Gs` (which is an alternative correct symbol). To avoid confusion between G-Force, Gauss, and Gram the units have been renamed to `UNIT_G_FORCE`, `UNIT_GRAM`, and `UNIT_GAUSS`. In addition, gram now uses the correct symbol `g`; which sadly is the same as for g-force. But usually there is enough context to tell them apart. ### Testing procedure Green CI ### Issues/PRs references None Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de>

18392: drivers/servo: reimplement with high level interface r=benpicco a=maribu ### Contribution description The previous servo driver didn't provide any benefit over using PWM directly, as users controlled the servo in terms of PWM duty cycles. This changes the interface to provide a high level interface that abstracts the gory PWM details. In addition, a SAUL layer and auto-initialization is provided. ### Testing procedure The test application provides access to the servo driver via the `saul` shell command. ``` > saul 2022-08-02 22:12:31,826 # saul 2022-08-02 22:12:31,827 # ID Class Name 2022-08-02 22:12:31,830 # #0 ACT_SWITCH LD1(green) 2022-08-02 22:12:31,832 # #1 ACT_SWITCH LD2(blue) 2022-08-02 22:12:31,834 # #2 ACT_SWITCH LD3(red) 2022-08-02 22:12:31,837 # #3 SENSE_BTN B1(User button) 2022-08-02 22:12:31,838 # #4 ACT_SERVO servo > saul write 4 0 2022-08-02 22:12:41,443 # saul write 4 0 2022-08-02 22:12:41,445 # Writing to device #4 - servo 2022-08-02 22:12:41,447 # Data: 0 2022-08-02 22:12:41,450 # [servo] setting 0 to 2949 (0 / 255) 2022-08-02 22:12:41,453 # data successfully written to device #4 > saul write 4 256 2022-08-02 22:12:45,343 # saul write 4 256 2022-08-02 22:12:45,346 # Writing to device #4 - servo 2022-08-02 22:12:45,347 # Data: 256 2022-08-02 22:12:45,351 # [servo] setting 0 to 6865 (255 / 255) 2022-08-02 22:12:45,354 # data successfully written to device #4 ``` Each write resulted in the MG90S servo that I connected to move to the corresponding position. ### Issues/PRs references Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de>

Add CAN FD support to STM32G4 and native architecture

miri64 referenced this issue in miri64/RIOT Apr 11, 2013

Remove swtimer

07e8ac9

see #4

miri64 mentioned this issue Apr 11, 2013

Remove swtimer #34

Merged

miri64 closed this as completed Apr 24, 2013

mehlis mentioned this issue Aug 13, 2013

segfault in vtimer update shortterm #132

Closed

benpicco mentioned this issue Oct 26, 2013

native uart0 crashes when no real terminal is attached #270

Closed

OlegHahm referenced this issue in OlegHahm/RIOT Nov 6, 2013

Merge pull request #4 from mikoff/master

f4869ab

chronos support updated

maxencechotard mentioned this issue Dec 10, 2014

samr21 : RPL_UDP: always falling into "isr_hard_fault" #2173

Closed

jnohlgard referenced this issue in jnohlgard/RIOT Jan 12, 2015

Merge pull request #4 from gebart/pr/kinetis-spi-periph-conf

3bfcc71

Kinetis SPI configuration granularity

daniel-k mentioned this issue Jul 8, 2015

cpu/cortexm_common: additional information on hardfault #3333

Merged

OlegHahm mentioned this issue Jul 10, 2015

netdev2_tap: crashes when hammered #3341

Closed

nmeum added a commit to nmeum/RIOT that referenced this issue May 1, 2017

Fix for issue RIOT-OS#4

e499e7a

Closes RIOT-OS#4

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Jun 1, 2017

Merge pull request RIOT-OS#4 from biboc/openthread-core-2

fbea41a

Improve OT_JOB + auto-init improved

roberthartung added a commit to roberthartung/RIOT that referenced this issue Jun 29, 2017

gitlab ci: PORT test RIOT-OS#4

43eada8

roberthartung added a commit to roberthartung/RIOT that referenced this issue Jul 24, 2017

gitlab ci: PORT test RIOT-OS#4

8acbfbc

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Oct 24, 2017

Merge pull request RIOT-OS#4 from miri64/newlib/enh/newlib_gnu_source

4b6160e

newlib: use RIOT dependency system for _GNU_SOURCE instead

nunux13 mentioned this issue May 19, 2018

__libc_init_array () trigger HARD FAULT HANDLER on SAML21E18B arm core bug #9155

Closed

ZetaR60 pushed a commit to ZetaR60/RIOT that referenced this issue Jun 30, 2018

Merge pull request RIOT-OS#4 from phiros/add_gnu_parallel

44e5969

added GNU parallel

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Oct 13, 2018

Merge pull request RIOT-OS#4 from kb2ma/nanocoap/block2-fixes2

a8e1e97

pr/nanocoap/block2 fixes 2

This was referenced Jul 16, 2019

pkg/semtech_loramac: fix memcpy to uninitialized pointer #11847

Merged

pkg/semtech_loramac: fix memcpy to uninitialized pointer [backport 2019.07] #11848

Merged

fjmolinas mentioned this issue Nov 25, 2019

doc: document how to handle multiple cpu_models in a directory #12407

Open

janschlicht mentioned this issue Mar 10, 2020

driver/bme680: add I2C/SPI driver for BME680 device #12717

Merged

leandrolanzieri referenced this issue in leandrolanzieri/RIOT Sep 9, 2020

Merge pull request #4 from leandrolanzieri/pr/crypto-ewsn2020/kconfig/ps

555644f

add PS module to Kconfig and app

CW-75 pushed a commit to CW-75/RIOT that referenced this issue Jul 1, 2022

Merge pull request RIOT-OS#4 from Mesh4all/type/CI

f19d652

Create compilation_check.yml

gdoffe added a commit to cogip/RIOT that referenced this issue Feb 23, 2024

Merge pull request RIOT-OS#4 from cogip/fdcan

a0832e5

Add CAN FD support to STM32G4 and native architecture

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remove swtimer #4

Remove swtimer #4

OlegHahm commented Feb 28, 2013

miri64 commented Apr 2, 2013

OlegHahm commented Apr 9, 2013

miri64 commented Apr 11, 2013

Remove swtimer #4

Remove swtimer #4

Comments

OlegHahm commented Feb 28, 2013

miri64 commented Apr 2, 2013

OlegHahm commented Apr 9, 2013

miri64 commented Apr 11, 2013