@haukepetersen Thanks for you comments! Indeed the IRQ-disabling is not neccessary and was ment for testing purposes. I addressed you comments accordingly and will updated the PR later this day.

There is an other question at the moment. So far, I only tested the driver with the /tests/netdev test.
It would be important for us to have a working rpl-udp demo. In the Virtual meeting two weeks ago, we already discussed on this plan shortly. My conclusion was that it is possible with the PR "transceiver: netapi adapter #1969" to use the existing (old) network stack in combination with the new network device (this radio driver).

1. Is this assumption correct in general?
2. What steps would be neccessary to make the rpl_udp example runnable with the kw2x-rf radio driver?
3. As is saw it, the default transceiver has to be defined in transceiver.h even through the transceiver interface is not used anymore?

Sry about my confusion.

@jremmert-phytec-iot The netdev (and netapi) are currently under heavy construction, and I honestly doubt we will get them stable before Embedded world... I personally do not know much about the netapi adapter, maybe @authmillenon can shed some light on this?

As a short-term solution towards the Embedded World I would probably suggest to implement the old transceiver interface for you radio. Although it will be thrown out at some point, you can run the current network stack (and the rpl_udp demo) with it. Also implementing this should only take a day or two...

Ok, im currently in the process of adaption. Your right, that might be the savest option to get a stable demo.

I think I missunderstood the netdev-adapter and the last days I couln't figure out how it works.

Adapted to Transceiver interface and rebased.

Closed due to refactoring and reimplementation in #2756.