-
Notifications
You must be signed in to change notification settings - Fork 347
doc: nrf_modem: clean up the variants and feature page #1935
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
base: main
Are you sure you want to change the base?
Conversation
nordic-hani
commented
Nov 26, 2025
- Clean up the page to use the concept of "modem firmware products".
- The cellular variant of libmodem actually supports three different modem firmware products.
- Added example of exceptions from the table.
- Altered the existing note to become a footnote for the "AT" entry.
5bbd793 to
887051c
Compare
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-nrfxlib#1935 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
* Clean up the page to use wording "modem firmware". * The cellular variant of libmodem actually supports three different modem firmware products. * Added example of exceptions from the table. * Altered the existing note to become a footnote for the "AT" entry. Signed-off-by: Håvard Vermeer <havard.vermeer@nordicsemi.no>
887051c to
8e0a699
Compare
|
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-nrfxlib#1935 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
| ##################### | ||
|
|
||
| The Modem library comes in two variants, each with a specific feature set and support for a specific variant of the nRF91 Series firmware. | ||
| The Modem library comes in two *variants*, each with a specific feature set and support for the equivalent *modem firmware*. |
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 Modem library comes in two *variants*, each with a specific feature set and support for the equivalent *modem firmware*. | |
| The Modem library comes in two variants, each with a specific feature set and support for the equivalent modem firmware. |
I think these need not be in italics as these are normal terms used in the docs.
|
|
||
| * mfw-nr+_nrf91x1 | ||
|
|
||
| Features that are common across *modem firmware*, are also common across *Modem library variants*. |
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.
| Features that are common across *modem firmware*, are also common across *Modem library variants*. | |
| Features that are common across modem firmware are also common across Modem library variants. |
| | :ref:`nrf_modem_rs_capture_api` | :file:`nrf_modem_rs_capture.h` | No | Yes | Yes | No | | ||
| +---------------------------------+--------------------------------+-------------+-------------+-----------------+-----------------+ | ||
|
|
||
| .. [#at-note] Although the Modem library AT interface is fully supported by both Modem library variants, the AT command set supported by the cellular modem firmware and the DECT NR+ modem firmware is different. |
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.
Could remove the footnote as it is not used in the table.
| .. note:: | ||
| Although the Modem library AT interface is fully supported by both Modem library variants, the AT command set supported by the cellular and DECT NR+ PHY firmware is different. | ||
| The different APIs may have certain subsets of functionality that are only supported by certain modem firmware and modem firmware versions. |
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 different APIs may have certain subsets of functionality that are only supported by certain modem firmware and modem firmware versions. | |
| The different APIs might have certain subsets of functionality that are only supported by certain modem firmware and modem firmware versions. |
| .. note:: | ||
| Although the Modem library AT interface is fully supported by both Modem library variants, the AT command set supported by the cellular and DECT NR+ PHY firmware is different. | ||
| The different APIs may have certain subsets of functionality that are only supported by certain modem firmware and modem firmware versions. | ||
| For example, :ref:`nrf_sockets` is supported for all cellular firmware products (and Modem library variants), but the socket option ``NRF_SO_SEC_CIPHERSUITE_USED`` is not suported by mfw_nrf9160. |
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 example, :ref:`nrf_sockets` is supported for all cellular firmware products (and Modem library variants), but the socket option ``NRF_SO_SEC_CIPHERSUITE_USED`` is not suported by mfw_nrf9160. | |
| For example, :ref:`nrf_sockets` is supported for all cellular firmware (and Modem library variants), but the socket option ``NRF_SO_SEC_CIPHERSUITE_USED`` is not supported by mfw_nrf9160. |
| Exceptions like this are documented with notes like the one below: | ||
|
|
||
| .. code-block:: c | ||
| /** | ||
| * @note This is only supported by the following modem firmware products: |
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.
| Exceptions like this are documented with notes like the one below: | |
| .. code-block:: c | |
| /** | |
| * @note This is only supported by the following modem firmware products: | |
| Exceptions like this are documented with notes like the following in the header files: | |
| .. code-block:: c | |
| /** | |
| * @note This is only supported by the following modem firmware: |
Maybe we could mention that it is documented in the header file?


