docs: add DC/DW support to legacy MCU1 profile

README.md

@@ -1,15 +1,17 @@
-# AIC8800D80 Linux Driver
-This driver is for the AIC8800D80 chipset, supported by devices such as the Tenda U11 and AX913B.
+# AIC8800 Linux Driver
+This driver supports AIC8800-family chipsets used by devices such as the Tenda U11, AX913B, and TP-Link Archer TX1U Nano.
 
 > **Legacy MCU revision 1 branch:** You are viewing `legacy-mcu1`. This branch
-> is only for AIC8800D80 devices that report `chip_id=7, chip_mcu_id=1` and fail
-> the current V5 FMAC upload at `0x170400`. It uses the complete matched Radxa
-> SDK V3 D80 firmware and loader profile validated in
-> [issue #58](https://github.com/shenmintao/aic8800d80/issues/58). Use
+> is only for AIC8800D80 or AIC8800DC/DW devices that report
+> `chip_id=7, chip_mcu_id=1`. It provides complete matched V3 firmware and
+> loader profiles for the D80 upload-limit failure validated in
+> [issue #58](https://github.com/shenmintao/aic8800d80/issues/58) and the DC/DW
+> V5 main-application timeout validated in
+> [issue #71](https://github.com/shenmintao/aic8800d80/issues/71). Use
 > [`main`](https://github.com/shenmintao/aic8800d80/tree/main) for newer
 > `chip_mcu_id=0` hardware or when the MCU revision is unknown. See the
-> [legacy MCU1 support notes](tests/issue58-mcu1-legacy-fw/README.md) before
-> installing.
+> [D80](tests/issue58-mcu1-legacy-fw/README.md) and
+> [DC/DW](tests/issue71-mcu1-v3-profile/README.md) support notes before installing.
 
 Added support for devices with Vendor ID 368B (tested).
 

tests/issue58-mcu1-legacy-fw/README.md

@@ -37,7 +37,9 @@ identified in [PR #35](https://github.com/shenmintao/aic8800d80/pull/35).
 Bluetooth continues to use the kernel's standard `btusb` driver; this branch
 does not contain or install `aic_btusb`.
 
-Firmware and loader paths for D80N, D80X2, DC, and other variants are unchanged.
+Firmware and loader paths for D80N, D80X2, and other variants are unchanged.
+The same branch now also carries the separately validated legacy DC/DW profile
+documented in the [issue #71 support notes](../issue71-mcu1-v3-profile/README.md).
 
 ## Hardware validation
 

tests/issue71-mcu1-v3-profile/README.md

@@ -1,10 +1,10 @@
-# Issue #71: complete MCU1 V3 DC/DW profile
+# AIC8800DC/DW legacy MCU revision 1 support
 
-This branch is the second test for
+The `legacy-mcu1` branch is the maintained compatibility profile for older
+AIC8800DC/DW devices tracked in
 [issue #71](https://github.com/shenmintao/aic8800d80/issues/71). It follows the
-same method as the successful issue #58 legacy MCU1 branch: use a complete,
-matched legacy firmware and loader profile rather than mixing firmware
-generations.
+same method as the successful issue #58 D80 profile: use a complete, matched
+legacy firmware and loader rather than mixing firmware generations.
 
 The branch keeps the current USB transport, cfg80211 integration, device IDs,
 DKMS installer, and modern-kernel compatibility. For AIC8800DC/DW it restores
@@ -12,16 +12,17 @@ the complete firmware directory and matching loader from immediately before
 SDK V5 commit `d66e5cb`. That loader includes the MCU1 cache fix and flash DPD
 validation used by the reporter's previously working driver.
 
-The first issue #71 test proved that the DPD result stored in flash is valid,
-but the V5 main application still timed out at `DBG_START_APP_REQ`. This branch
-tests the complete profile that produced the reporter's known-good firmware
-hashes.
+The first issue #71 test proved that the DPD result stored in flash was valid,
+but the V5 main application still timed out at `DBG_START_APP_REQ`. Test commit
+[`d999571`](https://github.com/shenmintao/aic8800d80/commit/d999571) restored the
+complete profile matching the reporter's known-good firmware hashes, after
+which the reporter confirmed that the TX1U Nano worked.
 
 ## Install
 
 ```bash
 git fetch origin
-git switch test/issue-71-mcu1-v3-profile
+git switch legacy-mcu1
 git pull --ff-only
 sudo ./install.sh
 sudo poweroff
@@ -61,10 +62,8 @@ New interface create wlan0
 There should be no command timeout, `err_lmac_reqs`, or failed USB probe after
 the main application starts.
 
-If the interface is created, also test scanning, association, DHCP, gateway
-and Internet reachability, at least 10 minutes of real traffic, and one USB
-unplug/replug cycle. Attach `issue71-v3-profile.log` whether the result passes
-or fails.
+Confirm scanning, association, DHCP, gateway and Internet reachability, real
+traffic, and clean initialization after a USB unplug/replug cycle.
 
 ## Roll back