Suppost for rtl8811au chipset

[BadPotato1007]

Hey!
So I was wondering if this project will be supporting rtl8811au based chips aswell? The only difference is that the 8812 supports two mimo streams, and the 8811 nly supports 1, but otherwise both cards use the same drivers and are able perform all the same functions, ofc, given that the speed is a little bit slower

[josephnef]

Hey @BadPotato1007 — yes, your read is correct: 8811AU is the 1×1 cut of the same Jaguar silicon as 8812AU, and the 1T1R code paths were already present in the driver but unreachable because chip detection hardcoded RFType = 2T2R.

Opened #21 which derives RFType from REG_SYS_CFG bit 27 (RF_TYPE_ID) the way Realtek's upstream rtl8812au driver does, and also widens the demo's USB PID list to include the common 8811AU SKUs.

Would you mind testing on your hardware? A few things would help me close this out:

1. lsusb output for your dongle — we need to confirm it's an 8811AU (PIDs 0bda:0811, a811, b811, sometimes 8812) and not an 8811CU (0bda:c811 — different silicon, won't work with this driver no matter what we do; sellers often mislabel them).
2. Run WiFiDriverDemo after building Add RTL8811AU support via RF_TYPE_ID autodetect #21 and paste the log line that starts RF_Type is … — should read RF_Type is 0 TotalTxPath is 1 on an 8811AU.
3. Any 5 GHz association / scan oddities? A few upstream 8811AU issues trace back to RFE-Type / antenna-byte mis-reads from EFUSE; if you hit that, the log will tell us.

Thanks for the report.

[BadPotato1007]

Thanks for your reply! I shall definitely take some time out for this in a day or two! I was also wondering about a couple of rtl8821au cards that I have, it seems that the only difference between them is the fact that the 21 chip supports bluetooth aswell? Possible to add that?

…

On Mon, 18 May, 2026, 6:40 pm Joseph, ***@***.***> wrote: *josephnef* left a comment (OpenIPC/devourer#20) <#20 (comment)> Hey @BadPotato1007 <https://github.com/BadPotato1007> — yes, your read is correct: 8811AU is the 1×1 cut of the same Jaguar silicon as 8812AU, and the 1T1R code paths were already present in the driver but unreachable because chip detection hardcoded RFType = 2T2R. Opened #21 <#21> which derives RFType from REG_SYS_CFG bit 27 (RF_TYPE_ID) the way Realtek's upstream rtl8812au driver does, and also widens the demo's USB PID list to include the common 8811AU SKUs. Would you mind testing on your hardware? A few things would help me close this out: 1. lsusb output for your dongle — we need to confirm it's an 8811*AU* (PIDs 0bda:0811, a811, b811, sometimes 8812) and not an 8811*CU* ( 0bda:c811 — different silicon, won't work with this driver no matter what we do; sellers often mislabel them). 2. Run WiFiDriverDemo after building #21 <#21> and paste the log line that starts RF_Type is … — should read RF_Type is 0 TotalTxPath is 1 on an 8811AU. 3. Any 5 GHz association / scan oddities? A few upstream 8811AU issues trace back to RFE-Type / antenna-byte mis-reads from EFUSE; if you hit that, the log will tell us. Thanks for the report. — Reply to this email directly, view it on GitHub <#20?email_source=notifications&email_token=AQ5IHFUPXXR7GDEI5PZJT3T43MDUFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINBXG44TSNZQGM2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4477997034>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ5IHFUVSHX5LNQJAIOBCSD43MDUFAVCNFSM6AAAAACZCTJJCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINZXHE4TOMBTGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[josephnef]

Sure, take your time with the 8811AU test.

On 8821AU — afraid it isn't quite that close. Bluetooth is the smallest of the differences; 8821AU is separate silicon (Realtek's "Jaguar2" family), not a 1T1R cut of 8812/8811. Upstream rtl8812au ships them in the same kernel module but with two distinct HAL trees (hal/rtl8812a/ vs hal/rtl8821a/). Devourer currently only has the 8812a HAL — the 8821 power sequence (Hal8821APwrSeq.c), 8821 PHY/BB/RF init, and 8821 firmware blob all need porting, plus chip-detection has to learn to dispatch between CHIP_8812 and CHIP_8821. Roughly an order of magnitude more work than this PR.

Could you open a separate issue for 8821AU support so we can scope it on its own? That way we can keep this one focused on landing 8811AU once you've had a chance to test #21.

[BadPotato1007]

Sure, will do :)