Wireless problems:

1) Quality values vary wildly or are absent
	- atmel doesn't return any quality data from scanned APs
	- ipw_2100 doesn't return _any_ quality data at all, either for
		current AP or for scanned APs
	- Different methods for almost every driver
		- Prism54 does a quality as a percentage
		- airo mixes use of absolute and relative values in dBm
		- Average and max quality levels for almost all drivers are artificial
			and don't come from the the card in any way
2) Frequency values vary wildly from iw_get_range
	- prism54 uses completely different exponent values than airo
	- airo, atmel, orinoco are the same
3) airo/prism54 seem to have problems with ip6 and cause panic
	- See bug in RH bugzilla about this
4) not all drivers have correct netlink support, if they even have it
	- orinoco is too twitchy, sends too many events (shouldn't send them
		during a scan for example)
	- atmel, airo, and others don't seem to have any netlink support
5) Not all drivers support wirless scanning
	- orinoco
6) Firmware issues
	- Cisco aironet firmware upload is quite inconsistent, fails with
		5.21 for example
7) Ethtool support for all drivers
8) Ad-Hoc mode support is quite flaky or absent from most drivers
	- prism54 "mgmt tx queue full" errors
	- madwifi resets bitrate to 0 when switching to ad-hoc
9) WPA support is lacking or just in-progress, needs much help
10) Drivers deal with hidden ESSIDs differently
	- ipw2x00 traps " " and runs of \0 and changes it to "<hidden>" in the driver,
		while other drivers just pass the string through

Importance:
1) All drivers _MUST_ support wireless scanning (*cough* orinoco *cough*)
2) WPA support
3) Consistent (and present) quality data among drivers, both for
	currently connected AP and for scanned APs
4) The ip6 panic issues
5) rtnetlink link notification for all drivers when
	they associate with an AP
6) Ad-Hoc mode support
7) Ethtool support
8) Cisco firmware issues