From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Go in ptxdist
Date: Thu, 6 Oct 2016 12:04:00 +0200 [thread overview]
Message-ID: <ccf85fba-093d-fb55-08ca-aa131572d6f2@pengutronix.de> (raw)
In-Reply-To: <20161006063332.6emfdkityxiyf3lc@pengutronix.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 1799 bytes --]
On 10/06/2016 08:33 AM, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, Oct 05, 2016 at 05:55:10PM +0200, Clemens Gruber wrote:
>> They write: "ARM on Linux. You must run an EABI kernel. These are
>> generally known as armel for softfloat (compatible with ARMv5) or armhf
>> for hardware floating point (ARMv6 and above)."
>
> At least for Debian an ARMv6 compatible CPU (e.g. Raspberry Pi 1) cannot
> run armhf. According to https://www.debian.org/ports/:
Cannot run debian's flavour of armhf, as it uses vp3 und thumb-2"
> A lot of modern 32-bit ARM boards and devices ship with a
> floating-point unit (FPU), but the Debian armel port doesn't
> take much advantage of it. The armhf port was started to improve
> this situation and also take advantage of other features of
> newer ARM CPUs. The Debian armhf port requires at least an ARMv7
> CPU with Thumb-2 and VFP3-D16 floating point support.
>> If you set GOARM to 6 or 7 it always creates hardfloat code. So I think,
>> setting it to anything else than 5 would lead to a crash on all
>> architectures without a VFP unit?
>
> Not necessarily. AFAIK given a properly configured kernel a hardfloat
> instruction generates an exception that is then fixed up in the kernel.
> It's not efficient but at least it works.
armel passes floating point values in the integer registers and debian's
armhf passes them in floating point registers. This means you cannot mix
and match armel and armhf, as the are ABI incompatible.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-10-06 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 15:23 Clemens Gruber
2016-10-05 13:13 ` Michael Olbrich
2016-10-05 15:55 ` Clemens Gruber
2016-10-05 16:31 ` Michael Olbrich
2016-10-05 20:42 ` Clemens Gruber
2016-10-06 9:17 ` Michael Olbrich
2016-10-07 16:47 ` Clemens Gruber
2016-10-07 18:37 ` Uwe Kleine-König
2016-10-11 16:18 ` Clemens Gruber
2016-10-12 0:07 ` Clemens Gruber
2016-10-06 6:33 ` Uwe Kleine-König
2016-10-06 10:04 ` Marc Kleine-Budde [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccf85fba-093d-fb55-08ca-aa131572d6f2@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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