Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Bob McMahon <bob.mcmahon@broadcom.com>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] a cheer up tweet for y'all
Date: Tue, 9 Jan 2024 06:36:52 -0500	[thread overview]
Message-ID: <CAA93jw6ryXYAjdwYwQvNeQ8-4Z_Bo3NospXcTq8wBnk20cVDvw@mail.gmail.com> (raw)
In-Reply-To: <877cki4vxq.fsf@toke.dk>

On Tue, Jan 9, 2024 at 5:56 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Bob McMahon via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net>
> writes:
>
> > What are you expecting from chip makers?
>
> High-quality open source drivers, upstreamed into the Linux mainline by
> the time the hardware ships, would be a good start :)
>
> Vendors seem to manage this for Ethernet NICs just fine, so it can't
> really be a technical barrier that is keeping this from happening.
>
> If we're going further down the wish list, "no binary firmware blobs"
> would be next as far as I'm concerned. Not holding my breath on that
> one, though :/

Data Sheets with register layouts
Sending internal developers to Linux technical conference like netdev
and linux plumbers
Participation in interop events (esp for wifi and 5g)
An Open Source programs office
Ponies

>
> -Toke



-- 
40 years of net history, a couple songs:
https://www.youtube.com/watch?v=D9RGX6QFm5E
Dave Täht CSO, LibreQos

  reply	other threads:[~2024-01-09 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 17:19 Dave Taht
2024-01-09  4:41 ` Bob McMahon
2024-01-09 10:56   ` Toke Høiland-Jørgensen
2024-01-09 11:36     ` Dave Taht [this message]
2024-01-09 17:42     ` Bob McMahon
2024-01-10 11:23       ` Toke Høiland-Jørgensen
2024-01-10 13:55         ` XianJun Jiao
2024-01-10 15:47           ` Dave Taht
2024-01-10 18:23         ` Bob McMahon
2024-01-11  9:31           ` Dave Taht
2024-01-11 17:29             ` Bob McMahon

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=CAA93jw6ryXYAjdwYwQvNeQ8-4Z_Bo3NospXcTq8wBnk20cVDvw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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