summaryrefslogtreecommitdiffstats
path: root/drivers/net/bnx2x_main.c
diff options
context:
space:
mode:
authorReinette Chatre <reinette.chatre@intel.com>2009-04-21 10:55:47 -0700
committerJohn W. Linville <linville@tuxdriver.com>2009-04-21 16:43:34 -0400
commitd2ee9cd2e2bdfa2e5817142d6f044697066d3977 (patch)
tree9e4dec9fd4c009b8ce12f3bd1529ef2b455d3cc1 /drivers/net/bnx2x_main.c
parentc491bf1205485c83086bf4f2f26ca6598d48133a (diff)
downloadblackbird-op-linux-d2ee9cd2e2bdfa2e5817142d6f044697066d3977.tar.gz
blackbird-op-linux-d2ee9cd2e2bdfa2e5817142d6f044697066d3977.zip
iwlwifi: add debugging for TX path
When debugging TX issues it is helpful to know the seq nr of the frame being transmitted. The seq nr is printed as part of ucode's log informing us which frame is being processed. Having this information printed in driver log makes it easy to match activities between driver and firmware. Also make possible to print TX flags directly. These are already printed as part of entire TX command, but having it printed directly in cpu format makes it easier to look at. Signed-off-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/bnx2x_main.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud