Ok, there is a less evasive way. By using lsusb (and google in some cases). For example, with all my adapters:
Originally Posted by DonJoe
The first one is my laptop's internal card;
Bus 001 Device 002: ID 0bda:8197 Realtek Semiconductor Corp. RTL8187B Wireless Adapter
Bus 002 Device 004: ID 0ace:1215 ZyDAS ZD1211B 802.11g
Bus 002 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter
The second is my TP-Link WN422G V1.2;
The third is my Alfa AWUS036H (seems like RTL8187 = RTL8187L);
And the last is my TP-Link WN321G (RT73).
In case of doubt, you can also use the codes in red (vendorID:ProductID) with google, it should tell you what's the chipset.
You can also use Airdriver-ng, as follows:
Will not be as accurate as lsusb, but will give you an idea of what drivers are being used with your adapters (when the drivers are installed/supported, obviously). Seems like BT is loading two drivers (Ralink) for my TP-Link WN321G... Well, as long as it works, fine by me
root@bt:~# airdriver-ng loaded
Found following stacks loaded (as module):
Found following drivers loaded (as module):
27. Ralink rt2570 (rt2x00) - mac80211
33. Ralink rt73 (rt2x00) - mac80211
36. Realtek rtl8187 - mac80211
41. ZyDAS 1211rw - IEEE80211 Softmac
Hope it helps.