From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (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 8D07421F19C for ; Mon, 27 May 2013 06:32:23 -0700 (PDT) Received: by mail-ie0-f173.google.com with SMTP id k5so18511272iea.32 for ; Mon, 27 May 2013 06:32:23 -0700 (PDT) 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; bh=5oPs2reznylAW1JnccnXovyzZMpesAZ0JGnbzxPy3eQ=; b=wABWSTUpmDkNHWvaNd3gZn8vRpMomp8pCa5fDt6ELKjoFJjtTLgs/oHz/5jwVayPmc sSniI3QBdSaUewwmXRYteRNNo77XPBlDOEKi3a73Zp4mYWP7YX9CHbvvYB9gvW+ua/Zw TaQTtR8Ct+7FCpOFnbvsPWAbznxVilstAkP85HkPjc4oRPuXYEMnxok16JxBYV723EF4 j7dn9LtfLj1rOF8zcVjDsUdQOfqN1WmHoOpr6wQ8mfM0Bqe++/xvbJZ8a8eurEHW9Sw7 Zl23RHI9ifJ6WdxzBhntwAAEIsQh5k/XjhCfNBwQQEi3eKNgsTN/sSLgfHfh8mGQGN0C Llew== MIME-Version: 1.0 X-Received: by 10.50.72.49 with SMTP id a17mr4796630igv.36.1369661542903; Mon, 27 May 2013 06:32:22 -0700 (PDT) Received: by 10.64.35.44 with HTTP; Mon, 27 May 2013 06:32:22 -0700 (PDT) In-Reply-To: References: Date: Mon, 27 May 2013 06:32:22 -0700 Message-ID: From: Dave Taht To: David Lang Content-Type: multipart/alternative; boundary=047d7bdc9e50ba352f04ddb32db6 Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] tp-link 4300 evaluation 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: Mon, 27 May 2013 13:32:23 -0000 --047d7bdc9e50ba352f04ddb32db6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, May 27, 2013 at 2:32 AM, David Lang wrote: > On Sun, 26 May 2013, Lance Hepler wrote: > > That's tragic. I just picked up a Netgear WNDR4300 (openbox on sale at t= he >> local Fry's) to see if I could hack up a CeroWrt clone on it. It seems t= o >> be mostly the same hardware as the WNDR3700v4 and the TP-Link WDR43[01]0= , >> with things just wired up slightly differently. >> > > As I understnad it, the difference between the WNDR3700v4 and WNDR4300 is > that the 4300 has a slightly better wireless chip. > > Unfortunantly from what I've seen so far, they did something wierd with > the storage and as a result the stock openwrt can't access it. I've seen > reports of people getting it to run from an initramfs, but this means tha= t > no settings can be preserved across reboot. > > If you've seen anything different, I'd be very interested to hear about i= t > (I picked up a 3700v4 and a couple 4300's for testing) > according to a birdie, "it looks like it's an ONFI with quirks, or nobody has realised that it's ONFI at all.". Perhaps that's enough clue to get someone started? but I fear jtag debugging will be needed. Flash chips tend to have interesting race conditions.... > David Lang > > > 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 readi= ly >> consumer-available hardware with open-source friendly SoCs. (Maybe a >> Xilinx >> Zynq-based router funded through Kickstarter? =3D) >> >> This is all pretty new stuff, perhaps some more performance can be glean= ed >> by tuning the compiler optimizations (-march=3D74Kc?), 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, th= e >> 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 t= he >> list to respond to this email, as such I naturally didn't receive the >> original.. >> > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > _______________________________________________ > 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 --047d7bdc9e50ba352f04ddb32db6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, May 27, 2013 at 2:32 AM, David L= ang <david@lang.hm> wrote:
On Sun, 26 May 2013, Lance Hepler wrote:

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.

As I understnad it, the difference between the WNDR3700v4 and WNDR4300 is t= hat the 4300 has a slightly better wireless chip.

Unfortunantly from what I've seen so far, they did something wierd with= the storage and as a result the stock openwrt can't access it. I'v= e seen reports of people getting it to run from an initramfs, but this mean= s that no settings can be preserved across reboot.

If you've seen anything different, I'd be very interested to hear a= bout it (I picked up a 3700v4 and a couple 4300's for testing)

according to a birdie, "it looks like it's an ONFI with quirks= , or nobody has realised that it's ONFI at all.". Perhaps that'= ;s enough clue to get someone started? but I fear jtag debugging will be ne= eded. Flash chips tend to have interesting race conditions....


David Lang


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

This is all pretty new stuff, perhaps some more performance can be gleaned<= br> by tuning the compiler optimizations (-march=3D74Kc?), 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 fixet= h
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..

_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel




--
Dave T=E4ht

= Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html=20 --047d7bdc9e50ba352f04ddb32db6--