From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4AB24202102 for ; Thu, 3 Jan 2013 12:03:37 -0800 (PST) Received: by mail-ie0-f170.google.com with SMTP id k10so18864090iea.15 for ; Thu, 03 Jan 2013 12:03:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=wzbWiHBw5Hlvpco1k8iM5F1IB717fMTffzlveU6EbEw=; b=KrkeqvG07vWUtgjAv4R9iz1YEAukm3j10ztv1iApRHqoIbgEjNvXvtlJyM1L+PIAWh EFywJgAjHbnHoGyeIE8gwoC7wt3WuH4ZQQ6w71vYiNMtZXlR47/4Uwbvk/CS3GhfXHh6 oRUSF8o0cqbfwnQWqEnjvHb/+/XxnmFl1iDg+gcQmOLTQmJQvezglFGkBlLBcIjxw/oN 3z+kzlAx2r0dclRWKfPe3682rk+bqS7W5K4HNme4ohQmi42Z//Eldfu2Z+TEWqyDPkIP txQpiv5nqdhfTRq3IawUNfEoBAauCVWmr6kJPkRy/dyt0fL7Pxbmw5s1y1d2hla0IfKt 0cnw== MIME-Version: 1.0 Received: by 10.50.187.225 with SMTP id fv1mr38965717igc.96.1357243416774; Thu, 03 Jan 2013 12:03:36 -0800 (PST) Received: by 10.64.135.39 with HTTP; Thu, 3 Jan 2013 12:03:36 -0800 (PST) In-Reply-To: References: <54532012A5393D4E8F57704A4D55237E42A2907F@CH1PRD0510MB381.namprd05.prod.outlook.com> Date: Thu, 3 Jan 2013 12:03:36 -0800 Message-ID: From: Dave Taht To: David Lang Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Richard Brown , "" Subject: Re: [Cerowrt-devel] WNDR3700v4 is out... X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jan 2013 20:03:37 -0000 Although the wndr4300 gained support in openwrt, it is still rather limited when I last looked. Due to the use of NAND flash in this board Squashfs + JFFS2 may never work, and even with JFFS2, it's worrisome regarding wear leveling.... On Thu, Jan 3, 2013 at 11:56 AM, David Lang wrote: > still working on this, but openwrt has gained support for the WNDR4300, a= nd > reports are that it appears that it's the same board as the WNDR3700v4. T= he > 4300 is selling for ~$130 so it's a viable option, even if the 3700v4 fal= ls > through. > > David Lang > > > On Sun, 23 Dec 2012, Dave Taht wrote: > >> On Sun, Dec 23, 2012 at 2:27 AM, David Lang 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 bootstra= p >>> this. I have built my own openwrt images for the 3700v2 and 3800 and ha= ve >>> 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=3D41092 >> >> 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 >> >> >> >> >> > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html