Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Lance Hepler <nlhepler@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] tp-link 4300 evaluation
Date: Sun, 26 May 2013 18:23:04 -0700	[thread overview]
Message-ID: <CAE0u2M62RQy+vDBCUNsLH2RYkupfA1qewVB5mvfdJ+-UV5RtSQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

That's tragic. I just picked up a Netgear WNDR4300 (openbox on sale at the
local Fry's) to see if I could hack up a CeroWrt clone on it. It seems to
be mostly the same hardware as the WNDR3700v4 and the TP-Link WDR43[01]0,
with things just wired up slightly differently.

I'd be interested in your netperf testing setup. With the AR71xx chips
going out of style, the AR934x series is probably our best bet for readily
consumer-available hardware with open-source friendly SoCs. (Maybe a Xilinx
Zynq-based router funded through Kickstarter? =)

This is all pretty new stuff, perhaps some more performance can be gleaned
by tuning the compiler optimizations (-march=74Kc?), and perhaps the
AR8327N switch chip could use someone poking about its driver (the rtl8366s
in the WNDR3800 _has_ been around a while). Although, in all honesty, the
omission of that second ethernet port could just be a coffin nail.

Helpfully, the WNDR4300 has 128MB of NAND flash, as does the WNDR3700v4. So
compiling a full CeroWRT distribution shouldn't be a problem. The fixeth
script will need to be changed, but not much else.

Lance

PS: I apologize if this post doesn't show up where it should. I joined the
list to respond to this email, as such I naturally didn't receive the
original..

[-- Attachment #2: Type: text/html, Size: 1510 bytes --]

             reply	other threads:[~2013-05-27  1:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27  1:23 Lance Hepler [this message]
2013-05-27  9:32 ` David Lang
2013-05-27 13:32   ` Dave Taht
2013-05-27 13:33     ` David Lang
2013-05-27 16:30       ` Lance Hepler
2013-05-27 13:13 ` Dave Taht
2013-05-27 21:08   ` Lance Hepler
2013-05-27 23:41     ` Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2013-05-26 12:08 Dave Taht

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=CAE0u2M62RQy+vDBCUNsLH2RYkupfA1qewVB5mvfdJ+-UV5RtSQ@mail.gmail.com \
    --to=nlhepler@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.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