-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Update code PairDevice calls to work with network params. #14429
Update code PairDevice calls to work with network params. #14429
Conversation
Co-authored-by: Boris Zbarsky <[email protected]>
(Note this needs a rebase to resolve the Darwin test failure) |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale pull request has been automatically closed. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
PR #14429: Size comparison from 796ba98 to fd49c4f Increases above 0.2%:
Increases (2 builds for linux)
Decreases (1 build for linux)
Full report (31 builds for cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Something somewhere got messed becuase the initialization happens in the destructor which is not correct for obvious reasons.
PR #14429: Size comparison from 535c6c8 to 0196c04 Increases above 0.2%:
Increases (2 builds for linux)
Decreases (2 builds for linux)
Full report (26 builds for cyw30739, efr32, esp32, k32w, linux, nrfconnect, p6, telink)
|
Functions order was confusing the documentation.
PR #14429: Size comparison from 535c6c8 to 39a5c4a Increases above 0.2%:
Increases (26 builds for cyw30739, efr32, esp32, k32w, linux, nrfconnect, p6, telink)
Decreases (21 builds for cyw30739, efr32, esp32, k32w, linux, p6)
Full report (26 builds for cyw30739, efr32, esp32, k32w, linux, nrfconnect, p6, telink)
|
Problem
The setup code PairDevice functions had no way to pass in commissioning parameters, which meant it wasn't possible to commission BLE devices by code.
Change overview
Testing
Chip tool commissioning M5 over BLE