-
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
[zephyr] Added support for getting GeneralDiagnostics attributes #12552
[zephyr] Added support for getting GeneralDiagnostics attributes #12552
Conversation
PR #12552: Size comparison from e8da685 to 7ca45e1 Increases (1 build for telink)
Full report (17 builds for esp32, k32w, mbed, p6, qpg, telink)
|
7ca45e1
to
4ad880f
Compare
PR #12552: Size comparison from 186c004 to 4ad880f Increases above 0.2%:
Increases (18 builds for linux, nrfconnect, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
1455e69
to
6f8c61a
Compare
6f8c61a
to
eeaaa34
Compare
PR #12552: Size comparison from bfdbd45 to eeaaa34 Increases above 0.2%:
Increases (18 builds for linux, nrfconnect, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Fast tracking, given this is a platform change by a platform manufacturer (modulo some error code replacements across others). |
9eafd0a
to
fba36eb
Compare
PR #12552: Size comparison from 21392ef to fba36eb Increases above 0.2%:
Increases (18 builds for linux, nrfconnect, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
nrfconnect/Zephyr platform doesn't support get methods for GeneralDiagnostics attributes * Added methods for getting RebootCount, NetworkInterfaces and BootReasons * Added to the InetIterator methods allowing to get interface type and hardware address using Zephyr API * Added BootReasonType to the DiagnosticDataProvider to remove dependency between platform and auto-generated code
fba36eb
to
d5fd8e3
Compare
PR #12552: Size comparison from f647393 to d5fd8e3 Increases above 0.2%:
Increases (18 builds for linux, nrfconnect, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
#### Problem 1b24137 (project-chip#12552) added `InetIterator::GetHardwareAddress()`, with an implementation for Zephyr and stubs for other builds. #### Change overview Implement `GetHardwareAddress()` for LwIP builds. (For sockets builds, there is no cross-platform access to the hardware MAC. Linux could use `SIOCGIFHWADDR`.) #### Testing CI (test from project-chip#12552)
#### Problem 1b24137 (project-chip#12552) added `InetIterator::GetHardwareAddress()`, with an implementation for Zephyr and stubs for other builds. #### Change overview Implement `GetHardwareAddress()` for LwIP builds. (For sockets builds, there is no cross-platform access to the hardware MAC. Linux could use `SIOCGIFHWADDR`.) #### Testing CI (test from project-chip#12552)
* [Inet] InetIterator::GetHardwareAddress for LwIP #### Problem 1b24137 (#12552) added `InetIterator::GetHardwareAddress()`, with an implementation for Zephyr and stubs for other builds. #### Change overview Implement `GetHardwareAddress()` for LwIP builds. (For sockets builds, there is no cross-platform access to the hardware MAC. Linux could use `SIOCGIFHWADDR`.) #### Testing CI (test from #12552) * fix buffer size check
Problem
nrfconnect/Zephyr platform doesn't support get methods for
GeneralDiagnostics
attributesChange overview
RebootCount
,NetworkInterfaces
andBootReasons
InterfaceIterator
methods allowing to get interface type and hardware address using Zephyr APIBootReasonType
to theDiagnosticDataProvider
to remove dependency between platform and auto-generated codeTesting
Tested manually for nrfconnect platform using Python CHIP Controller
zclread GeneralDiagnostics
commands