Summary
The bsp-duchamp-u-oss branch (Poco X6 Pro / Redmi Turbo 3, MT6897) is missing WiFi chip source
for the device's actual on-die WiFi silicon (chip ID 0x7961, "soc7_0"), which prevents building a
working wlan_drv_gen4m_6897 module from this public source alone.
Details
The device's stock firmware reports:
ro.hardware.wlan.chip: mt6637
vendor.connsys.wifi.adie.chipid: 0x6637
ro.vendor.wlan.gen: gen4m_6897
- Firmware string:
WIFI_RAM_CODE_soc7_0-...
This corresponds to MediaTek's "soc7_0" chip generation (chip_id 0x7961), which is a distinct,
standalone driver implementation (register base 0x830c0000, its own descriptor format, ~2700
lines in soc7_0.c) — not a variant of the existing chips/connac2x2/connac2x2.c in this branch
(which is chip_id 0x0001, an older/different part with a v1 descriptor path).
gen4-mt79xx/chips/ on bsp-duchamp-u-oss only goes up to soc5_0. No soc7_0/ directory
exists, and gen4-mt79xx/Makefile has no findstring 7_0 / SOC7_0 build block.
Confirmed present elsewhere in this same repo
chips/soc7_0/ (and the matching include/chips/coda/soc7_0/ headers) exist on other branches
of this repo, e.g. bsp-rodin-v-oss. This suggests the omission on bsp-duchamp-u-oss is likely
an incomplete/stale OSS drop rather than an intentional exclusion, since the same silicon
generation is already public elsewhere in this org.
Also checked (for completeness)
- Independently verified against
oppo-source/android_kernel_modules_and_devicetree_oppo_mt6897
(also MT6897) — same gap, tops out at soc5_0 there too, consistent with this being a genuine
source-completeness issue rather than something device-specific to duchamp.
Ask
Could the soc7_0 chip source (and corresponding gen4-mt79xx/Makefile build wiring) be added to
bsp-duchamp-u-oss, matching what's already public on other branches like bsp-rodin-v-oss?
Happy to provide more detail (build logs, diffs) if useful.
Summary
The
bsp-duchamp-u-ossbranch (Poco X6 Pro / Redmi Turbo 3, MT6897) is missing WiFi chip sourcefor the device's actual on-die WiFi silicon (chip ID 0x7961, "soc7_0"), which prevents building a
working
wlan_drv_gen4m_6897module from this public source alone.Details
The device's stock firmware reports:
ro.hardware.wlan.chip: mt6637vendor.connsys.wifi.adie.chipid: 0x6637ro.vendor.wlan.gen: gen4m_6897WIFI_RAM_CODE_soc7_0-...This corresponds to MediaTek's "soc7_0" chip generation (chip_id
0x7961), which is a distinct,standalone driver implementation (register base
0x830c0000, its own descriptor format, ~2700lines in
soc7_0.c) — not a variant of the existingchips/connac2x2/connac2x2.cin this branch(which is chip_id
0x0001, an older/different part with a v1 descriptor path).gen4-mt79xx/chips/onbsp-duchamp-u-ossonly goes up tosoc5_0. Nosoc7_0/directoryexists, and
gen4-mt79xx/Makefilehas nofindstring 7_0/SOC7_0build block.Confirmed present elsewhere in this same repo
chips/soc7_0/(and the matchinginclude/chips/coda/soc7_0/headers) exist on other branchesof this repo, e.g.
bsp-rodin-v-oss. This suggests the omission onbsp-duchamp-u-ossis likelyan incomplete/stale OSS drop rather than an intentional exclusion, since the same silicon
generation is already public elsewhere in this org.
Also checked (for completeness)
oppo-source/android_kernel_modules_and_devicetree_oppo_mt6897(also MT6897) — same gap, tops out at
soc5_0there too, consistent with this being a genuinesource-completeness issue rather than something device-specific to duchamp.
Ask
Could the
soc7_0chip source (and correspondinggen4-mt79xx/Makefilebuild wiring) be added tobsp-duchamp-u-oss, matching what's already public on other branches likebsp-rodin-v-oss?Happy to provide more detail (build logs, diffs) if useful.