linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Shafi <mshajakhan@atheros.com>
To: Jouni Malinen <j@w1.fi>
Cc: "Björn Smedman" <bjorn.smedman@venatech.se>,
	"Mohammed Shajakhan" <Mohammed.Shajakhan@Atheros.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Luis Rodriguez" <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH 1/1] ath9k: Update comments for not parsing DTIM period
Date: Wed, 9 Feb 2011 20:25:33 +0530	[thread overview]
Message-ID: <4D52AAE5.4050300@atheros.com> (raw)
In-Reply-To: <20110209143853.GA6519@jm.kir.nu>

On Wednesday 09 February 2011 08:08 PM, Jouni Malinen wrote:
> On Tue, Feb 08, 2011 at 10:22:39PM +0100, Björn Smedman wrote:
>    
>> On Mon, Feb 7, 2011 at 4:38 PM, Mohammed Shafi Shajakhan
>> <mshajakhan@atheros.com>  wrote:
>>      
>>> -        * Some times we dont parse dtim period from mac80211, in that case
>>> -        * use a default value
>>> +        * We don't parse dtim period from mac80211 during the driver
>>> +        * initialization as it breaks association with hidden-ssid
>>> +        * AP and it causes latency in roaming
>>>        
>    
>> I realize I'm not the perfect representative for the intended audience
>> but I don't understand that comment at all. The previous one made
>> sense to me, but the new one seems to refer to some logic somewhere
>> else. In ath_beacon_config() I expect AP/IBSS logic but the comment
>> seems to be about some special case for a STA vif associating with a
>> hidden access point, no? I don't understand that special case either
>> but that is more easily attributable to ignorance. :)
>>      
> While I agree that the proposed comment is quite confusing, this
> function is actually used even in station mode to set beacon timers for
> when to wake up for receiving beacon frames, etc. However, I don't see
> why this comment should really be here. In addition, this should really
> be fixed by updating DTIM period after the first Beacon frame is
> received. Forcing a wait for that Beacon frame is the one that causes
> the extra latency; I don't remember why exactly this would break
> hidden SSID case unless there is another bug somewhere.
>    
Jouni I had validate few times with our AP and it does broke assoc with 
hidden SSID AP.

thanks,
shafi

> ath9k does not need to know the DTIM period before association and the
> first call to this function may need to handle the 0 ->  1 safety check.
> This should then be followed by another call (likely new code in
> mac80211 needed for this) to update the timers after the DTIM period has
> been learned post-association.
>
>    

      reply	other threads:[~2011-02-09 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 15:38 [PATCH 1/1] ath9k: Update comments for not parsing DTIM period Mohammed Shafi Shajakhan
2011-02-08 21:22 ` Björn Smedman
2011-02-09  5:12   ` Mohammed Shafi
2011-02-09 14:38   ` Jouni Malinen
2011-02-09 14:55     ` Mohammed Shafi [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=4D52AAE5.4050300@atheros.com \
    --to=mshajakhan@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Mohammed.Shajakhan@Atheros.com \
    --cc=bjorn.smedman@venatech.se \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).