Yes, it is working, it's just a bit confusing for someone looking at
the code. Anyhow let's continue the discussion on the PR.
Thanks,
Aaron
2016-04-02 1:05 GMT+13:00 Martine Lenders :
> Hi,
> regardless, I opened a PR to fix it:
> https://github.com/RIOT-OS/RIOT/pull/5227
>
> Cheers,
> Martine
>
Hi,
regardless, I opened a PR to fix it:
https://github.com/RIOT-OS/RIOT/pull/5227
Cheers,
Martine
2016-04-01 13:59 GMT+02:00 Martine Lenders :
> Hi,
> just tested the behavior with `examples/default` and setting the short
> address is working, so it might be a bit messy implemented (mostly beca
Hi,
just tested the behavior with `examples/default` and setting the short
address is working, so it might be a bit messy implemented (mostly because
`netdev2_ieee802154_set()` was introduced later in the process), but it IS
working.
Cheers,
Martine
2016-04-01 6:55 GMT+02:00 Aaron Sowry :
> Actu
Actually, I don't think netdev2_ieee802154_set() will ever be called
from _set(), since the check to call this is 'if (res == -ENOTSUP)'.
'res' is set to '0' before the case statement and never changed in the
case of NETOPT_ADDRESS, so I guess the only reason it works at all is
because the device s
Hi,
I'm currently working on an 802.15.4 driver, and trying to use all the
fancy new boilerplate functionality which was merged recently. I'm
using the at86rf2xx driver as inspiration, but the way it sets some
options (e.g. the long and short addresses) confuses me a bit.
The at86rf2xx's netdev s
