Skip to content

Removed Features and Modules

This document contains a listing of all features and modules that were removed from RIOT at some point in time, mostly due to missing maintenance. The purpose of this list is to have a reference point for reintegrating those features in the future, if new interest arises or a new maintainer is found.

This list is not supposed to contain a change log of all the things that are being removed from RIOT, but should contain only full modules that are removed without any alternative being merged at the same time. For example things like the first netdev should not be put in this list, as a successor (former netdev2) has been merged.

For each high-level feature removed there should be one entry in this list. The entries should be ordered alphabetically and comply to the following template:

### path/feature_name [HASH of removal commit]
Author(s):
- author 1 <foo.bar@abc.com>
- author 2 <a.b@c.net>
Reason for removal:
- give a short and comprehensive reasoning why this feature was removed
- typical reasons are:
- feature is not maintained anymore
- lack of hardware so feature can not be tested (anymore)
- feature was never used and there is no reason for keeping it

Additionally, a link reference for the commit on GitHub is added to the bottom of this document.

By putting the name of the removed feature and the commit hash in the same line, one can very quickly find the commit using git grep.

Listing the authors of the removed code is done for appreciation of their work. This way, their names are never removed from the RIOT repository.

Author(s):

Reason for removal:

  • board is quite outdated
  • board cannot be automatically tested for lack of UART
  • board has many special cases, which hurt upgrade to msp430-elf-gcc 9.x
  • the onboard radio has been unsupported for a while
  • no one seems to use the board, no one seems to maintain it

Author(s):

Reason for removal:

  • Hardware not available so can’t be tested

Author:

Reasons for removal:

  • The board is a custom design at the RWTH Aachen, so only two persons have access to the hardware
  • It was unmaintained for several month now
  • Various refactoring PRs affected the ATmega CPU family have not been tested, it is unclear if the board is actually usable with RIOT

Author:

Reasons for removal:

  • UART input not supported.
  • Hardware not available for testing and not available for purchase either.
  • Not actively maintained / broken for some time.

Author(s):

Reason for removal:

  • this was an early development board by Nordic which was discontinued (successor: nrf51dk)
  • also for a BLE DEVKIT.N board from Mommosoft, which was discontinued as well
  • no hardware available anymore for testing, many exclusions from CI

Author(s):

Reason for removal:

  • this was an early development board by Nordic which was discontinued (successor: nrf51dongle)
  • no hardware available anymore for testing

Author(s):

Reason for removal:

  • this was an early development board by Nordic which was discontinued (successor: nrf51dk)
  • no hardware available anymore for testing

Author(s):

Reason for removal:

  • code broken and excluded from all tests for a long time
  • no maintainer available

Author(s):

Reason for removal:

  • The old implementation of the SLWSTK6220A based on cpu/ezr32wg did not use the Gecko SDK, that other EFM32-based boards do use
  • The old implementation had limited peripherals supported
  • New implementation (with the same name) that is based on cpu/efm32 was added in commit fe941ac9fe3f81c0f08ff3b8564cf439639abcda

Author(s):

Reason for removal:

  • This board is sold only B2B, so that our community members from the DIY/hobbyist community and academia do not have access to the board. Our community members from the industry mostly develop their own hardware and, therefore, have no interest in supporting this board. As result, none of the RIOT core contributors has access to the hardware, preventing us from doing the necessary testing for maintaining this board.

Author(s):

Reason for removal:

  • hardware not available to the community for testing
  • original author and maintainer won’t be able to maintain the code

Author(s):

Reason for removal:

  • no longer accessible on the IoT-LAB testbed

Author(s):

Reason for removal:

  • code broken and excluded from all tests for a long time
  • no maintainer available

Author(s):

Reason for removal:

  • hardware not available to the community for testing
  • original author and maintainer won’t be able to maintain the code

Author:

  • Neil Jones neil.jones@imgtec.com

  • No boards use this CPU (the only one was mips-malta).

  • (Same reasons as mips-malta)

Author:

Reasons for removal:

  • Not maintained anymore
  • Current state is not very useful and nobody claimed to use it

Author(s):

Reason for removal:

  • code broken and excluded from all tests for a long time
  • no maintainer available

Author(s):

Reason for removal:

Author(s):

Reason for removal:

Author(s):

Reason for removal:

  • Unused, untested and no longer needed

Author(s):

Reason for removal:

  • Stale upstream (last update to date in Mar 2018)
  • Ported version even older (last update Feb 2016)
  • Updating to more recent version would be more effort than its worth

Author:

Reasons for removal:

  • Not maintained anymore, no updates for 8 years
  • Upstream libcoap allows building with RIOT, so there is a migration path for users

Author(s):

Reason for removal:

  • Outdated, unmaintained and no longer working

Author:

Reasons for removal:

  • Package has not been update since 2013.
  • Tests were never integrated to the CI.
  • NHDP, which was the only upstream user, has been removed.

Author(s):

Reason for removal:

  • No users besides the test
  • The qDSA signature does not seem to have received the level of attention and scrutiny by the crypto community that would justify inclusion in a general purpose OS

Author(s):

Reason for removal:

  • Provides some feature as sys/event_thread
  • Has been deprecated directly in the first release it was provided

Author:

Reasons for removal:

  • Not maintained anymore.
  • Existing quality and security defects.

Author:

Reasons for removal:

  • Not maintained anymore
  • Not used in GNRC

Author:

Reasons for removal:

  • Not maintained anymore.
  • Does not comply with the current RIOT programming practices.

Author(s):

Reasons for removal:

  • Unsafe code.
  • Did not comply with RIOT standards.
  • More standard alternatives available (such as CBOR).