From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
"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: Thu, 23 Jun 2016 16:27:55 -0700 [thread overview]
Message-ID: <CAA93jw4F=EThAaY3x9VN3GEDzQ9eYi41XNpEO5Fz9CsXJnQcJg@mail.gmail.com> (raw)
In-Reply-To: <1BA20F0C-953C-4296-92D0-B35596ACD249@gmail.com>
On Thu, Jun 23, 2016 at 4:20 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> 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. :-)
Yes, it was a group team of hackers going against the prevailing
wisdom of endless backward compatibility, and succeeding due to
technical excellence and demonstrable performance improvements -
that's why that story sticks with me. I admire anybody that can do
that. :)
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-06-23 23: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
[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 [this message]
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='CAA93jw4F=EThAaY3x9VN3GEDzQ9eYi41XNpEO5Fz9CsXJnQcJg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@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