benpicco
benpicco
`ZTIMER_MSEC` might not always be available. But you can use [`xtimer_msleep()`](https://github.com/RIOT-OS/RIOT/blob/master/sys/include/ztimer/xtimer_compat.h#L140) which will always select an appropriate backend.
Great that you took that over! But why does the round-trip-time get so much worse? Since `at86rf2xx` is a 'full-mac' device, I'd expect the submac to do very little here...
I'm not sure if this is the right thing to do since you'll need a way to verify your `.noiinit` section contains valid data anyway. e.g. a magic value at...
I agree that this is confusing, we can do much better simply by not trying to stack too much on top of each other - see #21219
Is this not already covered by the `CPU_HAS_BITBAND` code path?
Ah the Kinetis Bit Manipulation Engine is indeed different from the ARM bit-banding extension! I would have thought they'd just use the standard functionality under a different name.
Thank you for debugging this! I now wonder if it would be easier converting the driver to the new radio HAL / subMAC so we can use the common 802.15.4...
A callback struct with a NULL handler does no harm in itself. Only when you try to add it to an event queue, things will blow up.
> For example when runnin IEEE802154 over LoRa I still want to see the currently used spreading factor, coding rate etc. That should be handled via the (extended) `ieee802154_phy_conf_t` struct,...
How do we proceed here?