Skip to content

rtl8811au support#22

Open
RomanLut wants to merge 1 commit into
OpenIPC:masterfrom
RomanLut:rtl8811au_support
Open

rtl8811au support#22
RomanLut wants to merge 1 commit into
OpenIPC:masterfrom
RomanLut:rtl8811au_support

Conversation

@RomanLut
Copy link
Copy Markdown

Attempt to add rtl8811au support.

Still no luck, waiting for hardware.

The missing parts were taken from https://github.com/svpcom/rtl8812au/tree/v5.2.20-rssi-fix-but-sometimes-crash

@josephnef
Copy link
Copy Markdown
Collaborator

Thanks for porting this — adding the 8821a HAL tree is exactly the missing piece for actual RTL8821AU dongles. Two coordination notes plus one logistics ask.

Scope / dispatch. The PID allow-list in RtlUsbAdapter::InitDvObj currently lumps real RTL8811AU PIDs (0bda:0811, 0bda:a811) into RtlChipType::RTL8821. Those are Jaguar silicon (CHIP_8812 with RFType=1T1R), not Jaguar2 — sending them through the 8821 HAL with the 8821 firmware blob shouldn't work. Suggest narrowing the table to genuinely-8821 SKUs (e.g. 2357:0120, 0bda:0820/0821/0823, the 8821-combo OEM IDs) and letting the existing 8812 path handle 8811AU. Even better long-term would be a SYS_CFG-based family check (IC-ID bits) so new SKU revs don't need a code patch — that's what upstream rtl8812au does.

Conflict with #21. I have a small PR open (#21) that touches the same lines in EepromManager::read_chip_version_8812a — it derives RFType from REG_SYS_CFG bit 27 (RF_TYPE_ID) so the already-present 1T1R BB/RF paths reach actual 8811AU dongles. Whichever lands first will force the other to rebase. Happy to coordinate — I think the two compose cleanly once #22's dispatch is narrowed:

Hardware / logistics. The reporter on #20 (BadPotato1007) has a TP-Link Archer T2U Plus (2357:0120) — that's already in your allow-list — and is up for testing #22, which would close the loop. Also: we'd like to keep one in the OpenIPC lab for regressions. Where did you source / where are you planning to source your test dongle from? Happy to order from the same place so we're testing against an identical SKU rev.

@RomanLut
Copy link
Copy Markdown
Author

Where did you source / where are you planning to source your test dongle from?

https://www.amazon.de/-/en/dp/B07P681N66?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
I hope correct chipset arrive. You may wait a few days untill I check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants