linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Benoit Papillault <benoit.papillault@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Add HT IE to IBSS beacons and probe responses.
Date: Tue, 11 May 2010 12:48:12 +0200	[thread overview]
Message-ID: <1273574892.3669.54.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4BE49BDD.8010803@free.fr>

On Sat, 2010-05-08 at 01:01 +0200, Benoit Papillault wrote:

> > It would be helpful if you were to rebase over my patch that adds the
> > channel type tracking.
> 
> Your patches are now in wireless-testing, so I am doing it at the moment.

Thanks.

> >> +	if (channel_type != NL80211_CHAN_NO_HT&&
> >> +	    sband->ht_cap.ht_supported) {
> >
> > You shouldn't be able to get here with an HT channel but !ht_supported,
> > no? Or is that to support the case where you have HT only on one band?
> 
> Good point. I think there are several cases here :
> 
> - a non-HT STA is joining an HT IBSS (we need to check 802.11n-2009 to 
> see how it's supposed to be handled). In this case channel_type could be 
> ht40+ and ht_supported = false

Hmm, true.

> - an HT STA is joining a non-HT IBSS. It's clear in this case that no HT 
> IE should be sent, which is catched by (channel_type != 
> NL80211_CHAN_NO_HT) condition.

Right.

> Could we examine those cases in a follow up patch?

Well what do we actually need to do then?

> >> +}
> >> +
> >> +int ieee80211_add_ht_info(u8 **ppos,
> >> +			  struct ieee80211_supported_band *sband,
> >> +			  struct ieee80211_channel *channel,
> >> +			  enum nl80211_channel_type channel_type)
> >
> > what's wrong with ieee80211_add_ht_ie()
> 
> Seems it's close to what I'm doing, but not entirely the same. I will 
> read it. If applicable, should I move ieee80211_add_ht_ie to util.c (and 
> declaration to ieee80211_i.h) then ?

Yes.

Also I just noticed that there's a TODO item in rx.c when we receive an
HT frame from a peer we don't know about yet. Not sure what to do there,
but you'll need to look at it.

johannes


  reply	other threads:[~2010-05-11 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 22:36 [PATCH v2] cfg80211: Parse channel_type in NL80211_CMD_JOIN_IBSS Benoit Papillault
2010-05-05 22:36 ` [PATCH v2] mac80211: Add HT IE to IBSS beacons and probe responses Benoit Papillault
2010-05-06  6:40   ` Johannes Berg
2010-05-07 23:01     ` Benoit Papillault
2010-05-11 10:48       ` Johannes Berg [this message]
2010-05-12 21:02         ` Benoit Papillault
2010-05-13  0:47           ` Bruno Randolf
2010-05-13  7:09             ` Benoit Papillault
2010-05-14 13:58           ` Johannes Berg

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=1273574892.3669.54.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=benoit.papillault@free.fr \
    --cc=linux-wireless@vger.kernel.org \
    /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).