fabian18
fabian18
Oops forgot the rebase ...
Thank You!
In case of `slip` it has to do with this packet [hold](https://github.com/RIOT-OS/RIOT/blob/2327d74d24af600caa28159d54147556490a1de5/sys/net/gnrc/netif/gnrc_netif.c#L1882-L1884C12): ```C /* hold in case device was busy to not having to rewrite *all* the link * layer...
We could maybe prohibit to remove a packet snip which is not the first snip in the chain.
Sorry, then it was in the `else` above
fixed with #18969
The `msg_bus` module just came to my mind. Have you considered this as an alternative to callbacks, since you already said that you would like to be able to "unsubscribe"?...
Ok please squash.
I am observing that the hard fault in the test is also happening for `same54-xpro`, when `mtd->driver` is accessed in `mtd_init()`
I have very limited knowledge about linker scripts and it does not solve the hard fault, but I wonder if we have to subtract `_slot_aux_len` from `_fw_rom_length`.