From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id CA4C321F1A6 for ; Sat, 29 Mar 2014 13:19:27 -0700 (PDT) Received: by mail-ob0-f169.google.com with SMTP id va2so7579195obc.28 for ; Sat, 29 Mar 2014 13:19:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=V6SJv6JDwb7qek5wvVe3H5S0NcVLAPDYLTJkuoXMWi4=; b=m2v77kymGZPE7wc/rPkw6VXw8yp0Rwj7OuTOy3Vym9gmNnfv/6aMKGWqG4p04oGskq BOM33NAL0yhEYiKKsNccPOC2Ak8CPtnRFRaSpBKND3fWVO9GboF3/Y+ARVV+3sWJg+Nu RM9eylE6kJghSsQuba461iY3sXQ9OKOpthmIhWalyBA0qrPQG4bmVz6ZkBmOTPUhMowD 8A1MVpkpVfm7bGVpgtiQ8XPVK0zRuRMWW7JNNvNfzFgdU2eYoQMTwRRJrYt8MQRdbmzn U4YeINXYxpmY/AUdEGNwk9Rs/58B4tz0P1lB3qqmp20AaDmY0NB8ttVXiFwqIzd988ct V35w== X-Gm-Message-State: ALoCoQm3Q2UKwWHW+qb79cJYzCjoATQ7scGsjJe3JVXsq+hfnOK9Z2DcybAOKX8RWXWuQFtuT4sw MIME-Version: 1.0 X-Received: by 10.60.162.7 with SMTP id xw7mr13399747oeb.13.1396124366731; Sat, 29 Mar 2014 13:19:26 -0700 (PDT) Received: by 10.76.9.40 with HTTP; Sat, 29 Mar 2014 13:19:26 -0700 (PDT) X-Originating-IP: [66.183.97.3] In-Reply-To: References: Date: Sat, 29 Mar 2014 13:19:26 -0700 Message-ID: From: Martin Bailey To: Dave Taht Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement 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: Sat, 29 Mar 2014 20:19:28 -0000 You're right, there is that proprietary firmware bit for 5GHz. It's mostly but not fully open-source then, at least the firmware is easy to access and update. Newegg specifies v2 in the product description, that's the most reliable source for now. I imagine Amazon will also run out of 1.0 and 1.1 inventory pretty soon if it's not already the case. On Sat, Mar 29, 2014 at 12:56 PM, Dave Taht wrote: > On Sat, Mar 29, 2014 at 12:27 PM, Martin Bailey wrot= e: >> The recently released v2 of the TP-Link Archer C7 router would be a >> pretty good low-cost replacement. It's fully open-source Atheros/Qualcom= m, > > Um, no, the ath10k depends on a binary blob. Which has been really > irksome. I do hope they open-source the firmware so we can make > more progress on incorporating better algorithms into wifi. > >> includes a fairly high performance 720MHz SOC with 128MB RAM, 16MB >> flash and 6 dual-band antennas (AC1750) with very good range. It can >> be found for $99 right now. The first hardware revision isn't >> supported by the ath10k driver in OpenWRT so make sure to only >> consider v2. > > It's not clear how to ensure you are buying a v2 through sites like amazo= n. > > If you can find a good source for it let me know... > >> >> http://wiki.openwrt.org/toh/tp-link/tl-wdr7500 >> https://wikidevi.com/wiki/TP-LINK_Archer_C7_v2.x >> http://www.newegg.com/Product/Product.aspx?Item=3DN82E16833704177 >> >>> On Thu, 27 Mar 2014, Aaron Wood wrote: >>> >>>> Date: Thu, 27 Mar 2014 13:50:27 +0100 >>>> From: Aaron Wood >>>> To: David Lang >>>> Cc: Dave Taht , >>>> "cerowrt-devel at lists.bufferbloat.net" >>>> >>>> Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement >>>> >>>> On Wed, Mar 26, 2014 at 11:11 PM, David Lang wrote: >>>> >>>>> If the openwrt folks could figure out how they are going to deal with >>>>> NAND >>>>> flash, it would be nice to be able to use one of the many routers tha= t is >>>>> shipping with more flash (128M in the newer netgear routers would be >>>>> nice) >>>>> >>>>> if I were to get my hands on one, what sort of testing would you want= to >>>>> do to it to tell if it looks like it would hold up? >>>> >>>> >>>> I have experience running mtd on NAND, using jffs2. It seems to be >>>> holding >>>> up well. Better than NOR did, honestly. Although in general, I wish = they >>>> would shift to eMMC. But it's driven by two factors: >>>> >>>> 1) part cost >>>> 2) chipset support from the router SoC vendors >>>> >>>> Given some of the wishes that I see on here, I think for development, >>>> people would be happier with a platform that wasn't based on a router = SoC >>>> (like the wndr is), but instead was based on an embedded application >>>> processor with PCIe for the radios, and an external switch fabric. >>> >>> I think we have two competing desires. >>> >>> one is to have a nice powerful device for those people who have fast >>> connections >>> and for us to experiment with. >>> >>> the second is to have a 'home' device. >>> >>> using a 3800 or similarly priced ($100-$150 USD) device that's readily >>> available >>> is very good for the second category, the question is if we can find on= e >>> that's >>> powerful enough for the first. >>> >>> David Lang >>> >>>> But for >>>> thermal purposes alone, I've been seeing more and more external switch >>>> fabrics. The heat of a 5-port gigabit switch IC is pretty substantial >>>> (from my teardowns). >>>> >>>> One item I think will be a boon, especially with DNSSEC, is super-cap = or >>>> battery-backed rtc, but that's asking for a unicorn, I think. Or... = a >>>> Gateworks Ventana GW5310 loaded with a couple standard (industrial-gra= de) >>>> PCIe radios, loaded into a custom case. My guess is that it's a prett= y >>>> expensive route, though. I would be surprised if a completely assembl= ed >>>> unit would be <$300. At which point it starts to look better to just = run >>>> a >>>> separate router and AP (using standard wndr-type platforms as the APs = and >>>> a >>>> higher-end board or PC as the gateway). >>>> >>>> -Aaron >>>> >> _______________________________________________ >> 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