Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	"babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<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:04:48 +0200	[thread overview]
Message-ID: <87mvma26gf.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <0173B4D2-C84A-4200-B388-F8E964CAEB86@gmail.com>

> They can both run armhf userspace,

Just to make sure the audience is not confused: the Raspberry Pi 1 cannot
run Debian armhf, which requires ARMv7.  It can run either Debian armel,
which doesn't use floating point, or Raspbian, which is Debian recompiled
for ARMv6 with hardware floating point.

> I agree however that none of the R-Pis make good routers at the performance
> levels we want.  They just don’t have the right kind of I/O: we need
> direct or PCIe attachment of Ethernet and wifi MACs, not USB and SDIO.

Agreed.  Who's going to save us?

-- Juliusz

  reply	other threads:[~2016-06-24 11:05 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 [this message]
2016-06-24 16:36                   ` Eric Johansson
2016-06-24 20:27                     ` David Lang
     [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=87mvma26gf.wl-jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.univ-paris-diderot.fr \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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