-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add support for random MAC address #19
Conversation
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.
Looks good to me. Maybe in the documentation you can write a very short paragraph about the options for the MAC address setting - that would help the developers a lot, IMHO. They would not need to look into the Kconfig setting.
Add a build time option to generate random MAC address, this helps in test deployments. Used Zephyr API in the BM code to simplify things, as srand() was giving same MAC address (seed problems). Signed-off-by: Chaitanya Tata <[email protected]>
f11733a
to
5622bc8
Compare
Done, added a separate section. |
This build path isn't tested, fix build errors. Signed-off-by: Chaitanya Tata <[email protected]>
Group them logically for a better navigation and reading experience. Signed-off-by: Chaitanya Tata <[email protected]>
5622bc8
to
88d8682
Compare
Add for both RPU context and FMAC context. Signed-off-by: Chaitanya Tata <[email protected]>
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.
Thanks! @sachinthegreen pls, review the code part as well :)
MAC address can be passed to init which takes precedence over any build time options. Signed-off-by: Chaitanya Tata <[email protected]>
Add a build time option to generate random MAC address, this helps in test deployments.
Used Zephyr API in the BM code to simplify things, as srand() was giving same MAC address (seed problems).