From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Mike Mu <mikemu@google.com>, linux-wireless@vger.kernel.org
Cc: Stanley Mui <stanleymui@google.com>
Subject: Re: Configuring Minstrel-Blues
Date: Mon, 15 Aug 2016 23:48:35 +0200 [thread overview]
Message-ID: <f32852ed-0fee-1711-e26d-5a41f831267a@dd-wrt.com> (raw)
In-Reply-To: <CAGTDyhHOxwTiXtsWuy1cLq+eraikTs9McS0kUBXS2W6B09CwgQ@mail.gmail.com>
Am 15.08.2016 um 23:41 schrieb Mike Mu:
> Hi Linux-Wireless,
>
> I am trying to enable Minstrel-Blues for the ath9k chipset that's used
> in Google Fiber's access points. I applied the patches in
> https://github.com/thuehn/Minstrel-Blues/tree/master/src onto our
> backports-20160122 tree, with some unsuspicious merge conflicts, and
> built an image.
>
> To test, I ran iperf from the AP to a station very close by. I
> captured the packets to look at the RSSI with and without the
> Minstrel-Blues patches applied, but did not see any difference in
> RSSI.
why do you think that a rate control algorithm will change the rssi?
> Is there anything I need to configure first to make it work? Is it
> possible that I'm missing a patch that's not in backports-20160122?
>
> Thanks!
> Mike
>
--
Mit freundlichen Grüssen / Regards
Sebastian Gottschall / CTO
NewMedia-NET GmbH - DD-WRT
Firmensitz: Berliner Ring 101, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565
next prev parent reply other threads:[~2016-08-15 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 21:41 Configuring Minstrel-Blues Mike Mu
2016-08-15 21:48 ` Sebastian Gottschall [this message]
2016-08-16 12:08 ` Sven Eckelmann
2016-08-17 11:52 ` Thomas Hühn
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=f32852ed-0fee-1711-e26d-5a41f831267a@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mikemu@google.com \
--cc=stanleymui@google.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