The standardized C interface (APIs) that the middleware calls to execute hardware-level actions.
RDK-B utilizes a modular, layered architecture to achieve "router disaggregation," separating high-level applications from the underlying hardware. rdk-b integration with non-native wi-fi socs
Handles broadband management, including TR-181 data models, TR-069, and persistent storage. The standardized C interface (APIs) that the middleware
// libHalBridge: Translating Broadcom-style sync calls to nl80211 async int WIFI_HAL_TriggerScan_Shim(char *interface, int freq_list[]) { // Step 1: Convert RDK-B params to nl80211 scan request struct nl_msg *msg = nl80211_cmd_alloc(interface, NL80211_CMD_TRIGGER_SCAN); nla_put_u32(msg, NL80211_ATTR_SCAN_FLAGS, NL80211_SCAN_FLAG_AP); // Step 2: Send async, but block using a conditional variable pthread_mutex_lock(&scan_mutex); scan_complete = 0; nl80211_send(msg); // Step 2: Send async
// Update the RD-K configuration file to include the non-native Wi-Fi SoC settings rdk_config_t config = { .wifi_soc = "non_native_wifi_soc", .wifi_driver = "wifi_driver", }; rdk_configure(&config);
The critical "gluing layer." It defines a standard set of APIs that high-level RDK components use to communicate with the hardware, regardless of the vendor. The Challenge of Non-Native Integration rdkcentral/OneWifi - GitHub
Acts as the central management system for Wi-Fi parameters, client steering, and telemetry.