ng_netconf: adapt byte orders to output #2885
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The byte order of addresses in ng_netdev/ng_netconf is a little bit messed up:
ng_at86rf2xx
it is little endian (regardless of the host byte order), becauseng_at86rf2xx
assumes the address is stored in little endianxbee
is doing.My solution: addresses (including PAN ID) shall always be configured in network byte (big endian) order. If the protocol does not use network byte order (e.g. IEEE 802.15.4) it needs to convert it to their specific order.