fpv: give the 8812eu its own gk7205v200 build

[openipc-ai]

#61 asks for 8812eu support on gk7205v200 FPV. #70 and the first version of this PR both tried to satisfy it by adding BR2_PACKAGE_RTL88X2EU_OPENIPC=y next to the existing BR2_PACKAGE_RTL8812AU_OPENIPC=y. CI built that and it does not fit:

- uImage:          [1988KB/2048KB]
- rootfs.squashfs: [5504KB/5120KB]
-- size exceeded by: 384KB
   headroom: kernel=59KB rootfs=-384KB

Two heavy kernel Wi-Fi drivers do not go in one 8M image. The driver itself is fine — 8812eu.ko links and installs — it is purely flash budget, and there is no 384KB of slack to find in a 5MB rootfs that was already at its cap.

The tree had already said so, and I misread it. Every defconfig here that ships both drivers is 16M: all the ssc338q, ssc30kq, ssc377qe and ssc378qe fpv/apfpv/rubyfpv targets. Every 8M one ships 8812au alone: gk7205v200/v210/v300 fpv and venc, hi3516ev200_fpv, hi3516ev300_fpv. The "missing" 8812eu on the Goke configs was never an oversight — it is what 8M allows.

What this does instead

gk7205v200_fpv_8812eu is gk7205v200_fpv with one line changed, the driver swapped rather than added:

-BR2_PACKAGE_RTL8812AU_OPENIPC=y
+BR2_PACKAGE_RTL88X2EU_OPENIPC=y

The existing gk7205v200_fpv is untouched, so nobody using an 8812au adapter is affected.

Nothing else needs to move for it

• Registration is automatic — the defconfig is the registration. --self-test passes at 108 devices, and the diff narrows to exactly the new target, so the build in this PR is the proof:

  ci-matrix: 1/108 devices (needs_build=True) --- narrowed to the affected devices
    gk7205v200_fpv_8812eu
  

• Excludes are resolved as ${OPENIPC_SOC_MODEL}_${OPENIPC_VARIANT}.list by firmware's general/scripts/rootfs_script.sh, and VARIANT stays "fpv", so this reuses gk7205v200_fpv.list. That list strips neither driver.
• Release assets do not collide. master.yml keys on the underscore count: gk7205v200_fpv has COMMON=1 and uploads the canonical openipc.gk7205v200-nor-fpv.tgz, while this one has COMMON=2 and is renamed to gk7205v200_fpv_8812eu-nor.tgz. Same for its sizes.json.

Only gk7205v200, which is what #61 asked for. The other four 8M FPV targets have the same constraint and could take the same treatment if anyone asks.

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

PR Summary by Qodo

Enable RTL88X2EU adapters on gk7205v200 FPV

✨ Enhancement ⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Enables RTL88X2EU driver support for gk7205v200 FPV firmware.
• Supports 8812EU adapters alongside existing 8812AU hardware.

High-Level Assessment

The targeted defconfig change is optimal: it adds the requested driver only to gk7205v200_fpv, avoids duplicate device definitions, and lets the existing build pipeline validate the 8 MB image-size constraint.

Files changed (1) +1 / -0

Other (1) +1 / -0

gk7205v200_fpv_defconfigEnable the RTL88X2EU wireless driver +1/-0

Enable the RTL88X2EU wireless driver

• Selects the RTL88X2EU OpenIPC package for gk7205v200 FPV firmware alongside the existing RTL8812AU driver. This supports adapters sold under the same names but containing different chipsets.

devices/common/br-ext-chip-goke/configs/gk7205v200_fpv_defconfig

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

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can ask Qodo to dismiss a finding you disagree with, with your reason on record

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗