holzingk

Only one {config, "filename"} inside shell recognized

3

Inside a relx section, rebar3 recognizes two sys_config directives. Inside a shell section rebar3 does recognize only the first config directive. It would be nice if it would take care...

- [ ] Convert to `gen_event` structure - [ ] Figure out and document how this interacts with the other drivers

OTP 19.3.6 does not work with RTEMS 5

1

The cross-compilation configuration has RTEMS 4.12 hardcoded.

Module pmod_hb5 requires initialization, but is not accessible via grisp:add_device/2. Should be a gen_server imo

The `materialName` is not set in Materials defined with this plugin. I need it to access `GO_REVISION_${material name or dest}`. I am trying to use the destination as a workaround...

Clone OTP into ~/.cache/grisp and use git workspaces

1

One local clone of the repository is enough. Git supports having multiple workspaces of the same repository. This saves bandwidth, time and disk space.

Put build configuration in seperate gitignored file

2

The path to the toolchain depends on the host. Therefore it should not be part of version controlled files. The toolchain could either be specified in a seperate file in...

Detect when drivers were added or removed

3

At the moment you have to manually delete `_grisp` when there is a new or a deleted driver, otherwise you get an abscure build failure. Perhaps we shoud automate that...

Check if toolchain was rebuilt

2

If toolchain was rebuilt suggest users to rebuild OTP (with `--configure false`). Helps avoiding strange behaviours.

Useless error messages from Wifi/Network stack e.g. err: wlan0: ipv4_addroute: File exists

7

During boot of the board I always get this error message: ``` notice: wlan0: link state changed to UP err: wlan0: ipv4_addroute: File exists ```