// Step 3: Wait for NL80211_CMD_SCAN_ABORTED or NL80211_CMD_NEW_SCAN_RESULTS while (!scan_complete) { pthread_cond_wait(&scan_cond, &scan_mutex); } pthread_mutex_unlock(&scan_mutex);
They wrote a Python daemon, qca-bridge-d , that listened to Redis (where RDK-B caches its data model), translated Device.WiFi.SSID.1.Enable into dbus-send --system --dest=org.qualcomm.wpa /org/qualcomm/wpa/1 org.qualcomm.wpa.SetEnable boolean:true . rdk-b integration with non-native wi-fi socs
, the log screamed.
Lead firmware engineer, Mira Khoury, stared at the boot log. The Broadcom SoC, running the full RDK-B suite (CcspCommon, MTA, WebUI, TR-069), had just enumerated the PCIe bus. It saw the QCA chip. It even loaded the vendor's proprietary wlan.ko driver. But the RDK-B middleware, specifically the CcspWifiSsp (Service Subsystem for Wi-Fi), was throwing a tantrum. The Broadcom SoC, running the full RDK-B suite
// 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); But the RDK-B middleware