-
Notifications
You must be signed in to change notification settings - Fork 1.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
manifest: nrf_modem v2.6.0 #14173
manifest: nrf_modem v2.6.0 #14173
Conversation
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
92f818b
to
4dc09e2
Compare
4dc09e2
to
8b6ea53
Compare
8b6ea53
to
38ab737
Compare
38ab737
to
7b4513f
Compare
@@ -540,30 +540,31 @@ Syntax | |||
|
|||
* ``<value>`` is an integer that indicates the packet data network ID to bind to. | |||
|
|||
* ``50`` - :c:macro:`SO_RAI_NO_DATA` (set-only). |
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.
Just a comment: I think that it makes sense to remove these from the documentation. Given that these are deprecated, we will map the old values to new values in SLM after the 2.6.0 release.
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 old values will be kept in the modem library for a couple of releases, so there should be no need to map the old values to the new ones.
@@ -19,6 +19,40 @@ The following changes are mandatory to make your application work in the same wa | |||
The setting controls whether the SLM connects automatically to the network on startup. | |||
You can read and write it using the ``AT#XCARRIER="auto_connect"`` command. | |||
|
|||
* The handling of Release Assistance Indication (RAI) socket options has been updated in the ``#XSOCKETOPT`` command. |
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 SLM part should be unnecessary as the old values work as well for now, and we will map those to new values under the hood after 2.6.0.
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 old values work as well for now, though the user should update their code to the new values. @divipillai should we add it to the migration guide for the NCS version where we deprecate functionality or the NCS version where we remove the old implementation completely (after it has been deprecated for a while)?
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.
As we now have a mechanism in place in SLM to keep such values unchanged (we only change the mapping in SLM, so that the customer-facing interface doesn't change), it may well be that they will never change from the SLM user's point of view.
Though if doing this (which I think is what we want, to limit breaking changes) I don't know whether it actually makes sense to introduce the new values in the documentation unless they work somehow differently than the old ones?
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 think that the new values are more well thought out than the previous ones So I would like to have them in SLM.
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.
Let's have them then, but also keep the other ones forever (without advertising them)?
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 reference: The section about RAI in SLM is removed from the migration guide for this release. If the old values are removed at a later point (from SLM user perspective), it should be added to the migration guide then.
7b4513f
to
c240a8f
Compare
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
__cmock_nrf_modem_at_cmd_IgnoreArg_len(); | ||
__cmock_nrf_modem_at_cmd_ReturnArrayThruPtr_buf(cnmi_reg_nok, sizeof(cnmi_reg_nok)); | ||
|
||
__mock_nrf_modem_at_printf_ExpectAndReturn("AT+CNMI=3,2,0,1", 0); |
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 need to play with this test to see how it affects on the test coverage and what's the point of the test in the modified form.
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!
7f8e33b
to
db7568c
Compare
Pull in latest nrf_modem. For a detailed list of changes, see its CHANGELOG file. Signed-off-by: Emanuele Di Santo <[email protected]>
db7568c
to
af823c6
Compare
We have opened #14195 as there is a need to combine the modem library release with the carrier library release. Please direct comments and approvals here. |
nrf_modem
v2.6.0 release.For a detail list of changes see the CHANGELOG file in
nrfxlib
.sdk-nrfxlib PR: nrfconnect/sdk-nrfxlib#1227