adrian 342a7804fb Add in some debugging code to check whether the current rate table has ... been bait-and-switched from the rate control code. This will avoid the panic that I saw and will avoid sending invalid rates (eg 11a/11g OFDM rates when in 11b, on 11b-only NICs (AR5211)) where the rate table is not "big". It also will point out situations where this occurs for the 11n NICs which will have sufficiently large rate tables that "invalid rix" doesn't occur. I'll try to follow this up with a commit that adds a current operating mode check. The "rix" is only relevant to the current operating mode and rate table. PR: kern/165475		2012-02-26 06:04:44 +00:00
..
amrr	Introduce TX aggregation and software TX queue management	2011-11-08 22:43:13 +00:00
onoe	Introduce TX aggregation and software TX queue management	2011-11-08 22:43:13 +00:00
sample	Add in some debugging code to check whether the current rate table has	2012-02-26 06:04:44 +00:00