From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: wip-armhf branch ready for wider testing
Date: Wed, 21 Jan 2015 15:59:02 +0100 [thread overview]
Message-ID: <87oapsw56x.fsf@gnu.org> (raw)
In-Reply-To: <873875vznr.fsf@netris.org> (Mark H. Weaver's message of "Tue, 20 Jan 2015 17:46:16 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> Our armhf targets the same set of machines as Debian's armhf, namely the
>>> ARMv7-A architecture with VFP3D16 coprocessor. So 'uname -m' must
>>> output "armv7l" or better, and I guess the processor "Features" as
>>> reported by /proc/cpuinfo must include "vfpv3" and either "vfpd16"
>>> or "vfpd32".
>>
>> Since it’s becoming a FAQ, could you add something along these lines to
>> the manual, right where armhf-linux is introduced?
>
> I already put this in the "GNU Distribution" node (chapter 6):
>
> The GNU distribution is currently available on the following
> platforms:
>
> [...]
>
> ‘armhf-linux’
> ARMv7-A architecture with hard float, Thumb-2 and VFP3D16
> coprocessor, using the EABI hard-float ABI, and Linux-Libre kernel.
>
> Do you think more is needed?
Perhaps in parentheses or in a footnote indicate what to look for in
“uname -m” and /proc/cpuinfo? WDYT?
Ludo’.
prev parent reply other threads:[~2015-01-21 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 22:39 wip-armhf branch ready for wider testing Mark H Weaver
2015-01-02 22:48 ` David Thompson
2015-01-03 19:09 ` Ludovic Courtès
2015-01-18 22:12 ` Andreas Enge
2015-01-19 18:16 ` Mark H Weaver
2015-01-19 20:10 ` Ludovic Courtès
2015-01-20 22:46 ` Mark H Weaver
2015-01-20 23:12 ` Daniel Pimentel
2015-01-21 14:59 ` Ludovic Courtès [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=87oapsw56x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.