From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (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 DFF0721F1D1 for ; Thu, 21 Mar 2013 08:47:46 -0700 (PDT) Received: by mail-ob0-f182.google.com with SMTP id ef5so406080obb.13 for ; Thu, 21 Mar 2013 08:47:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KJSd9to4LsWlkPw8rYQOoYF1eGqGwhzd9JRRmujRtY8=; b=j9UCQBAqucu2zu719bHM/w+oTpagDBbYnaxMSIbTJsS7c81S5ZIRY7w4JHgP6OuPR0 iCa8x2FuoHUMKPYfxhc3Gh9S3YVutE8b1Da2XqwEGqf+be3vJLsVlYJSq/PLQ7CGUROs II1wO+xT6DbLP0/3Lppd8e6XNfM9YJBt82KHJOhNFXdPDU4c+Pjy3NVBGxmqhrv36udx A0Npp8XqeEwu8OAiWaGalwC31Fvvp87y0KIiXvsrUDdNzGxSQ7cj0ai8TzqFWbA3baAs Gh4DmJPrs0i+UDG4lqKERE4y9dG5CSGVvDLltkqG6g93THFD/EI6Y87uTuw/X6A5Dwoy vuzQ== MIME-Version: 1.0 X-Received: by 10.182.95.34 with SMTP id dh2mr7194503obb.65.1363880865886; Thu, 21 Mar 2013 08:47:45 -0700 (PDT) Sender: gettysjim@gmail.com Received: by 10.76.22.193 with HTTP; Thu, 21 Mar 2013 08:47:45 -0700 (PDT) In-Reply-To: <1363879886.338631061@apps.rackspace.com> References: <1363879886.338631061@apps.rackspace.com> Date: Thu, 21 Mar 2013 11:47:45 -0400 X-Google-Sender-Auth: VwhdsWq9qhlG5hjWLX0XF-0BsFc Message-ID: From: Jim Gettys To: David P Reed Content-Type: multipart/alternative; boundary=089e015386d8870bad04d87142cc Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Buffalo WZR-600DHP (updated WZR-HP-AG300H) 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, 21 Mar 2013 15:47:47 -0000 --089e015386d8870bad04d87142cc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Mar 21, 2013 at 11:31 AM, wrote: > Down at the local Cambridge Micro Center there is a whole pile of new > 3800's. But knowing what Netgear does, this might be a completely > different hardware platform that is incompatible. How does one tell that > it's the right version, in case I want to buy another... (don't know at > this time if I do). > We've only seen one variant of the 3800, so we expect they should be fine. > > > Honestly, my main interest is that I'd like to see 802.11ac supported on > one of the new routers from Netgear or Cisco - but I suspect that the > drivers are probably not easy to get working on Linux. > The thing to do is to find routers based on the Qualcomm Atheros chipset: they've been best about Linux support in open source (as opposed to binary blobs to fit into specific versions of Linux). Even then, validating the driver is a significant amount of work. In the last couple years, broadcom open source driver support has improved, but IIRC, it is still a softmac device and has a blob of firmware, that is not trustworthy. - Jim > > > > > > > > > > -----Original Message----- > From: "Dave Taht" > Sent: Thursday, March 21, 2013 11:19am > To: cerowrt-devel@lists.bufferbloat.net > Subject: [Cerowrt-devel] Buffalo WZR-600DHP (updated WZR-HP-AG300H) > > Given how difficult it is becoming to get 3800s, a device with the > most similar chipset is this one. > > Anyone tried it? They were in use at the other two openwrt based demos at > ietf. > > I am working on getting a steady supply of 3800 refurbs and on other > alternative hardware. > > I note that unless major bugs show up in cerowrt, I'm not planning on > spinning up a new dev cycle until after Linux 3.8 is stable-ish > ... and not until after someone else steps up to be the new > buildmaster, and not until supplies of something suitable are assured. > > About the only major cerowrt thing I need to do in the coming weeks is > start pushing up the stuff to openwrt that works, maybe getting it > also into hipnet, and getting cake restarted. > > As I'll be travelling for the next 2 months - I kind of expect most of > what I'll be coding is prototyping code on x86, if that. > > (note - that doesn't mean development and CI are going to stop, > (although I do need a break), it just means I'm hoping you all enjoy > the current release as is, more than constantly upgrading.) > > Certainly get your feature requests in! What else needs to get into > this puppy to make it rock on ipv6 and naming and bufferbloat and > whatever else you need? > > -- > Dave T=E4ht > > Fixing bufferbloat with cerowrt: > http://www.teklibre.com/cerowrt/subscribe.html > _______________________________________________ > 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 > > --089e015386d8870bad04d87142cc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Thu= , Mar 21, 2013 at 11:31 AM, <dpreed@reed.com> wrote:

Down at the local Cambridge Micro Center there is a whol= e pile of new 3800's.=A0 But knowing what Netgear does, this might be a= completely different hardware platform that is incompatible.=A0 How does o= ne tell that it's the right version, in case I want to buy another...= =A0 (don't know at this time if I do).


We've only seen one variant of the 3800, so we expect th= ey should be fine.

=A0

Honestly, my main interest is that I'd = like to see 802.11ac supported on one of the new routers from Netgear or Ci= sco - but I suspect that the drivers are probably not easy to get working o= n Linux.


The thing to do is to find routers based on the Qualcomm Ath= eros chipset: they've been best about Linux support in open source (as = opposed to binary blobs to fit into specific versions of Linux). Even then,= validating the driver is a significant amount of work.

In the last couple years, broa= dcom open source driver support has improved, but IIRC, it is still a softm= ac device and has a blob of firmware, that is not trustworthy.
=A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 - Jim

=A0

=A0

=A0

=A0

=A0

-----Original Message-----
From: "D= ave Taht" <dave.taht@gmail.com>
Sent: Thursday, March 21, 2013 11:19am
T= o: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Buffalo WZR-600DHP (updated WZR-HP-AG300H)

=

Given how difficult it is becoming to get 3= 800s, a device with the
most similar chipset is this one.

Anyone = tried it? They were in use at the other two openwrt based demos at ietf.
I am working on getting a steady supply of 3800 refurbs and on otheralternative hardware.

I note that unless major bugs show up in cero= wrt, I'm not planning on
spinning up a new dev cycle until after Lin= ux 3.8 is stable-ish
... and not until after someone else steps up to be the new
buildmaster,= and not until supplies of something suitable are assured.

About the= only major cerowrt thing I need to do in the coming weeks is
start push= ing up the stuff to openwrt that works, maybe getting it
also into hipnet, and getting cake restarted.

As I'll be travell= ing for the next 2 months - I kind of expect most of
what I'll be co= ding is prototyping code on x86, if that.

(note - that doesn't m= ean development and CI are going to stop,
(although I do need a break), it just means I'm hoping you all enjoythe current release as is, more than constantly upgrading.)

Certain= ly get your feature requests in! What else needs to get into
this puppy = to make it rock on ipv6 and naming and bufferbloat and
whatever else you need?

--
Dave T=E4ht

Fixing bufferbloat= with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
____= ___________________________________________
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


--089e015386d8870bad04d87142cc--