From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Matthias Fend <Matthias.Fend@wolfvision.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: rt2x00: Ralink RT5572 very high peak current consumption
Date: Wed, 4 Jun 2014 15:18:01 +0200 [thread overview]
Message-ID: <20140604131801.GB1416@redhat.com> (raw)
In-Reply-To: <CC2A85E271C1FB479D9C17305347F69A44E4A7@WOLFSERVER19.wolfvision-at.intra>
Hi
On Tue, May 27, 2014 at 03:44:01PM +0000, Matthias Fend wrote:
> You just made my day! This was exactly the setting I was looking for.
> And yes, it seems that clearing the TXWI at the beacon location is not enough to completely disable beacon sending.
> Together with the already mentioned change in TXOP_HLDR_ET (use 0x0A instead of 0x82) it's looking identical to the windows setup.
I don't know why TXOP_HLDR_ET registr does matter, it seems to be
setting that is used for HCCA (Hybrid coordintanion function), which we
do not support (we do not set TXOP_HLDR_ADDR). But perhaps this setting
is also used on EDCA. Did you also tested this setting on STA mode ?
Regarding MAC_BSSID_DW1_BSS_BCN_NUM, I'll post RFC patches, please
test them (whould be good to test them on multi-vif AP setup, to
see if many beacons works).
Stanislaw
prev parent reply other threads:[~2014-06-04 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 12:25 rt2x00: Ralink RT5572 very high peak current consumption Matthias Fend
2014-05-26 15:37 ` AW: " Matthias Fend
2014-05-26 16:56 ` Andreas Hartmann
2014-05-27 15:12 ` Stanislaw Gruszka
2014-05-27 15:44 ` AW: " Matthias Fend
2014-06-04 13:18 ` Stanislaw Gruszka [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=20140604131801.GB1416@redhat.com \
--to=sgruszka@redhat.com \
--cc=Matthias.Fend@wolfvision.net \
--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 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.