Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] WNDR alternative for higher capacity
Date: Sun, 9 Feb 2014 11:06:04 -0800	[thread overview]
Message-ID: <CAA93jw6fXwQZ7kghkJCtn76A1b9d0RX3YO2cr_Bj2OhG4zP8yw@mail.gmail.com> (raw)
In-Reply-To: <874n486rxe.fsf@toke.dk>

Rich Brown had contacted linksys. I don't know the current status.

So far we're not impressed with their follow through, or their
announcement, or their hardware. They seemed to think that merely
announcing they'd work with openwrt precluded things like, actually
contacting the openwrt devs to talk about their plans. This is the
rough equivalent of someone announcing a product that Apple would
support, without Apple;s actual endorsement.

Certainly linksys was a powerful brand and many folk have warm
feelings about their breakthrough new products in the early 00s, but
the company was a gutted shell long before it was sold off.

Over the past year...

I have had plenty of "early hardware" from various vendors to
evaluate, all rejected thus far, primarily due to the binary blob
problem. Some had pretty good kernel support, but rejected (like the
mirabox) for heat and ancient kernel issues as well, and a couple got
rejected because they couldn't push even half a gigabit.

It's a rather long list of unacceptable hardware at this point. I can
try to sort through what I can and cannot publish and get it out here
at some  point.

Currently on the top of the "not so-horrible-I'm going-to-barf list"
is the latest arm based atheros CPU chipset and mildly below that is
the mindspeed stuff. Mindspeed got bought recently and that's taken it
out of the running until they get their internal processes sorted out
or sold again.

The atheros chipset is still hotly smoking off the fab... I've held a
dev board in my hands but they took it away from me real fast. :)

The octeon was a contender for a while but with the death of mips it's
time to leave that arch. The armada 370s are not bad, the imx6 stuff
is not bad (there's been some good changes on the imx6 I should look
at it again)

That's just for cpu.

In all cases from all vendors the 802.11ac radio code is in binary
blobs, and barely works in the first place. The ath10k work is
proceeding in public at least, but they are still battling with
blowing up on the PCIe bus and other
severely low level problems. Ath10k support HAS landed in openwrt....

At the moment what I think I'm trying to do is divide the problem in half,
find a decent X86 based box with mini-pcie support, and solve the
gigE problem that way, and the wifi problem separately.

The cost goes way up... The closest I've found so far to what I wanted
was the latest nuc with sata support. Still want two hardwired
ethernet ports which it doesn't have....



On Sun, Feb 9, 2014 at 10:51 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Bill Merriam <lists@billmerriam.com> writes:
>
>> The announced but not yet available Linksys WRT1900AC might meet your
>> needs. The press release says they are providing advance copies of the
>> hardware to the openwrt developers and linksys expects openwrt to
>> ready when the hardware is released in "Spring 2014".
>
> I think it might, and I considered that; but got stuck on the "announced
> but not yet available" part...
>
>> It seems cerowrt developers need early hardware also.
>
> Well, maybe I'll try to convince someone at linksys that this is the
> case; any ideas about who I should email?
>
> -Toke
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2014-02-09 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 21:22 Toke Høiland-Jørgensen
2014-02-08 22:45 ` Dave Taht
2014-02-08 23:22   ` Toke Høiland-Jørgensen
2014-02-08 23:32     ` Fred Stratton
2014-02-09 17:22 ` Bill Merriam
2014-02-09 18:51   ` Toke Høiland-Jørgensen
2014-02-09 19:06     ` Dave Taht [this message]
2014-02-09 19:18       ` Toke Høiland-Jørgensen
2014-02-09 19:38         ` Fred Stratton
2014-02-09 19:43           ` Fred Stratton
2014-02-09 19:45           ` Dave Taht
2014-02-09 19:56           ` Toke Høiland-Jørgensen
2014-02-09 20:10             ` Dave Taht
2014-02-10 13:14       ` Rich Brown

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=CAA93jw6fXwQZ7kghkJCtn76A1b9d0RX3YO2cr_Bj2OhG4zP8yw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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