Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Jon Pike <jonpike54@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] State of the MWFF...
Date: Wed, 23 Jan 2019 20:36:22 -0800	[thread overview]
Message-ID: <CALukJKTPK79LRD7M=t2D+HjfQ8f1kYw8VhigFJqD2LAYm9gDHg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

Ok, sorry about that one... And I'm not asking that anyone actually
make a speech.

I was wondering how to easily find what's changing in the different
versions, as well as what versions are available where...  I
appreciate the great efforts of continuing development, and the
ability to watch it,  it's just a bit hard for a non developer like me
to follow what's changed and what's still coming.  I haven't been able
to find any changelog or even a feature list in my searching.


I'm still not sure how much of the newer make wifi fast stuff is out
there in current available OpenWrt builds, how much has gotten into
ath10k, and similar questions.

Poking around with my home setup/test bed where I have a few OpenWrt
versions available...  I can see the following:


TP-Link C7,  17.01.06
kmod  cake - 2018-7-16-f3..4-1
luci-app-sqm - 1.1.3-1
ath10k-qca988x- 2017-01-11

TP-Link C7,  18 + Snapshot 1-16-19
kmod  cake - 2019-01-08
luci-app-sqm - 1.2.4-1

ath10k-qca988x-ct 2018-10-10-d366b80d-1

My main x86 router doesn't run wifi, so I don't have what 18.06.1 runs.

I also wonder which would be a better choice for my dumb AP's, and how
to maximize MWFF benefits I'm hopefully getting by using it.

I think having this info more available would benefit a lot of people....

[-- Attachment #2: Type: text/html, Size: 1828 bytes --]

             reply	other threads:[~2019-01-24  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  4:36 Jon Pike [this message]
2019-01-25  8:53 ` Toke Høiland-Jørgensen

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='CALukJKTPK79LRD7M=t2D+HjfQ8f1kYw8VhigFJqD2LAYm9gDHg@mail.gmail.com' \
    --to=jonpike54@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    /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