Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] sophgo risc-v wifi6 chip
Date: Sat, 27 Jul 2024 14:23:44 -0700	[thread overview]
Message-ID: <CAHb6Lvoj_4qt0SwaXCZVnD2td+QRmO-DA7i2jPh=QhYgZ9JTUQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw74sAzx3hv5GPe_k5UThp9OjwJmN_-XCj0XjPM6rn62Ww@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2554 bytes --]

I wrote Cisco ios software early in my career (predating Wi-Fi and ethernet
switching.) We purchased a sun workstation for $100K that supported
compiles for 8 of us. Last week I built a 7 unit Rpi5 system running full
linux, pacing CCAs, ip routing, bridging, etc., connected via a managed
vlan switch for less than $1000. It's truly amazing that what was once a
full workstation is now so inexpensive.

I think a challenge we face is that these cheap SoCs are blinding us. They
are good for prototyping but not for end users homes which is at
around 2.2-2.3B worldwide. Then maybe ten Wi-Fi radios per home (using the
term radio loosely.)  Here, the solutions need to be in full transistors
(and very low power and very secure.) The advantages of getting rid of
these complex SoCs are so great it's worth doing. Wi-Fi doesn't need to be
managed by a complex workstation and 30+ years of software bloat. It just
needs to move packets well between a waveguide and free space. (The
preferred waveguide is fiber but others will work too.) It's non-trivial
the amount of NRE to do this and our industry to date has not even really
tried. Not sure why but it seems a mistake to me.

Bob


On Fri, Jul 26, 2024 at 3:57 PM Dave Taht via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:

>
>
> https://linuxgizmos.com/pine64-unveils-oz64-an-upcoming-sbc-featuring-sophgo-sg2000-soc-and-wi-fi-6/
>
> --
> Artists/Musician Campout Aug 9-11
> https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
> Dave Täht CSO, LibreQos
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.2: Type: text/html, Size: 3523 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  reply	other threads:[~2024-07-27 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 22:57 Dave Taht
2024-07-27 21:23 ` Bob McMahon [this message]
     [not found] <mailman.1.1722182401.12366.make-wifi-fast@lists.bufferbloat.net>
2024-07-29 12:03 ` Rich Brown
2024-07-29 17:01   ` 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='CAHb6Lvoj_4qt0SwaXCZVnD2td+QRmO-DA7i2jPh=QhYgZ9JTUQ@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=dave.taht@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