From: Jim Gettys <jg@freedesktop.org>
To: David P Reed <dpreed@reed.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Buffalo WZR-600DHP (updated WZR-HP-AG300H)
Date: Thu, 21 Mar 2013 11:47:45 -0400 [thread overview]
Message-ID: <CAGhGL2DPMXb715KtibXjuB_tcxV9kZ7cUrhwyEmDYR1KwCyihw@mail.gmail.com> (raw)
In-Reply-To: <1363879886.338631061@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 3180 bytes --]
On Thu, Mar 21, 2013 at 11:31 AM, <dpreed@reed.com> 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" <dave.taht@gmail.com>
> 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äht
>
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 5231 bytes --]
next prev parent reply other threads:[~2013-03-21 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 15:19 Dave Taht
2013-03-21 15:31 ` dpreed
2013-03-21 15:47 ` Jim Gettys [this message]
2013-03-21 16:13 ` Richard A. Smith
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=CAGhGL2DPMXb715KtibXjuB_tcxV9kZ7cUrhwyEmDYR1KwCyihw@mail.gmail.com \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.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