From: Joerg Albert <jal2@gmx.de>
To: Christian Lamparter <chunkeey@web.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ar9170: cleanup of bss_info_changed and beacon config
Date: Wed, 05 Aug 2009 21:05:09 +0200 [thread overview]
Message-ID: <4A79D7E5.1080604@gmx.de> (raw)
In-Reply-To: <200908050404.47371.chunkeey@web.de>
On 08/05/2009 04:04 AM, Christian Lamparter wrote:
> no signed/cc here?
oops, forgot it. Seems like both patches miss some context lines at the end, too.
> > ...
> the beacon timer isn't exclusively used to notify the driver when its
> time for a new beacon... The STA mode uses the same _timer_
> in reverse to wait for the next beacon form the assoc. AP.
> that said: It does not look like the firmware implements anything
> in this direction... But this is a clearly MAC register and there
> could be something in the silicon which does something useful with
> this information.
I wasn't aware of this usage within STA mode.
> so, to be on the safe side: why not preserve the old behavior for the
> STA mode as well and simply tell the hardware about dtim & beacon interval?
ar9170_set_beacon_timers() uses the beacon interval only if for AP mode, dtim is left in STA mode.
> The only remaining question is where to disabled the timer for STA.
> (which is in some way relevant to: [PATCH 2/2] because previously,
> these timers were always disabled by remove_interface.)
>
> I think the best place is in ar9170_op_bss_info_changed:
> if (changed & BSS_CHANGED_ASSOC) {
>
> just when bss_conf->assoc gets "0".
Yes. IMHO also enable on bss_conf->assoc == 1.
I'll look into another version of both patches after running some tests in STA mode.
Regards,
Joerg.
next prev parent reply other threads:[~2009-08-05 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 0:13 [PATCH 1/2] ar9170: cleanup of bss_info_changed and beacon config Joerg Albert
2009-08-05 2:04 ` Christian Lamparter
2009-08-05 19:05 ` Joerg Albert [this message]
2009-08-05 20:25 ` Christian Lamparter
2009-08-07 14:42 ` John W. Linville
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=4A79D7E5.1080604@gmx.de \
--to=jal2@gmx.de \
--cc=chunkeey@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.