[DNM] Bt upmerge fixes#22125
Closed
weeTike wants to merge 18 commits into
Closed
Conversation
Run migrate_posix_kconfigs.py to rename deprecated POSIX API Kconfig options. GETOPT was replaced by POSIX_C_LIB_EXT which default to n. Remove the obsolete default value change and use the replacement POSIX_C_LIB_EXT. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
Update version to upmerged sdk-zephyr and sdk-mcuboot. Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
Update Matter SDK revision. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no>
The combination of AF_PACKET and IPPROTO_RAW is not correct as packet sockets should only be used with IEEE 802.3 protocol numbers. As the support for this combination will likely be soon removed from Zephyr, switch to use DGRAM packet socket instead. Using ETH_P_ALL is fine in this case, as OpenThread interface only provides IPv6 packets anyway. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
The combination of AF_PACKET and IPPROTO_RAW is not correct as packet sockets should only be used with IEEE 802.3 protocol numbers. As the support for this combination will likely be soon removed from Zephyr, switch to use DGRAM packet socket instead. As PPP L2 only supports IP/IPv6 packets, specify the L2 protocol type field accordingly so that the L2 can interpret the packet data correctly. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
The combination of AF_PACKET and IPPROTO_RAW is not correct as packet sockets should only be used with IEEE 802.3 protocol numbers. As the support for this combination will likely be soon removed from Zephyr, switch to use DGRAM packet socket instead. As PPP L2 only supports IP/IPv6 packets, specify the L2 protocol type field accordingly so that the L2 can interpret the packet data correctly. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
Totally unexpected, the exact same Kconfig options and C designators are introduced in the upstream Zephyr repository. Prefix the Kconfig options of the NCS implementation with NRF to resolve the conflicts. Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
Refer to commit zephyrproject-rtos/zephyr@d382fca Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
last_erased_page_start_offset has been removed by zephyrproject-rtos/zephyr#82326. Need to change accordingly to not break the build. Signed-off-by: Maximilian Deubel <maximilian.deubel@nordicsemi.no>
This has been renamed upstream. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
BT_ISO_CHAN_TYPE_CONNECTED has been refactored into BT_ISO_CHAN_TYPE_CENTRAL and BT_ISO_CHAN_TYPE_PERIPHERAL. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
Signature was changed to have const bt_conn upstream. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
This is needed after changes in upstream zephyr. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
Adjust for new net_linkaddr definition. Signed-off-by: Maximilian Deubel <maximilian.deubel@nordicsemi.no>
Moved OpenThread-related Kconfigs from L2 layer to modules/openthread. All of those configs were not strictly related to the L2 layer, so they fits better to OpenThread module. This operation allows using OpenThread Kconfigs even if L2 layer is disabled. Enabling NET_L2_OPENTHREAD also configures those configs by selecting the OPENTHREAD kconfig, so there is no change regarding backwards compatibility. The only change is that the Kconfigs related to Thread were moved to the modules space, so their location in the menuconfig also changed. Once it is done, a choice for setting different L2 implementations seems to be redundant. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no> Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no>
github-actions
Bot
added
doc-required
Contributor
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:more detailsGithub labels
List of changed files detected by CI (0)Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
Contributor
|
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 3 projects with PR revision Note: This message is automatically posted and updated by the Manifest GitHub Action. |
The signature of bt_conn_get_remote_info changed upstream to use const conn *, but in this usecase conn * should not be const. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
BT_GATT_CCC_INITIALIZER was renamed upstream. It is now called BT_GATT_CCC_MANAGED_USER_DATA_INIT. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
Upstream refactor means it is no longer needed by default. Signed-off-by: Timothy Keys <timothy.keys@nordicsemi.no>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.
No description provided.