[NEW FEATURE] Multiple kind of network

[nicolas-rabault]

Multiple kind of network

Based on #428 , the multi-phy feature will allow Luos engine to deal with multiple and different networks at the same time (WiFi, CAN, Robus, …), acting like a switch. This feature will allow to deal with multiple networks on your device, multiply data bandwidth, and break the frontier between your embedded networks and your cloud or computer applications.

To allow that :

• Reception context is saved in the phy side allowing parallel reception.
• Phy add/remove is managed the same way services are.
• Every phy have its own TX_job list (message to transmit to a target).
• The node is considered as a phy (this is the localhost transportation interface)
• Filtering is able to filter messages for any phy interface.
• RX messages are filtered to all phy and converted into phy TX_job if needed.
• No more dynamical size variability over time in messages allocation.

User point of view

This new version should not change anything on the service development side. A few API may be changed but services algorithm shouldn't change at all.
Users will have to add physical layers on the main.c the same way they are managing services (only by calling phy init).

Expected results

In the end of this project, we should have Luos services on a computer and multiple board able to exchange information and detect each other using serial communication over USB and Robus at the same time.
All services across all network should appear as a global unified architecture in the routing table.

Tasks :

• Manage phy instanciation and dynamical phy table management
• Deal with hardware flexible node_id listing
• Deal with hardware efficient RX
• Deal with hardware efficient TX
• Simplify msg_alloc by removing reallocation.
• Move msg_alloc tasks to phy structs
• Modify luos_tasks to become localhost TX_job list.
• Deal with filtering. node_id and service_id for each phy is indexed on the phy struct.