-
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
net/l2util: add eui_short/48/64_get() #12641
Closed
Closed
Changes from 8 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
523d5cf
net/l2util: add l2util_get_eui_short/48/64()
benpicco 3366c83
fixup! net/l2util: add l2util_get_eui_short/48/64()
benpicco 70c9cf2
sys/luid: add warning to use eui*_get() instead of luid_get_eui*()
benpicco 94a3bed
fixup! fixup! net/l2util: add l2util_get_eui_short/48/64()
benpicco 18ce9b4
fixup! fixup! fixup! net/l2util: add l2util_get_eui_short/48/64()
benpicco 70b87a4
fixup! sys/luid: add warning to use eui*_get() instead of luid_get_eu…
benpicco 9ed80a2
fixup! fixup! fixup! fixup! net/l2util: add l2util_get_eui_short/48/64()
benpicco bcc1433
fixup! fixup! fixup! fixup! fixup! net/l2util: add l2util_get_eui_sho…
benpicco 78ce6c1
fixup! fixup! fixup! fixup! fixup! fixup! net/l2util: add l2util_get_…
benpicco ef45452
drivers/at86rf2xx: convert to use l2util_generate_eui64()
benpicco fdc9e4a
boards/samr21-xpro: provide board_get_eui64()
benpicco File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Please relight my memory: What is the driver name of the netdev?
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.
The idea was that a EUI would be assigned to a certain device/driver.
E.g. both
samr21-xpro
andsame54-xpro
contain a EUI-64 resp. EUI-48.On
samr21-xpro
that should only be used for the first device of theat86rf2xx
driver…It's not pretty but so far we haven't come up with a better solution to assign IDs to netdevs.
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.
Mhhhh its not just not pretty, it can be very costly. Both the string will cost memory, and string operations aren't the most efficient either. :-/
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.
Would it make sense to use
NETDEV_TYPE_
here?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.
If the
netdev
allocations would be in an xfa this would be simpler :-/.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.
For this we would have the migration benefit, that this could be done driver by driver.
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.
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.
I thought it is not. If it is why use the (more RAM heavy) name?
If we don't use the current approach, I believe we don't have. Also: only every board that provides a netdev
params
.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.
Well we just have to touch every netdev driver (to do the index -> params mapping inside the driver instead of auto_init). I just want to be sure that's the right way to go before I shave that Yak 😉
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.
See #12641 (comment). As far as I understand
board.c
might not exist anymore in the near future :-/.