Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Kelvin Edmison <kelvin@edmison.net>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Alternative platform for make-wifi-fast?
Date: Thu, 10 Mar 2016 10:16:27 -0800	[thread overview]
Message-ID: <CAA93jw5iJuNPcasG17bySvAG0XLiKpu3wm-odVCsrSunEeDn3g@mail.gmail.com> (raw)
In-Reply-To: <CALErE73gsC-r6wSoiMFa5pNi17dyWueZT08=8yB-qVSHT6VW3w@mail.gmail.com>

I have longed for something wifi to enter the realm of the OCP project
for ages, and more enterprise-y features be regularly available on the
lower end (see also, eero).

as for all the talk of open-ness... it's just talk till code shows up
somewhere like github - what's the chipset? where's the source?
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi


On Thu, Mar 10, 2016 at 6:53 AM, Kelvin Edmison <kelvin@edmison.net> wrote:
> It's not a router platform, but I thought this was an interesting
> development.
>
> EdgeCore is apparently contributing 3 Access Point designs to the
> OpenCompute project.
>
> http://www.businesswire.com/news/home/20160309005481/en/Edgecore-Networks-Brings-Open-Networking-Access-Network
>
> One of the designs, a 802.11ac 3x3 MIMO design, looks to be based on this:
> http://www.edge-core.com/temp/ec_download/1448/ECW7220-L_DS_20150916.pdf
> (there is an outdoor 3x3 and an indoor 2x2 as well)
>
> Are there any thoughts as to the feasibility of using this as a basis for
> make-wifi-fast?
>
> Regards,
>   Kelvin
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

      reply	other threads:[~2016-03-10 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 14:53 Kelvin Edmison
2016-03-10 18:16 ` Dave Taht [this message]

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

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

  git send-email \
    --in-reply-to=CAA93jw5iJuNPcasG17bySvAG0XLiKpu3wm-odVCsrSunEeDn3g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=kelvin@edmison.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