Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: dpreed@reed.com
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net, codel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
Date: Thu, 20 Dec 2012 10:05:15 -0500	[thread overview]
Message-ID: <CAA93jw52UXboVRFuH6SbyXN-NNqR5MgG7gr0G99wr=cEqDnXew@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5KD0ztWW36XQ3A41_+nmubrmUCj=rLaSs1Sp2SzSRv-g@mail.gmail.com>

OK, I ordered 2. It's not clear how the ethernet is fully implemented
(The marvel phy is documented, the actual ethernet interface is not so
far as I can see, so some source code  reading is going to be
required. )

I note that me doing this is also kind of driven by supplies of the
wndr3800 drying up. The prospect of having to do yet another port to
some other low-end hardware for cerowrt is depressing and mildly
intimidating. I'd rather do anything else than bring up yet another
board that will be obsolete in 6 months, when I'd rather be working at
a level far, far, above the hardware at this point. If I gotta do a
new board bring up, I'd rather switch to arm as I view MIPs as
basically dead (it's not dead, it's resting) at this point.

I also picked up a dreamplug today to BQL it. Not fond of that arm
implementation.

As for cero's future, well...

The wndr3700v4 is out, and appears to be a good hardware upgrade from
the 3800 series, but it's not supported by openwrt yet.

I took a look at their GPL source distribution. And yea! it's openwrt.
And boo! it's ancient openwrt, for example dnsmasq is 2.39 (current is
2.64), and their kernel is 2.6.31.

I think the cpu and ethernet chips tho look a lot better: Atheros
AR9344+ AR9580(5GHz)+AR9344(2.4GHz). It's my hope these do ipv6
better.

I have looked at similar products from buffalo and others, would like
external antennas and a good switch this time around. Thoughts?

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2012-12-20 15:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dave.taht@gmail.com>
2012-12-20  7:28 ` Dave Taht
2012-12-20  8:17   ` Hal Murray
2012-12-20  8:27     ` Jonathan Morton
2012-12-20  9:51       ` Hal Murray
2012-12-20  9:13     ` Dave Taht
2012-12-20  9:26       ` Dave Taht
2012-12-20 10:32         ` Hal Murray
2012-12-20 13:53           ` [Cerowrt-devel] " dpreed
2012-12-20 14:18             ` Dave Taht
2012-12-20 15:05               ` Dave Taht [this message]
2012-12-21 12:34                 ` Dave Taht
2012-12-21 17:48                   ` dpreed
2012-12-21 18:14                     ` Jim Gettys
2012-12-21 18:25                       ` dpreed
2012-12-21 18:45                         ` Jim Gettys
2012-12-21 19:34                           ` dpreed
2012-12-21 19:42                             ` Jim Gettys
2012-12-21 21:54                           ` [Codel] " David Woodhouse
2012-12-21 21:56                             ` John Crispin
2012-12-21 22:08                               ` David Woodhouse

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

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

  git send-email \
    --in-reply-to='CAA93jw52UXboVRFuH6SbyXN-NNqR5MgG7gr0G99wr=cEqDnXew@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dpreed@reed.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