From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Why we are discussing ARM
Date: Fri, 24 Jun 2016 10:10:57 -0400 [thread overview]
Message-ID: <D5748C04-6C06-4E93-AD24-96B31B571CBC@gmail.com> (raw)
In-Reply-To: <mailman.1398.1466735830.3642.cerowrt-devel@lists.bufferbloat.net>
To avoid us wasting time on an unsuitable candidate, I want to un-recommend the WiTi Board from www.mqmaker.com. Although it was designed for good performance and attractive price, it has a couple serious flaws:
- Wrong architecture - ramips/mt7621
- Flakey company - they met their kickstarter goal, and shipped units. But I think they set their unit price too low, and now don't have any extra dough left over to support the product.
I own one, it works fine in my limited testing. But I am not buying another...
Rich
parent reply other threads:[~2016-06-24 14:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.1398.1466735830.3642.cerowrt-devel@lists.bufferbloat.net>]
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=D5748C04-6C06-4E93-AD24-96B31B571CBC@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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