Follow-ups left open by TxMode::no_agg / NOAGG (#459)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- c, linux
- 领域
- networking
调研方向
Start with tests/tx_no_agg_onair.sh for the measurement follow-ups; the issue names no code entry point for the driver ports. First determine which follow-up has suitable hardware and a reproducible bench, then read the prior results from #459. Done means delivering the requested measurements or a validated on-air port; several investigations remain open-ended and hardware-dependent.
由索引模型根据 Issue 内容生成。
描述
Left open by #459 (TxMode::no_agg / /NOAGG, merged as 87dde96). None blocks the feature as shipped; each is a measurement or a port the PR explicitly did not claim.
- Cost of occasional flagged frames. Only the every-other-frame worst case was measured (−47 % heard on the 8812EU, −60 % on the 8812CU). The realistic shape, one control frame every N aggregated video frames, is unmeasured.
tests/tx_no_agg_onair.shneeds a duty knob (flag every Nth frame) and a goodput reading, not a heard-fps one. - Mixed-width fold. The A-MPDU folds bandwidth as well as rate (a 20 MHz frame behind a 40 MHz opener airs at 40). The harness scores rate only. Add a width arm once the witness's
rx.seqcarries the decoded bandwidth. - Port to Jaguar1 / Jaguar2 / MT7612U.
tx_no_agg_okis false there by design. Jaguar2 shares the halmac descriptor (SET_TX_DESC_BKdword2[16]) so it is likely the same two writes; Jaguar1's 8812A descriptor and the MT7612U TXWI need their own look. Each needs an on-air arm, not a code-reading. - Cross-rate fold on the 8822C is deeper than on the 8822E (24 % vs 40 % of MCS0 frames kept their rate unflagged, same script, same knobs). Unexplained. Candidates: USB high-speed vs SuperSpeed feed depth, or a die difference in how many MPDUs the MAC waits to accumulate. One unit per die so far.
- 8812EU on the OpenIPC bench drops off the USB bus about 1 s after the TX bring-up reset (dmesg disconnect + re-enumerate; doctor HEALTHY on EFUSE/fw/RX). It ran a 60 s flood on 2026-09-26, so the bench changed. Rig, not code, but it is why the EU arm was not repeated here.
- 主要语言
- 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 天内回复