From: Dave Taht <dave.taht@gmail.com>
To: Zhang Wenjie <wei.a.yang@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Always in search of the next gen
Date: Sat, 22 Nov 2014 16:39:11 -0800 [thread overview]
Message-ID: <CAA93jw7d_D+4A9_eYv5ix-oiczkPLBCxemMHvh79DNyWme1JQQ@mail.gmail.com> (raw)
In-Reply-To: <6E7FBEA3-0659-4AA7-8B9B-FBED0F439FBC@gmail.com>
On Sat, Nov 22, 2014 at 4:07 PM, Zhang Wenjie <wei.a.yang@gmail.com> wrote:
>
> 在 2014年11月23日,上午1:49,Dave Taht <dave.taht@gmail.com> 写道:
>
> These looked interesting:
>
> http://www.alibaba.com/product-detail/made-in-china-2-4G-5GHz_1891823798.html
>
>
> But it seems that it uses ar9341 which only supports 802.11b/g/n
There are multiple conflicting needs at play here. the first Is to
find a router that is more readily available than the wndr3800, that
we can continue to experiment on in the make-wifi-fast context. At the
moment the ath9k is the best candidate chip to hack on. I would like
to find a dual radio device even smaller and cheaper than the one
above to do that work with, but still of high build quality and
overall design.
Then there are needs for something faster as a home gateway with sqm.
Things like the edgerouter dont compare to a low end atom here, and
the only things in between in terms of cpu capability are things like
the linksys ac1900 and the x4.
Then there are desires for 802.11ac, which, due to the mostly
unhackable firmware available at this point is pretty frustrating to
try and move the industry forward with.
A fourth need, dominating all these needs overall, is sustainable
funding and support from those in the industry that would like to be
making better routers.
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
prev parent reply other threads:[~2014-11-23 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 17:49 Dave Taht
2014-11-23 0:07 ` Zhang Wenjie
2014-11-23 0:39 ` 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=CAA93jw7d_D+4A9_eYv5ix-oiczkPLBCxemMHvh79DNyWme1JQQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=wei.a.yang@gmail.com \
/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