Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
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] Cross-compiling to armhf [was: beaglebone green wireless boards...]
Date: Fri, 24 Jun 2016 02:20:17 +0300	[thread overview]
Message-ID: <1BA20F0C-953C-4296-92D0-B35596ACD249@gmail.com> (raw)
In-Reply-To: <87oa6rpl7h.wl-jch@pps.univ-paris-diderot.fr>


> On 24 Jun, 2016, at 01:57, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
> 
>> the long slow EABI changeover that was obsoleted almost overnight by the
>> armhf work the raspian folk did, and so on.
> 
> I am pretty positive that armhf predates raspbian.  Let's please give
> credit where credit is due.

Ironically, it was I who demonstrated to the Raspbian folks the benefits of an armhf build for the R-Pi 1, back in the early days of that platform.  It seems like an awfully long time ago now.  :-)

I did it by building Gentoo in armhf mode - *on* my R-Pi 1 - and distributing the ready-built rootfs.  To do this, I simply started from a softfp Gentoo build, and rebuilt it from the ground up using the Stage 1 bootstrap method.  All the tools and support simply worked from that point on.

At the time, ARMv7 distros were already typically built in armhf mode, but ARMv6 machines were usually expected to use softfp (or even softfloat) builds originally intended for ARMv5.  Since the R-Pi was obviously going to be a “platform standard” and would always include an FPU, the effort of producing a proper ARMv6-hf build was justified.

 - Jonathan Morton


  parent reply	other threads:[~2016-06-23 23:20 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
     [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           ` Jonathan Morton [this message]
2016-06-23 23:27             ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] 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=1BA20F0C-953C-4296-92D0-B35596ACD249@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jch@pps.univ-paris-diderot.fr \
    /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