From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jouni Malinen Date: Wed, 29 Dec 2010 08:52:29 +0200 Subject: [ath9k-devel] Progress on Ath9k HT support on Adhoc mode In-Reply-To: References: <4CF88076.6080105@gmail.com> <201012091336.19873.simon_alex@web.de> <5C6A1397A52B4FC1A5E85604FEA41D32@PatrickAsus> <14C05393AD794FD0A06B6BB332CC46AF@PatrickAsus> Message-ID: <1293605549.30342.8.camel@jm-desktop> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Tue, 2010-12-28 at 22:32 -0800, Mohammed Shafi wrote: > On Wed, Dec 29, 2010 at 11:40 AM, Robert Chan > wrote: > > So should I assume that the details here are "too updated" or are the modes > > above are only independently supported (but not able to work together such > > as IBSS + N + mesh)? The modes in that table should be considered independent and support for 802.11n in the table should really be read as at least one of the modes supporting it, not all modes supporting it. So no, that does not mean that either IBSS or mesh would support 802.11n (AP and station modes do). > I think 'mesh mode' also handled in mac80211 , if mesh mode is > supported with 11n then ibss(which is a sub-set ?) should have 11n > support. Mesh and IBSS are independent modes and both will need to be independently addressed for 802.11n support. In addition, both of them have protocol limitations on which 802.11n HT features can be supported. Finally, HT support for either mode is not yet complete in mac80211 and as such, cannot be complete with ath9k either. - Jouni