From 0e5ba492cfbcf70ca0e2c955f4c238d230f53e75 Mon Sep 17 00:00:00 2001 From: Joseph <162703152+josephnef@users.noreply.github.com> Date: Sat, 30 May 2026 20:15:18 +0300 Subject: [PATCH] docs: update README chip-status table to reflect current state MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace the single "Status" column with a 2.4 GHz / 5 GHz split. - 8812AU: TX + RX on both bands (unchanged). - 8811AU: rides the 8812 code path (unchanged). - 8814AU: RX-only on both bands. TX submits succeed on the bulk pipe but nothing reaches the air — see issue #36. The previous "RX + flaky TX, works on fresh-chip runs" phrasing was incorrect: empirically TX is gated at every band, not flaky. - 8821AU: TX + RX at 2.4 GHz, RX-only at 5 GHz. 5 GHz TX needs the per-channel IQK calibration ported from upstream halrf_iqk_8821a_ce.c — see issue #59. Top-of-file summary blurb updated to match. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 20c658a..f95d31b 100644 --- a/README.md +++ b/README.md @@ -3,9 +3,9 @@ The Realtek 11ac driver that simply devours its competitors. Devourer is a userspace re-implementation of Realtek's RTL88xxAU Wi-Fi -driver (Jaguar family: RTL8812AU + RTL8821AU shipping, RTL8811AU -supported via the 8812 code path, RTL8814AU RX solid + TX validated on -fresh-chip runs), speaking to the chip directly through libusb. No +driver (Jaguar family: RTL8812AU shipping on both bands, RTL8821AU +shipping at 2.4 GHz, RTL8811AU supported via the 8812 code path, +RTL8814AU RX-only), speaking to the chip directly through libusb. No kernel module, no `rtl8812au` DKMS tree — just a C++20 static library (`WiFiDriver`) plus two demo executables for RX and TX. It is the OpenIPC project's driver of choice for long-range video links built on @@ -21,12 +21,12 @@ register-table layout, firmware-download plumbing, and family; chip-specific EEPROM handling, firmware blobs, and RF tables are layered on top. -| Part | RF / streams | Status | Notes | -| -------------- | --------------- | ------------- | ------------------------------------------- | -| **RTL8812AU** | 2T2R | Supported | VID/PID `0bda:8812`; reference part | -| **RTL8811AU** | 1T1R | Supported | 1T1R cut of 8812 silicon; rides 8812 code path with `RFType=RF_TYPE_1T1R` selected from `REG_SYS_CFG` bit 27 | -| **RTL8814AU** | 4T4R, 3-SS max | RX + flaky TX | VID/PID `0bda:8813`; 2-SS effective on USB-2; TX works on fresh-chip single-cell runs but degrades to `LIBUSB_ERROR_IO` after virsh USB passthrough cycles | -| **RTL8821AU** | 1T1R AC + BT | Supported | OEM-rebadged as TP-Link Archer T2U Plus (`2357:0120`) etc; Android hotplug works end-to-end | +| Part | RF / streams | 2.4 GHz | 5 GHz | Notes | +| -------------- | --------------- | ------------- | ------------- | ------------------------------------------- | +| **RTL8812AU** | 2T2R | TX + RX | TX + RX | VID/PID `0bda:8812`; reference part | +| **RTL8811AU** | 1T1R | TX + RX | TX + RX | 1T1R cut of 8812 silicon; rides 8812 code path with `RFType=RF_TYPE_1T1R` selected from `REG_SYS_CFG` bit 27 | +| **RTL8814AU** | 4T4R, 3-SS max | RX only | RX only | VID/PID `0bda:8813`; 2-SS effective on USB-2. TX submits succeed on the bulk pipe but nothing reaches the air at any band — see issue #36 | +| **RTL8821AU** | 1T1R AC + BT | TX + RX | RX only | OEM-rebadged as TP-Link Archer T2U Plus (`2357:0120`) etc; Android hotplug works end-to-end. 5 GHz TX needs the per-channel IQK calibration ported from upstream `halrf_iqk_8821a_ce.c` — see issue #59 | Successor families (`Jaguar2` / `Jaguar+` — 8812BU, 8822BU/BE, etc., and the later `Kestrel` 11ax generation) are **out of scope**: they share