From: Dave Taht <dave@taht.net>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
make-wifi-fast@lists.bufferbloat.net,
Rajkumar Manoharan <rmanohar@codeaurora.org>,
nbd@nbd.name
Subject: [Make-wifi-fast] State of the make-wifi-fast patchset?
Date: Sun, 03 Feb 2019 19:23:44 -0800 [thread overview]
Message-ID: <87tvhk6xtr.fsf_-_@taht.net> (raw)
In-Reply-To: <87sgxgc199.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Fri, 25 Jan 2019 14:31:14 +0100")
Are we at the point yet where the whole is testable out of
wireless-next?
Are there "proper" devices readily available that can touch the
controversy inducing ath10k stuff? I do have a lot of older ath10k
gear...
Has support for mt76 landed? Any prototype patches from intel?
(this message partially triggered by the release of openwrt 18.06.2 and
the pending 19.x branch, and being essentially asleep since christmas)
next prev parent reply other threads:[~2019-02-04 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 14:20 [Make-wifi-fast] [PATCH v6 0/4] Switch ath9k and ath10k to mac80211 airtime framework Toke Høiland-Jørgensen
2019-01-22 14:20 ` [Make-wifi-fast] [PATCH v7 1/4] mac80211: Expose ieee80211_schedule_txq() function Toke Høiland-Jørgensen
2019-01-22 14:23 ` Toke Høiland-Jørgensen
2019-01-25 13:25 ` Johannes Berg
2019-01-25 13:31 ` Toke Høiland-Jørgensen
2019-02-04 3:23 ` Dave Taht [this message]
2019-02-04 11:19 ` [Make-wifi-fast] State of the make-wifi-fast patchset? Toke Høiland-Jørgensen
2019-01-22 14:20 ` [Make-wifi-fast] [PATCH v6 2/4] ath9k: Switch to mac80211 TXQ scheduling and airtime APIs Toke Høiland-Jørgensen
2019-02-12 18:45 ` Kalle Valo
2019-01-22 14:20 ` [Make-wifi-fast] [PATCH v6 3/4] ath10k: migrate to mac80211 txq scheduling Toke Høiland-Jørgensen
2019-01-22 14:20 ` [Make-wifi-fast] [PATCH v6 4/4] ath10k: reporting estimated tx airtime for fairness Toke Høiland-Jørgensen
2019-01-24 19:28 ` Kan Yan
2019-01-25 8:31 ` Toke Høiland-Jørgensen
2019-02-11 9:24 ` Kalle Valo
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvhk6xtr.fsf_-_@taht.net \
--to=dave@taht.net \
--cc=johannes@sipsolutions.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=nbd@nbd.name \
--cc=rmanohar@codeaurora.org \
--cc=toke@redhat.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