Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)
維護者通常 1 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 42/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- c
研究方向
Start with tests/fast_bw_rxcheck.cpp and compare the 20 MHz to 10 MHz FastSetBandwidth path described here with the full SetMonitorChannel path. Reproduce the intermittent near-zero hit count using the stated RTL8812BU receiver and RTL8812CU transmitter setup. The issue is resolved when the cause is identified and the fast switch reliably decodes the partner during the narrowband window.
由索引模型根據 Issue 內容生成。
描述
One item left open by #584, which fixes the 8822B fast bandwidth paths but does not touch this.
The fast 20 MHz -> narrowband switch sometimes decodes nothing
tests/fast_bw_rxcheck.cpp on an RTL8812BU (0bda:b812, USB 2, channel 36), with an RTL8812CU (0bda:c812) transmitting 10 MHz narrowband (DEVOURER_NB_BW=10). The RX starts at 20 MHz, toggles to 10 MHz with FastSetBandwidth, and should decode the partner only in that window.
| build | runs with 0 or 1 hits in the narrowband window | healthy runs |
|---|---|---|
master 0761c60c |
1 of 6 | 5 of 6, ~1800 hits each |
| #584 | 4 of 9 | 5 of 9, ~1800 hits each |
Each run is a fresh RX bring-up; the transmitter stayed up across runs. The fast_set_bandwidth 20 -> narrowband branch is identical on the two builds for a toggle without a hop, and the two rates cannot be told apart at these counts, so this is treated as pre-existing.
Not investigated
- Whether the RF18 edge in that branch is itself unreliable, the way the missing edge on the return was (#584 measured 3 of 6 deaf there before adding it).
- Whether the transmitter is at fault. It was a build from 9 November, and a Jaguar3 part; a different narrowband partner would separate the two.
- Whether the full path (
SetMonitorChannelto 10 MHz) shows the same rate. If it does not, the difference between the two paths is the lead. - 5 MHz, and 2.4 GHz.
A run counts as failed here when the narrowband window has at most 1 hit against ~1800 in a healthy run; nothing in between was seen.
- 主要語言
- 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 天內回覆
-
難度 5/5 一週以上 新手友好度 12/100
OpenIPC/devourer#579 · 1 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 5/5 一週以上 新手友好度 12/100
維護者通常 1 天內回覆
-
enhancement
難度 5/5 一週以上 新手友好度 8/100
維護者通常 1 天內回覆
-
M6 test realism — a moving-UE handover bench (conducted path-loss matrix, then an over-the-air walk)未關閉enhancement
難度 5/5 一週以上 新手友好度 25/100
OpenIPC/devourer#563 · 1 則留言 ·
維護者通常 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 天內回覆