adrian 04e79987ba Add some debugging and forcing of the BAW to match what the current
tracked BAW actually is.

The net80211 code that completes a BAR will set tid->txa_start (the
BAW start) to whatever value was called when sending the BAR.
Now, in case there's bugs in my driver code that cause the BAW
to slip along, we should make sure that the new BAW we start
at is actually what we currently have it at, not what we've sent.

This totally breaks the specification and so this stays a printf().
If it happens then I need to know and fix it.

Whilst here, add some debugging updates:

* add TID logging to places where it's useful;
* use SEQNO().
2014-04-08 07:14:14 +00:00
..
2014-04-08 04:05:04 +00:00
2014-04-08 04:05:04 +00:00
2014-04-07 20:44:00 +00:00
2014-03-31 16:37:41 +00:00
2014-04-05 22:43:18 +00:00
2014-04-07 22:37:13 +00:00
2013-11-29 20:14:26 +00:00
2014-03-14 02:58:48 +00:00
2014-03-14 06:29:43 +00:00
2014-04-08 01:54:50 +00:00
2014-04-07 01:55:53 +00:00
2014-04-07 07:06:13 +00:00
2014-04-07 18:10:49 +00:00
2014-02-06 13:28:06 +00:00
2014-04-05 22:43:18 +00:00
2014-04-05 22:43:18 +00:00
2014-03-14 06:29:43 +00:00