Skip to content

Custom driver offload socket creation failing #46161

Answered by rlubos
alissa-maria asked this question in General
Discussion options

You must be logged in to vote
NET_SOCKET_REGISTER(ublox_sara_n310, NET_SOCKET_DEFAULT_PRIO, AF_UNSPEC,
			offload_is_supported, offload_socket);

This is wrong, if you set the same priority as the native socket implementation, then the native socket implementation will most likely be processed first, as the alphabetic order applies. If you want ublox_sara_n310 to be the default choice, then it should have lower priority than CONFIG_NET_SOCKETS_PRIORITY_DEFAULT, ideally use CONFIG_NET_SOCKETS_OFFLOAD_PRIORITY which has lower prioirty by default (lower priority == earlier processing).

Optionally, if you want the native socket implementation to remain the default choice, you can enable CONFIG_NET_SOCKETS_OFFLOAD_DISPATCHER

Replies: 4 comments 9 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
9 replies
@soerlemans
Comment options

@rlubos
Comment options

rlubos Jun 2, 2022
Collaborator

@soerlemans
Comment options

@rlubos
Comment options

rlubos Jun 3, 2022
Collaborator

@alissa-maria
Comment options

Answer selected by alissa-maria
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug area: Networking area: Modem area: Offloading
4 participants
Converted from issue

This discussion was converted from issue #46140 on June 01, 2022 09:14.