From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] some very promising hardware in the pipeline
Date: Thu, 30 Jul 2015 07:05:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1507300703170.11810@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw5aBVezpf30ckzrzjx58KbJG6vs-3Aea50aHEK9Dx_2mw@mail.gmail.com>
On Wed, 29 Jul 2015, Dave Taht wrote:
> see: https://lite.turris.cz/en/
>
> As this is basically the same chipset as the linksys we are having
> successes with... AND it has several mini-pcie slots, making it
> possible to
> experiment with wifi... and the turris folk are more clued than anyone
> I've met of late... I am thinking that maybe, just maybe, we have a
> platform to base another cerowrt-like project on. That said, their
> existing openwrt derived OS could maybe, merely, need a few tweaks,
> here and there - they do remote updates! yea!
>
> * CPU Marvell Armada 385, dual core, 1.6 GHz
> * 1 GB DDR3L RAM
> * 2-4 GB eMMC + 8 MB NOR flash
> * gigabit WAN - dedicated interface in the CPU, switchable between RJ45
> and SFP (possibility of 2.5 Gbps, not tested)
> * 5x gigabit LAN (7 port switch Marvell connected with two gigabit lines
> into the processor)
> * 3x miniPCIe, one switchable to mSATA
> * optional wifi 2x2 MIMO b/g/n + 2x2 or 3x3 MIMO a/n/ac
> * 2x USB 3.0
> * RTC with battery backup
> * SIM card slot
> * dimmable RGB LED
I agree, this is extremely powerful hardware configuration with nothing I
can think of that is wrong with it. Just makes me worried about price
point. I'm worried this is going to be a USD200 device once it's done.
What is the SIM card used for? To put a mini-PCIE WWAN card on there?
--
Mikael Abrahamsson email: swmike@swm.pp.se
prev parent reply other threads:[~2015-07-30 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 12:10 Dave Taht
2015-07-30 5:05 ` Mikael Abrahamsson [this message]
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=alpine.DEB.2.02.1507300703170.11810@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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