RTL8822E: close all open quirks/unknowns and produce a definitive quirks doc
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- c, linux
调研方向
Start with docs/8822e-quirks.md as the stated deliverable, then read the referenced RadioManagementJaguar3.{h,cpp}, HalJaguar3.cpp, and RtlJaguar3Device.{h,cpp} alongside the existing tests and README bench row. Run tests/regress.py and the relevant tests/eu_*.sh and bench scripts on the specified hardware; the issue is done when the open quirks are investigated, constraints and reproducers are documented, and the README bench row is updated once #3 is understood.
由索引模型根据 Issue 内容生成。
描述
Goal
The RTL8822E family (WiFi-only RTL8812EU 0bda:a81a + BT-combo RTL8822EU 0bda:e822, chip-id 0x17, Jaguar3) carries several documented-but-not-root-caused quirks and untested areas. This issue tracks a systematic campaign to (a) root-cause the open ones, (b) confirm the ones we work around blindly, and (c) land a definitive docs/8822e-quirks.md so nothing about this chip is folklore.
Known quirks — root-caused vs OPEN
| # | Quirk | Status | Code |
|---|---|---|---|
| 1 | Path-B OFDM TXAGC (0x41e8) desenses RX — any nonzero write near-deafens the RX, value-independent, field-specific. Neutralized structurally (skip_path_b_ofdm_ref gated on _rx_wanted); cost = path-B OFDM TX pinned to table default in TX+RX. |
ROOT CAUSE OPEN — "suspected path-B TSSI/gain-stage asymmetry vs the kernel's" | RadioManagementJaguar3.{h,cpp} (apply_power_by_rate_8822e, wr(0x41e8,…)), RtlJaguar3Device.h (_rx_wanted) |
| 2 | 2.4 GHz RX-deaf without a 3-wire re-tune — BB-window RF writes don't push RF18/RXBB to the 2G analog front-end; needs the 0x1830[29]/0x4130[29] brackets. Fixed, but fragile (5 GHz survives on init defaults). |
fixed, needs validation | RadioManagementJaguar3.cpp:172 |
| 3 | 2.4 GHz TX throughput anomaly — bench ch6 = 8 Mbps vs ch36 = 51 / ch149 = 47 (~6× low on 2.4 GHz). | UNEXPLAINED | README bench row |
| 4 | OTP/efuse only reliably readable at init (burst mode + sw-power-cut, one-shot; probe refused post-bring-up by design). | by-design, document | HalJaguar3.cpp (cache_efuse_8822e, efuse_pwr_cut_8822e), RtlJaguar3Device.cpp:1068 |
| 5 | Retrofit RX is unreliable — DEVOURER_TX_WITH_RX must be set before InitWrite; post-hoc filter re-open + enable_rx_path is unreliable. |
known, document + test | RtlJaguar3Device.h:45 |
| 6 | IQK clears the 40 MHz TX_CCK_IND bit (hardware-observed on the 8812EU) — calibration-order fix-up. |
fixed, verify | RadioManagementJaguar3.h:204 |
| 7 | The BT-combo RTL8822EU (0bda:e822) is entirely untested — all EU validation to date is the WiFi-only 8812EU. Does the combo part need the coex runtime thread the way the CU does? |
UNKNOWN | Jaguar3Calibration.h:20, coex thread notes in CLAUDE.md |
Test matrix to close the gaps
- #1 (the big one): bisect devourer's TXAGC bring-up sequence against the vendor kernel's (
tests/eu_txagc_regdiff.sh+tests/decode_txagc.pyalready diff0x18e8/0x41e8). Determine whether a correct path-B TSSI/gain-stage setup lets0x41e8be programmed without desense — i.e. recover path-B OFDM TX power in TX+RX mode. Confirm/refute the TSSI-asymmetry hypothesis with RX-sensitivity (MDS) measurements as0x41e8and the path-B TSSI regs are swept. - #2: validate 2.4 GHz RX across every channel switch and bandwidth (20/40/80 + 5/10 narrowband), incl. 5↔2.4 GHz band hops (
tests/eu_rx_validate.sh), asserting the front-end actually re-tunes each time. - #3: root-cause the 2.4 GHz TX shortfall — PA bias (
efuse PPG_PABIAS_2G*), TXAGC reference, or the same 2G-front-end path as #2 on the TX side. SDR duty × PHY-rate on-air (tests/bench_onair.py), compared to the vendor driver. - #4/#5/#6: confirm behaviours and document the constraints with reproducers.
- #7: acquire an RTL8822EU (BT combo) and run the full matrix; determine the coex-thread requirement for the EU.
- Board variance: repeat on ≥2 different 8812EU/8822EU boards (efuse RFE-type / PA-bias layouts differ —
HalJaguar3.cpp:101handles rfe_type 21..24).
Full per-band × per-bandwidth × RX/TX/full-duplex matrix via tests/regress.py (EU rows already present) + the on-air/SDR benches.
Deliverable
docs/8822e-quirks.md — every confirmed behaviour, each quirk marked root-caused or worked-around, the residual costs (e.g. path-B TX power in TX+RX), and the reproducers. Update the README bench row once #3 is understood.
Hardware
Reference: LB-LINK BL-M8812EU2 (0bda:a81a, WiFi-only). Needed additionally: an RTL8822EU (BT combo, 0bda:e822) and a second 8812EU/8822EU board for variance. VM per tests/setup_vm.sh for the kernel-cross-validation cells.
- 主要语言
- C
- 星标
- 56
- 派生
- 29
- 平均合并
- 3 小时 43 分钟
- 30 天内合并 PR
- 75
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
OpenIPC/devourer 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)可能已有人在做 @josephnef 今天认领。 未关闭enhancement
难度 4/5 3-5 天 新手友好度 42/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 12/100
OpenIPC/devourer#579 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 8/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Needs-Triage
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 2 天内回复
-
issue: bug report
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
-
cross-platform fix-now
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
feature:index kind:crash status:confirmed triaged
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复