rt2x00: Only set the TBCN flag when the interface is configured to send beacons.
authorIvo van Doorn <ivdoorn@gmail.com>
Sun, 6 Jan 2008 22:38:58 +0000 (23:38 +0100)
committerDavid S. Miller <davem@davemloft.net>
Mon, 28 Jan 2008 23:09:23 +0000 (15:09 -0800)
commit3867705bb773818b39e0ca8d02ccb71fb4d2ffb8
tree87c320f5f062125d5bea56e2148c9c74ec175383
parent1230cb83f46731ca4eaa57c480788ed3c9d05935
rt2x00: Only set the TBCN flag when the interface is configured to send beacons.

These flags used to be fixed to one in rt2500pci_config_type, which
caused the beacon timer interrupt to fire. This would lead to
rt2x00lib_beacondone adding work which called
rt2x00lib_beacondone_scheduled which called ieee80211_beacon_get which
printed an error about not having any beacon data.

With this patch, these interrupts are only generated when the interface
is configured to send beacons.

Signed-off-by: Matthijs Kooijman <matthijs@stdin.nl>
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/rt2x00/rt2400pci.c
drivers/net/wireless/rt2x00/rt2500pci.c
drivers/net/wireless/rt2x00/rt2500usb.c
drivers/net/wireless/rt2x00/rt61pci.c
drivers/net/wireless/rt2x00/rt73usb.c