General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] "cerowrt II" announced by nlnet
Date: Tue, 7 Dec 2021 07:29:29 -0800	[thread overview]
Message-ID: <CAA93jw786GVm2GehmL945+BLqaD-cg7E4-1mbxM0PuBD0Raz2g@mail.gmail.com> (raw)

NLnet gave me a small grant to help fund at least a broad look at
what, if anything else, we could do on the fronts we care about.

https://nlnet.nl/project/CeroWRT-II/

Based on the promise of that grant (I got confirmation a few days ago)
for the last ~three months I'd been trying to scope out new work -
please see the openwrt forums for threads like:
https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554

Also: - we went off validating the nss hardware offload - looking at
packet captures - and I am still very low on ideas worth doing. And on
other people (paid or volunteer), interested in doing or funding them.

Some really interesting stuff has landed in the pending next stable
release of openwrt - the virtual time stuff went in, it's rumored
there is working
mu-mimo! The new mediatek chips look promising. But in all honesty the
future is very cloudy to me, and I have no intent (presently) to spin
up a branch per se, but to merely get one new feature in (better
hardware retries), to try and get on top of a wifi-6 chipset, and work
on a new tool (wtbb).

If only we could find steady, and significant funding this time
around... (this is more of a cerowrt II.000001 effort at this point).
I keep hoping more ISPs, and broadcom, in particular, would wake up to
their wifi problems. I'd love to see the eeros and the google wifi's
of the world working more closely with this community, too.

I think (lacking the pending testing) qualcom is in decent shape here,
and mediatek may well have leapfrogged them, for all I know. Intel
seems to be good, too, but they are not in the AP market. Ignorance,
however, is not bliss in my case. I want to *know*. :)

Thx, nlnet!


-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2021-12-07 15:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw786GVm2GehmL945+BLqaD-cg7E4-1mbxM0PuBD0Raz2g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --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