From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Bayesian rate control
Date: Mon, 24 Oct 2016 07:28:32 +0200 [thread overview]
Message-ID: <1477286912.4085.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGp19xcg1qCP3+JNbuiB7Hx=UjLN7KP55wVJT0sKV-iE12501A@mail.gmail.com> (sfid-20161023_160622_798535_C6DAB0EF)
> 1. Is there anybody else out there thinking along similar lines?
I'm not aware, but that may not mean much :)
> 2. What would be the best hardware/software stack to base this work
> on?
>
> I'm thinking the best driver for rate control experimentation would
> be ath9k, right? If so then a TP-Link TL-WA901ND router (apparently
> based on Qualcomm QCA956x SOC) with OpenWrt, and a TP-Link TL-WDN4800
> PCIe card (apparently based on Atheros AR9380 with PCI ID 168c:0030)
> for my desktop sounds like a good combo, no?
Seems reasonable, yes. You wouldn't have VHT, but HT has enough search
space to keep you busy ;-)
> But would I have to run a custom kernel on my desktop then (or can I
> somehow get by with an Ubuntu standard kernel)?
You could use a backported driver. https://backports.wiki.kernel.org/
johannes
next prev parent reply other threads:[~2016-10-24 5:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 13:57 [ath9k-devel] Bayesian rate control Björn Smedman
2016-10-24 5:28 ` Johannes Berg [this message]
2016-10-24 20:23 ` Björn Smedman
2016-10-25 7:14 ` Johannes Berg
2016-10-26 3:25 ` Adrian Chadd
2016-10-26 5:56 ` Johannes Berg
2016-11-05 5:09 ` Adrian Chadd
2016-11-15 9:34 ` Johannes Berg
2016-11-16 4:45 ` Adrian Chadd
2016-10-24 15:09 ` Dave Taht
2016-10-25 19:41 ` 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=1477286912.4085.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.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).