Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Eric Johansson <esj@eggo.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Why we are discussing ARM [was: Cross-compiling to armhf]
Date: Fri, 24 Jun 2016 13:27:12 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1606241323310.2687@nftneq.ynat.uz> (raw)
In-Reply-To: <9a37f44d-7e6b-f31f-58ad-1dd7eac8ee71@eggo.org>

On Fri, 24 Jun 2016, Eric Johansson wrote:

> On 6/24/2016 7:04 AM, Juliusz Chroboczek wrote:
>> Agreed. Who's going to save us?
>
>  * kickstart our own,
>  * license a design and enhance it to our needs (rpi 4??)
>  * work a deal with mikrotek to freeup docs on one of their boards so
>    we can replace router os with one of our own. see
>    http://www.balticnetworks.com/mikrotik-hap-ac-lite-dual-band-indoor-access-point-built-in-antennas.html.

There are a number of mikrotik boards that are listed as having OpenWRT support, 
including one with 9 gig-e ports and 3 microPCI slots that can hold radios

http://routerboard.com/RB493G
http://routerboard.com/RB493AH

  reply	other threads:[~2016-06-24 20:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 23:54 [Cerowrt-devel] beaglebone green wireless boards now available Dave Taht
2016-06-22 11:31 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Juliusz Chroboczek
2016-06-22 12:08   ` [Cerowrt-devel] [Babel-users] " Benjamin Henrion
2016-06-22 13:10     ` [Cerowrt-devel] Cross-compiling to armhf Juliusz Chroboczek
2016-06-22 13:15       ` Benjamin Henrion
2016-06-22 20:38         ` Juliusz Chroboczek
2016-06-22 16:38   ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Dave Taht
2016-06-23 22:10     ` Juliusz Chroboczek
2016-06-23 22:45       ` Dave Taht
2016-06-23 22:57         ` Juliusz Chroboczek
2016-06-23 23:13           ` Dave Taht
2016-06-24  0:02             ` [Cerowrt-devel] Why we are discussing ARM [was: Cross-compiling to armhf] Juliusz Chroboczek
2016-06-24  2:37               ` Jonathan Morton
2016-06-24 11:04                 ` Juliusz Chroboczek
2016-06-24 16:36                   ` Eric Johansson
2016-06-24 20:27                     ` David Lang [this message]
     [not found]               ` <E1bH8oe-0000Wv-EO@stardust.g4.wien.funkfeuer.at>
2016-06-26 17:59                 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-06-26 19:02                   ` Baptiste Jonglez
2016-06-26 19:58                     ` Jonathan Morton
2016-06-26 20:03                     ` Juliusz Chroboczek
2016-06-23 23:20           ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Jonathan Morton
2016-06-23 23:27             ` Dave Taht
2016-06-23 23:42               ` Dave Taht
2016-06-24 16:25                 ` Eric Johansson

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.1606241323310.2687@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=esj@eggo.org \
    /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