Draft: introduce agent_ubus_event.c step 1

Signed-off-by: Janusz Dziedzic janusz.dziedzic@iopsys.eu

marked this merge request as draft

assigned to @anjancx

I think no functional changes there (yet) :)

Agent will communicate with following -

1. ieee1905 via "ieee1905.cmdu" prefixed messages over system bus (UBUS events).
2. events via "wifi.*" prefixed messages over system bus (UBUS events).
3. operations via "wifi.*" prefixed messages over system bus (UBUS methods)
4. user commands via "map.agent" prefixed messages (UBUS methods).
5. configuration

Hopefully, not missing any ;) We should build APIs around each of the above. As a first step, we can cleanly separate 1 and 2.

I think we should also parse wifimanager ubus results and put them in same structures libwifi return. Then we will have consistent results and at any time we could use wifimngr ubus calls or simple switch to libwifi lib - without other code changes ...

merged separately

closed