linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mabbas <mabbas@linux.intel.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	mabbas@linux.intel.com
Subject: Re: [patch 4/5] IEEE 802.11n management action frame data structures
Date: Wed, 04 Apr 2007 03:37:46 -0700	[thread overview]
Message-ID: <46137FFA.6080202@linux.intel.com> (raw)
In-Reply-To: <20070326164503.f276cd71.randy.dunlap@oracle.com>

modified patch at the end

Randy Dunlap wrote:
> On Mon, 26 Mar 2007 04:42:22 -0700 mohamed wrote:
>
>   
>>  
>> +struct ieee802_11_addba_param {
>> +	 __le16 reserved:1;
>> +	 __le16 backPolicy:1;
>> +	 __le16 tid:4;
>> +	 __le16 bufSize:10;
>> +} __attribute__ ((packed));
>> +
>> +struct ieee80211_delba_param {
>> +	 __le16 reserved:11;
>> +	 __le16 intiator:1;
>> +	 __le16 tid:4;
>> +}__attribute__ ((packed));
>>     
>
> These bitfields are all local to one machine, not transported
> across a network to systems where the bitfields may be represented
> differently?
>
>
>   


Add draft IEEE 802.11n management action frame data structures and constants

Several Action frame format are defined to support IEEE 802.11n features.
This patch add the data structure for Block Ack management action frame.

Signed-off-by: Mohamed Abbas <mabbas@linux.intel.com>

diff --git a/include/linux/ieee80211.h b/include/linux/ieee80211.h
index 6bf824b..6d2c20e 100644
--- a/include/linux/ieee80211.h
+++ b/include/linux/ieee80211.h
@@ -201,6 +201,25 @@ struct ieee80211_mgmt {
 					__u8 new_chan;
 					__u8 switch_count;
 				} __attribute__((packed)) chan_switch;
+				struct{
+					u8 action_code;
+					u8 dialog_token;
+					__le16 capab;
+					__le16 timeout;
+					__le16 start_seq_num;
+				} __attribute__((packed)) addba_req;
+				struct{
+					u8 action_code;
+					u8 dialog_token;
+					__le16 status;
+					__le16 capab;
+					__le16 timeout;
+				} __attribute__((packed)) addba_resp;
+				struct{
+					u8 action_code;	
+					__le16 params;
+					__le16 reason_code;
+				}__attribute__((packed)) delba;
 			} u;
 		} __attribute__ ((packed)) action;
 	} u;
@@ -268,6 +287,8 @@ enum ieee80211_statuscode {
 	/* 802.11g */
 	WLAN_STATUS_ASSOC_DENIED_NOSHORTTIME = 25,
 	WLAN_STATUS_ASSOC_DENIED_NODSSSOFDM = 26,
+	/* 802.11e */
+	WLAN_STATUS_REQUEST_DECLINED = 37,
 	/* 802.11i */
 	WLAN_STATUS_INVALID_IE = 40,
 	WLAN_STATUS_INVALID_GROUP_CIPHER = 41,
@@ -309,6 +330,23 @@ enum ieee80211_reasoncode {
 };
 
 
+/* Category Code */
+enum ieee80211_category {
+	WLAN_CATEGORY_SPECTRUM_MGMT = 0,
+	WLAN_CATEGORY_QOS = 1,
+	WLAN_CATEGORY_DLS = 2,
+	WLAN_CATEGORY_BACK = 3,
+	WLAN_CATEGORY_WMM = 17,
+};
+
+
+/* BACK Action Code */
+enum ieee80211_back_actioncode {
+	WLAN_ACTION_ADDBA_REQ = 0,
+	WLAN_ACTION_ADDBA_RESP = 1,
+	WLAN_ACTION_DELBA = 2,
+};
+
 /* Information Element IDs */
 enum ieee80211_eid {
 	WLAN_EID_SSID = 0,

      parent reply	other threads:[~2007-04-03 22:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 11:42 [patch 4/5] IEEE 802.11n management action frame data structures mohamed
2007-03-26 23:45 ` Randy Dunlap
2007-03-28 19:12   ` Johannes Berg
2007-04-04 10:37   ` mabbas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46137FFA.6080202@linux.intel.com \
    --to=mabbas@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=randy.dunlap@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).