From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 28 Aug 2007 21:01:52 +0000 (-0400)
Subject: [MAC80211]: remove IEEE80211_HW_HOST_GEN_BEACON flag
X-Git-Tag: firefly_0821_release~26070^2~743
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=0ef6e49b75d0d64d5deab890c72d19fe86488f73;p=firefly-linux-kernel-4.4.55.git

[MAC80211]: remove IEEE80211_HW_HOST_GEN_BEACON flag

The flag is never checked because drivers can simply call
ieee80211_beacon_get() regardless of setting this flag.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Acked-by: Michael Wu <flamingice@sourmilk.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
---

diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 233444b46d9a..e635ca41a0df 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -463,14 +463,13 @@ struct ieee80211_hw {
 
 	/* TODO: frame_type 802.11/802.3, sw_encryption requirements */
 
-	/* Some wireless LAN chipsets generate beacons in the hardware/firmware
-	 * and others rely on host generated beacons. This option is used to
-	 * configure the upper layer IEEE 802.11 module to generate beacons.
-	 * The low-level driver can use ieee80211_beacon_get() to fetch the
-	 * next beacon frame. */
-#define IEEE80211_HW_HOST_GEN_BEACON (1<<0)
-
-	/* The device needs to be supplied with a beacon template only. */
+/* hole at 0 */
+
+	/*
+	 * The device only needs to be supplied with a beacon template.
+	 * If you need the host to generate each beacon then don't use
+	 * this flag and use ieee80211_beacon_get().
+	 */
 #define IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE (1<<1)
 
 	/* Some devices handle decryption internally and do not