[openipc-ai]

Problem

On hi3516cv200 and hi3518ev200, the WebUI's Wi-Fi page finds no networks with a cfg80211 dongle, even after the camera has joined one. A reporter on a hi3518ev200 with an MT7601U sees this while wlan0 is associated and has an address (#2675).

The page tries two tools and neither can answer:

• wpa_cli needs a control socket. No wpa_supplicant runs before a network is configured, and the configuration wlan_conf writes has no ctrl_interface after one is.
• iwlist is in the image, but with CFG80211_WEXT off it cannot drive a cfg80211 driver.

This turns the option on in both generic configs of the family. It fixes both states with one change, and 51 board configs in this tree already have it on.

Hardware tested on

Not run on a camera yet. No lab board here has an MT7601U. The diagnosis comes from reading the page's scan script and the kernel config, not from a kernel with the option on.

The Baolian 11R6W25-HX20Y device in OpenIPC/builder has its own kernel config and gets the same line in OpenIPC/builder#224. The reporter of #2675 can confirm on that image, and I'll add the result here.

Evidence

The reporter's camera, associated, with the scan still empty in the WebUI:

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    inet 192.168.137.5/24 brd 192.168.137.255 scope global wlan0
kern.info kernel: wlan0: associated

The camera's iw is absent, and no iwlist output from a camera exists yet, before or after this change. To check on a built image:

iwlist wlan0 scan | grep ESSID

Change, from git diff:

-# CONFIG_CFG80211_WEXT is not set
+CONFIG_CFG80211_WEXT=y

ci-matrix.py --stdin builds hi3516cv200_lite, hi3516cv200_neo, hi3518ev200_lite and hi3518ev200_ultimate. All four pass.

Size, master's latest against this PR's build log (squashfs, cap 5120 KB on the two 8 MB lite boards):

hi3518ev200_lite   4874 KB -> 4884 KB
hi3516cv200_lite   5049 KB -> 5060 KB   (60 KB left, no headroom warning)
cfg80211.ko        230808 -> 257016 bytes uncompressed (hi3518ev200_lite against the Baolian build)

The kernel with the option on, in QEMU (-M hi3516cv200), from the OpenIPC/builder#224 build, which carries the same line. This shows the modules load, not that a scan works, because QEMU has no USB dongle:

~ # modprobe mt7601u; echo modprobe_rc=$?
usbcore: registered new interface driver mt7601u
modprobe_rc=0
~ # lsmod | grep -E "cfg80211|mac80211|mt7601u"
mt7601u                44407  0
mac80211              308191  1 mt7601u
cfg80211              213933  2 mt7601u,mac80211

Scope

• No kernel patches under general/package/all-patches/linux/ (those go to OpenIPC/linux)
• No files specific to a single retail camera model (those go to OpenIPC/builder)
• No probing or bring-up tooling (that goes to OpenIPC/ipctool)
• Nothing under general/overlay/ or in a shared load_<vendor> script hardcodes a value specific to my board
• Package sources come from an OpenIPC repository, and any version bump keeps at least the specificity of the pin it replaces (a new package should pin a full 40-character SHA)
• No LD_PRELOAD, and no binaries that cannot be rebuilt from source
• New code is selected by a defconfig, so CI actually builds it

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Enable iwlist scans for cfg80211 dongles on hi3516cv200-family boards

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Enable cfg80211’s WEXT compatibility in both generic kernel configs so iwlist can scan cfg80211
 dongles.
• Restore the WebUI’s existing scan fallback when wpa_cli has no usable control socket.

Diagram

graph TD
  WebUI["Wi-Fi page"] --> Iwlist["iwlist scan"] --> Wext["WEXT compatibility"] --> Cfg["cfg80211 module"] --> Dongle["Wi-Fi dongle"]
  Configs["Generic kernel configs"] --> Wext

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Make wpa_cli scanning available

• ➕ Could use the WebUI’s existing wpa_cli scan path without enabling kernel compatibility code.
• ➖ Requires a supplicant and control socket before configuration, plus changes to generated supplicant configuration after setup.

Recommendation: Enable CFG80211_WEXT as proposed: it addresses both configured and unconfigured states through the existing iwlist fallback with no userspace workflow change. Check image and module sizes, then seek on-device scan confirmation before treating the reported failure as verified fixed.

Files changed (2) +2 / -2

Bug fix (2) +2 / -2

hi3516cv200.generic.configEnable cfg80211 WEXT support for hi3516cv200 +1/-1

Enable cfg80211 WEXT support for hi3516cv200

• Sets CONFIG_CFG80211_WEXT=y in the hi3516cv200 generic kernel config. This permits iwlist to use the cfg80211 compatibility path for wireless scans.

br-ext-chip-hisilicon/board/hi3516cv200/hi3516cv200.generic.config

hi3518ev200.generic.configEnable cfg80211 WEXT support for hi3518ev200 +1/-1

Enable cfg80211 WEXT support for hi3518ev200

• Sets CONFIG_CFG80211_WEXT=y in the hi3518ev200 generic kernel config. This gives its iwlist scan fallback the same cfg80211 compatibility path.

br-ext-chip-hisilicon/board/hi3516cv200/hi3518ev200.generic.config

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Untested Wi-Fi change ships to cameras 📘 Rule violation ≡ Correctness

Description

The PR flips CONFIG_CFG80211_WEXT from off to on in both hi3516cv200 generic kernel configs, which
changes how cfg80211 drivers are driven and adds code to cfg80211.ko in every image built from
them. The PR description says "Not run on a camera yet" and that the diagnosis "comes from reading
the page's scan script and the kernel config, not from a kernel with the option on", so no
before/after iwlist wlan0 scan output from a board is provided. The gate requires that hardware
evidence whenever the diff can change camera behaviour, and this diff does, so the change is merged
without the proof the checklist asks for.

Code

br-ext-chip-hisilicon/board/hi3516cv200/hi3516cv200.generic.config[659]

+CONFIG_CFG80211_WEXT=y

Evidence

The PR description explicitly states it was not run on hardware, and the diff changes a kernel
option in both generic configs that alters what the firmware does on a camera. The required
before/after evidence from a real board is absent, so the honesty and evidence gate fails.

Rule 3: Hardware evidence is present and honest
br-ext-chip-hisilicon/board/hi3516cv200/hi3516cv200.generic.config[659-659]
br-ext-chip-hisilicon/board/hi3516cv200/hi3518ev200.generic.config[764-764]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PR enables `CONFIG_CFG80211_WEXT=y` in the generic hi3516cv200 kernel configs but the description states it has not been run on a camera. The change alters cfg80211 behaviour and kernel size in every image built from these configs, so it needs output from a real board.
## Fix Focus Areas
- br-ext-chip-hisilicon/board/hi3516cv200/hi3516cv200.generic.config[656-662]
- br-ext-chip-hisilicon/board/hi3516cv200/hi3518ev200.generic.config[761-767]
## Recommended Fix
Before merging, test on an hi3518ev200 with an MT7601U (or the reporter's #2675 setup). Capture `iwlist wlan0 scan | grep ESSID` output and the `cfg80211.ko` size before and after the change, add them to the PR description, and check the hardware boxes. If no board is available, state that plainly and mark the change as unverified rather than claiming the fix works.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can turn these tips off under Display > Comment parts

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗