40 MHz / 80 MHz coverage left open by #352: 8814AU, 8821AU, Jaguar2 RX, 80 MHz, other channels

Open
#554 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
34/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c

Research direction

Start with tests/bw40_pair_onair.sh and docs/vht-on-2g4.md, then review the existing Jaguar2 40 MHz transmit test and the rtw_get_center_ch handling referenced in the issue. The issue calls for measurements across additional chips, receive paths, bandwidths and channels; 80 MHz coverage also needs new cells and rates. Done means recording those measurements with per-leg 20 MHz controls and peer power sweeps.

Written by the indexing model from the issue text.

Description

enhancement

What is left unmeasured after #352

#352 (Jaguar1 40 MHz dead both ways) closed on 2026-11-09: the cause was the HT40 centre-channel tune fixed in #500, verified on an RTL8812AU against an RTL8852CU with tests/bw40_pair_onair.sh (branch bw40-352-verify). That verification covered exactly one die, one channel and one width. These cells are still open:

  • RTL8814AU and RTL8821AU at 40 MHz. Both go through the same rtw_get_center_ch rule as the 8812AU but neither has been measured (noted as unverified in #500 as well). The 8814AU needs the pinned-kernel VM for any vendor-driver control and is judged by its devourer-TX cells only.
  • Jaguar2 DEVOURER_BW=40 receive path. The #352 body reports ad-hoc runs with an 8822BU receiver reading zero at both primary-channel offsets. Jaguar2 TX at 40 MHz is validated by tests/jaguar2_tx_bw40.sh against a kernel sniffer; the devourer receive side at 40 MHz has no record. docs/vht-on-2g4.md no longer claims it is dead, only that it is unmeasured.
  • 80 MHz on Jaguar1 and Jaguar2, both directions, with the same control structure (a 20 MHz control per leg, the wide monitor shown hearing a narrow frame before it is asked to hear a wide one).
  • 2.4 GHz channels other than 6, including the grid-edge fits from #500 (ch1 HT40−, ch13 HT40+ were measured as transmitter only), and at least one 5 GHz channel at 40 MHz on the RX side.

How

tests/bw40_pair_onair.sh already takes --dut, --peer, --channel and --offset, so the first three items are runs, not code — except that the script has no 80 MHz cells yet (DEVOURER_BW=80 / DEVOURER_HOP_BW=80 and the /80 rates would need adding). Keep each leg's 20 MHz control and the peer power sweep (--peer-tx-pwr): on the same-host pair, peer MCS7 into the 8812AU read 0 % at the Kestrel's 20 dBm default and 90 % at 12 or 4 dBm, so a dense-constellation zero must be checked for near-field saturation before it is read as a width defect.

🤖 Generated with Claude Code

Dominant language
C
Stars
56
Forks
29
Avg merge
3h 43m
Merged PRs (30d)
75

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenIPC/devourer

All issues in OpenIPC/devourer

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.