Files
openipc-builder/devices/common
OpenIPC AI teamandGitHub 5e2d58f644 fpv: give the 8812eu its own gk7205v200 build (#133)
#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

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 in a 5MB rootfs that was already at its cap.

The tree had already said so. Every defconfig here that ships both drivers is 16M: 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.

So this is a separate build. 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 on an 8812au adapter is affected.
It builds with room to spare -- rootfs 5024KB/5120KB, 96KB headroom.

Nothing else had to move for it:

  - Registration is automatic; the defconfig is the registration. --self-test passes at
    108 devices and the diff narrows to exactly this target, so its own build proved it.
  - Excludes resolve as ${OPENIPC_SOC_MODEL}_${OPENIPC_VARIANT}.list in firmware's
    rootfs_script.sh, and VARIANT stays "fpv", so it reuses gk7205v200_fpv.list. That
    list strips neither driver.
  - Release assets do not collide. master.yml keys on the underscore count:
    gk7205v200_fpv is COMMON=1 and uploads the canonical openipc.gk7205v200-nor-fpv.tgz,
    this one is 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.

Closes #70.
2026-08-27 21:21:47 +03:00
..