michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: release: Migration guide for CONFIG_NET_INTERFACE_NAME option

Browse source 
Clarified the impact of CONFIG_NET_INTERFACE_NAME Kconfig option
as it can change how SO_BINDTODEVICE BSD socket option behaves.

Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
This commit is contained in:
Jukka Rissanen 2023-09-05 10:32:49 +03:00 • committed by Fabio Baltieri
commit ccc2a7a90d
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/releases/migration-guide-3.5.rst
View file

@ -47,6 +47,16 @@ Required changes
- "IO" -> <( DT_MEM_ARM(ATTR_MPU_IO) )>
- "EXTMEM" -> <( DT_MEM_ARM(ATTR_MPU_EXTMEM) )>
* A new networking Kconfig option :kconfig:option:`CONFIG_NET_INTERFACE_NAME`
defaults to ``y``. The option allows user to set a name to a network interface.
During system startup a default name is assigned to the network interface like
``eth0`` to the first Ethernet network interface. The option affects the behavior
of ``SO_BINDTODEVICE`` BSD socket option. If the Kconfig option is set to ``n``,
which is how the system worked earlier, then the name of the device assigned
to the network interface is used by the ``SO_BINDTODEVICE`` socket option.
If the Kconfig option is set to ``y`` (current default), then the network
interface name is used by the ``SO_BINDTODEVICE`` socket option.
Recommended Changes
*******************