From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>
Subject: Re: [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...]
Date: Thu, 23 Jun 2016 16:13:46 -0700 [thread overview]
Message-ID: <CAA93jw5gojjWGUSWD9uwqQ2yTOQ+YSmkuEzMLvB5hivAKP3R2g@mail.gmail.com> (raw)
In-Reply-To: <87oa6rpl7h.wl-jch@pps.univ-paris-diderot.fr>
On Thu, Jun 23, 2016 at 3:57 PM, 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.
I note that I *really like arm*, going back a very long ways.
http://the-edge.blogspot.com/2002/06/axioms-one-of-my-axioms-about.html
I remember telling the CTO of palm they were doomed back then... they
had started trying to differentiate models by *color* at that
point....
sure the abi and compiler "were out there" - but getting 20,000
packages converted over and widely into a popular distro and platform,
to me, was the tipping point for wider adoption of the hard float abi,
as something others could build on. I just spent a few minutes
googling for that story, but couldn't find it (what I remember was 3
guys, 3 months, hammering at getting 20,000 packages to all "just
work").
What we had before was a mess of different ABIs, and a whole bunch of
slightly incompatible arm cpu versions - all enough different to
fragment the arm ecosystem. there was no way you could trust one
binary on a different box. Back around this time (2006-2010?) it was
also unclear that arm would accellerate so far past the herd, either,
and there were a ton of other factors, of course that led to where
it's now being considered for supercomputers and looks set to start
unseating intel in many places.
And despite really liking arm, I look forward to entirely new arches
like the risc-v and mill eating its lunch one day. Things like
trustzone, the mali gpu, and other portions of onchip IP commonly
shipped with the chips suck rocks, still. Very few applications are
taking good advantage of the neon vfp code, the onboard caches are way
behind intel's, and so on...
speaking of trustzone - yea! there's a way to use it now.
https://github.com/OP-TEE
>
> -- Juliusz
--
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:13 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 [this message]
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
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=CAA93jw5gojjWGUSWD9uwqQ2yTOQ+YSmkuEzMLvB5hivAKP3R2g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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