GK7202V300 (GK-W7): no wlan0 — USB Wi-Fi 8065:6000; Lite NOR 8M ships mt7601u only

[bneigher]

Hardware

• SoC: GOKE GK7202V300 (board GK-W7 style, 8MB NOR XMC XM25QH64 / XM25QH64CHIQ, JEDEC 0x20 0x40 0x17).
• Wi-Fi: USB device 8065:6000 (appears on USB bus 001 as single HS device). No separate PCIe/SPI Wi-Fi visible.
• Ethernet: No PHY on this board (femac … connect to PHY failed in dmesg — expected).

Firmware

• OpenIPC “Lite” NOR 8M full image for GK7202V300 (kernel Linux 4.9.37, build 2026-04-22, U-Boot 2016.11-gd5c37e8-dirty Jan 2025).
• Video: sensor=gc2053 (via fw_setenv), Majestic runs; sensor pipeline OK.

Problem

• After boot: ip link only shows lo — no wlan0 (or any wireless iface).
• lsusb: Bus 001 Device 002: ID 8065:6000
• Wireless modules under /lib/modules/.../drivers/net/wireless/: only mediatek/mt7601u/mt7601u.ko (+ mac80211). Firmware tree has mt7601u.bin only.
• modprobe mt7601u loads the driver (usbcore: registered new interface driver mt7601u) but no USB bind / no netdev — 8065:6000 is not MT7601U.

Stock firmware note (for donor/driver hints)

• On vendor firmware, Wi-Fi was associated with SSV6x5x stack (ssv6x5x.ko, p2p0, nl80211 / vendor config paths). Unclear if 8065:6000 is exactly SSV without full lsusb -v strings.

Ask

1. Is there a donor camera / board profile or different OpenIPC build (still NOR 8M) that includes a driver/firmware set matching USB 8065:6000 for GK7202V300?
2. If not, what is the recommended path: custom kernel module from vendor tree, Ultimate-only package, or issue + PR to add VID:PID 8065:6000 support — and which driver name should we target?

Attachments / evidence

• lsusb / ip link / find … wireless …*.ko / dmesg (no wlan probe lines for this chip) available if useful.

Thank you.

[bneigher]

Additional data: vendor GK-W7 / gc2053_dvp bring-up

Board / product: GK-W7 style, stock product string ipc533331a-W7-gc2053dvp-f8.

Stock sensor.conf: sensortype=gc2053_dvp (from vendor rootfs extract).

Vendor /komod/load logic (relevant excerpt): for gc2053_dvp they do not pass gc2053 as SNS_TYPE0 into the same path as the generic case; they force SNS_TYPE0=soi_f37 with a note in-tree about W7 FFC / clock (24 MHz vs 27 MHz):

SNESORTYPE=`cat /etc/ipcamera/sensor.conf | cut -d= -f2`
#### W7: gc2053_dvp — vendor comment about long FFC, 24 MHz vs 27 MHz for image
if [ $SNESORTYPE == "soih62_mipi" ] || [ $SNESORTYPE == "gc2053_dvp" ]; then
  SNS_TYPE0=soi_f37
else
  SNS_TYPE0=gc2053
fi
if [ $SNESORTYPE == "gc2083" ] || [ $SNESORTYPE == "gc2053" ] || [ $SNESORTYPE == "gc2093" ] || [ $SNESORTYPE == "soih62_mipi" ] ; then
  YUV_TYPE0=0
else
  YUV_TYPE0=1
fi

OpenIPC (Lite NOR 8M GK7202V300): only /etc/sensors/gc2053_i2c_1080p.ini is present (MIPI-oriented). After a clean Majestic restart we see a flood of gc2053_write_register → I2C_WRITE error and Timeout from venc channel 0; /mjpeg may return HTTP 200 but /image.jpg times out.

Question for maintainers: could GK7202V300 + GK-W7 + gc2053_dvp need a dedicated sensor profile / board option (or sysconfig sensor alias matching vendor soi_f37 / 24 MHz W7 behavior) instead of the generic gc2053_i2c_1080p.ini?

Happy to attach longer logs or full vendor script paths if useful.