From: Aaron Wood <woody77@gmail.com>
To: David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement
Date: Thu, 27 Mar 2014 13:50:27 +0100 [thread overview]
Message-ID: <CALQXh-O2PCpn8p1-KzBeWm5B34zsbB0Xt9rfL8bWtN_B=v4h_A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403261455030.2190@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
On Wed, Mar 26, 2014 at 11:11 PM, David Lang <david@lang.hm> wrote:
> If the openwrt folks could figure out how they are going to deal with NAND
> flash, it would be nice to be able to use one of the many routers that is
> shipping with more flash (128M in the newer netgear routers would be nice)
>
> if I were to get my hands on one, what sort of testing would you want to
> do to it to tell if it looks like it would hold up?
I have experience running mtd on NAND, using jffs2. It seems to be holding
up well. Better than NOR did, honestly. Although in general, I wish they
would shift to eMMC. But it's driven by two factors:
1) part cost
2) chipset support from the router SoC vendors
Given some of the wishes that I see on here, I think for development,
people would be happier with a platform that wasn't based on a router SoC
(like the wndr is), but instead was based on an embedded application
processor with PCIe for the radios, and an external switch fabric. But for
thermal purposes alone, I've been seeing more and more external switch
fabrics. The heat of a 5-port gigabit switch IC is pretty substantial
(from my teardowns).
One item I think will be a boon, especially with DNSSEC, is super-cap or
battery-backed rtc, but that's asking for a unicorn, I think. Or... a
Gateworks Ventana GW5310 loaded with a couple standard (industrial-grade)
PCIe radios, loaded into a custom case. My guess is that it's a pretty
expensive route, though. I would be surprised if a completely assembled
unit would be <$300. At which point it starts to look better to just run a
separate router and AP (using standard wndr-type platforms as the APs and a
higher-end board or PC as the gateway).
-Aaron
[-- Attachment #2: Type: text/html, Size: 2158 bytes --]
next prev parent reply other threads:[~2014-03-27 12:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1403251259390.747@uplift.swm.pp.se>
2014-03-25 15:16 ` Dave Taht
2014-03-26 22:11 ` David Lang
2014-03-27 12:50 ` Aaron Wood [this message]
2014-03-27 14:39 ` David Lang
2014-03-28 8:36 ` Mikael Abrahamsson
2014-03-28 9:33 ` Sebastian Moeller
2014-03-28 13:30 ` Aaron Wood
2014-03-28 18:40 ` Michael Richardson
2014-03-28 19:39 ` Dave Taht
2014-03-28 21:01 ` Aaron Wood
2014-03-29 21:08 ` Michael Richardson
2014-03-29 21:25 ` Dave Taht
2014-03-30 22:03 ` Michael Richardson
2014-03-30 22:10 ` Dave Taht
2014-03-28 19:14 ` Michael Richardson
2014-03-29 19:27 Martin Bailey
2014-03-29 19:52 ` Dave Taht
2014-03-29 19:56 ` Dave Taht
2014-03-29 20:19 ` Martin Bailey
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='CALQXh-O2PCpn8p1-KzBeWm5B34zsbB0Xt9rfL8bWtN_B=v4h_A@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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