-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cc2538_rf: Don't use netdev_ieee802154_t for channel #10426
Conversation
Tested with two firefly boards on the IoT-LAB, appears to work for me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on remote-rev, ACK! Still shows the channel, how was it handled before anyway?
please squash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comment was addressed. Please squash.
edbb4f6
to
8970446
Compare
Squashed!
getters and setters are also in the |
Contribution description
This PR modifies the behaviour of the cc2538_rf driver to not propagate the channel to the netdev_ieee802154_t struct. This helps the goal of separating the netdev and the ieee802154_t layer by another bit. The end goal is to remove the channel from the netdev_ieee802154_t struct.
The performance impact of this change should be negligible, the NETOPT_CHANNEL call is only used by the ifconfig command.
Testing procedure
Test whether:
Issues/PRs references
related to #10401, part of #7736
disclaimer: I don't own a board with the cc2538 on it so I'm flying blind here. As long as the actual channel getter work, the code should work.