From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Eric Raymond <esr@thyrsus.com>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] still trying to find hardware for the next generation worth hacking on
Date: Sat, 16 Aug 2014 00:21:50 +0300 [thread overview]
Message-ID: <CAJq5cE2MEieF8MYA1ezdnJ_TLN_xotJm1ZtHGGSeu0qFEAuKuw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6MntHVbTT4n_-bGm7Das3-kDseCJiR=WzTT6zpY06s1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
> one promising project is this one: https://www.turris.cz/en/
That does look promising. The existing software is OpenWRT, so porting
CeroWRT shouldn't be difficult.
The P2020 CPU is a PowerPC Book E type - basically a 603e with the FPU
ripped out, then turned into an SoC. It should have loads of performance,
and enough I/O to feed those GigE ports effectively.
The only real software concern should be that it's big-endian, but since I
already use an old PowerBook as a firewall, that's unlikely to be a big
hurdle. Fq_codel works well on it.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 710 bytes --]
next prev parent reply other threads:[~2014-08-15 21:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 20:33 [Cerowrt-devel] " Dave Taht
2014-08-15 20:51 ` [Cerowrt-devel] [Bloat] " Eric S. Raymond
2014-08-15 21:02 ` Dave Taht
2014-08-15 21:21 ` Jonathan Morton [this message]
2014-08-16 0:46 ` David P. Reed
2014-08-16 20:41 ` Michael Richardson
2014-08-17 17:13 ` dpreed
2014-08-17 17:43 ` William Katsak
2014-08-18 20:51 ` Frank Carmickle
2014-08-18 22:00 ` Dave Taht
2014-08-19 0:34 ` Michael Richardson
2014-08-22 3:11 ` Dave Taht
2014-08-22 13:16 ` Chuck Anderson
2014-08-22 13:32 ` William Katsak
2014-08-22 14:19 ` David P. Reed
2014-08-22 15:12 ` William Katsak
2014-08-22 20:20 ` dpreed
2014-08-22 20:39 ` [Cerowrt-devel] " Wes Felter
2014-08-18 19:19 ` [Cerowrt-devel] [Bloat] " Wes Felter
2014-08-18 20:09 ` Aaron Wood
2015-03-09 12:53 ` Guillaume Fortaine
2015-03-09 13:11 ` Sebastian Moeller
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=CAJq5cE2MEieF8MYA1ezdnJ_TLN_xotJm1ZtHGGSeu0qFEAuKuw@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=esr@thyrsus.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