From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: Richard Brown <richard.e.brown@dartware.com>,
"<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] WNDR3700v4 is out...
Date: Sun, 23 Dec 2012 08:02:29 -0500 [thread overview]
Message-ID: <CAA93jw5TQwWK86KOcS59YhGA+r2eEEWJU28vCgZCqrhWL6Qf4g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212222325300.21063@nftneq.ynat.uz>
On Sun, Dec 23, 2012 at 2:27 AM, David Lang <david@lang.hm> wrote:
> On Thu, 20 Dec 2012, Richard Brown wrote:
>
>> 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 found a WNDR3700v4 at the local Staples for $99.99. I wasn't brave
>> enough to buy it. Here's an image of the box so you can recognize it...
>
>
> I've purchased one, but I don't have the openwrt experiance to bootstrap
> this. I have built my own openwrt images for the 3700v2 and 3800 and have
> been using Linux since the 0.99 kernel days, so I am very comfortable
> mucking with kernel compile options.
>
> If someone is willing to coach me through the process, I'd be happy to do
> the experimentation.
I've ordered one too, but I would argue that a concerted effort would
need to be made on the part of some core #openwrt devs to get it
anywhere. The cpu is a mips 74k. It's a dual issue core with a very,
very long pipeline, so although it boasts twice the instructions per
clock than the 24k, and in simple benchmarks like drystone, rocks,
that deep pipeline isn't helpful for tons of code. (IMHO). It doesn't
look like the cache architecture is improved much, either.
It's not clear what the ethernet driver is, there appear to be legal
issues on the equivalent broadcom ethernet device, and so on, and so
forth.
You will need, at least, a 3.3v serial port and adaptor, and jtag
might be needed. If you want to learn about just how painful it is to
bring up a new board, this is your chance!
It makes sense to start a thread on openwrt-devel about doing the port.
https://forum.openwrt.org/viewtopic.php?id=41092
And/or find some other still supported hardware still being shipped by
some other manufacturer.
Frankly, if we truly have to jump platforms, I'd rather go arm.
> David Lang
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2012-12-23 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4.1356033603.24143.cerowrt-devel@lists.bufferbloat.net>
2012-12-20 21:21 ` Richard Brown
2012-12-23 7:27 ` David Lang
2012-12-23 13:02 ` Dave Taht [this message]
2012-12-23 14:45 ` dpreed
2012-12-23 15:16 ` David Lang
2012-12-23 15:22 ` Outback Dingo
2012-12-23 15:50 ` David Lang
2012-12-23 15:53 ` Dave Taht
2012-12-23 16:14 ` David Lang
2012-12-23 16:38 ` Dave Taht
2012-12-23 16:57 ` David Lang
2012-12-23 17:08 ` Dave Taht
2013-01-03 19:56 ` David Lang
2013-01-03 20:03 ` 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=CAA93jw5TQwWK86KOcS59YhGA+r2eEEWJU28vCgZCqrhWL6Qf4g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=richard.e.brown@dartware.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