Unified Wi-Fi and Bluetooth branch test

This branch tests replacing the separate main and bluetooth branches with one driver and installer. The kernel driver, firmware, and DKMS configuration were already identical on both branches. This test unifies their installer, migration, diagnostics, packaging description, and documentation.

The expected architecture is:

aic_load_fw initializes every supported adapter and uploads firmware.
aic8800_fdrv handles Wi-Fi.
A combo adapter exposes a Bluetooth HCI USB interface after initialization; the standard Linux btusb driver binds through normal USB device matching.
A Wi-Fi-only adapter exposes no HCI interface and does not need btusb.
The retired custom aic_btusb module is never installed or used.

The installer deliberately does not force-load btusb and does not globally unblock Bluetooth through rfkill.

Install

git fetch origin
git switch test/unified-wifi-bt
git pull --ff-only
sudo ./install.sh
sudo reboot

Test a Wi-Fi-only adapter

Confirm that:

The Wi-Fi interface is created.
Scanning, association, DHCP, and real traffic work.
No aic_btusb module is loaded.
The absence of btusb or an HCI controller is treated as normal.

Test a Wi-Fi/Bluetooth combo adapter

Confirm that:

Wi-Fi scanning, association, DHCP, and real traffic work.
aic_load_fw uploads the firmware before the HCI interface is used.
The Bluetooth USB interface is bound to the standard btusb driver.
bluetoothctl can power on, scan, pair, and exchange real traffic.
No aic_btusb module, alias, soft dependency, or udev binding rule remains.

Collect results

git rev-parse --short HEAD
lsusb
lsusb -t
lsmod | grep -E 'aic|btusb|bluetooth'
iw dev
bluetoothctl list
sudo ./diagnose_bt.sh | tee unified-wifi-bt-diagnostic.log
sudo journalctl -k -b --no-pager | tee unified-wifi-bt-kernel.log

Please attach both logs and identify whether the tested adapter is Wi-Fi-only or a combo device.

Roll back during testing

git switch main
git pull --ff-only
sudo ./install.sh
sudo reboot

2.1 KiB Raw Blame History