-
Notifications
You must be signed in to change notification settings - Fork 2.1k
RFC: use continuous interface identifiers #4852
Copy link
Copy link
Closed
Labels
Area: networkArea: NetworkingArea: NetworkingDiscussion: RFCThe issue/PR is used as a discussion starting point about the item of the issue/PRThe issue/PR is used as a discussion starting point about the item of the issue/PRState: won't fixState: The issue can not or will not be fixedState: The issue can not or will not be fixed
Description
The current solution using the driver's PID as an identifier for a network interface is a bit uninituitive and very dependent on the actual application. Since these PIDs are stored in an array anyway, using the array index for the identifier instead, would make the identifiers continuous and persistent over all applications on the same board (as long as we don't change the initialization code).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: networkArea: NetworkingArea: NetworkingDiscussion: RFCThe issue/PR is used as a discussion starting point about the item of the issue/PRThe issue/PR is used as a discussion starting point about the item of the issue/PRState: won't fixState: The issue can not or will not be fixedState: The issue can not or will not be fixed