From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: wip-armhf branch ready for wider testing
Date: Mon, 19 Jan 2015 13:16:51 -0500 [thread overview]
Message-ID: <87bnluws8c.fsf@netris.org> (raw)
In-Reply-To: <20150118221223.GA19598@debian> (Andreas Enge's message of "Sun, 18 Jan 2015 23:12:23 +0100")
Andreas Enge <andreas@enge.fr> writes:
> On Sat, Jan 03, 2015 at 08:09:42PM +0100, Ludovic Courtès wrote:
>> Congrats on all the progress made!
>
> These are good news indeed!
>
>> It would be nice to have a couple of build machines for this platform.
>> If anyone reading this wants to help, please let us know!
>
> On which kind of machines does this armhf run? Is it related to the output
> of "uname -m"?
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".
> I have a raspberry pi that identifies as "armv6l", and a seagate
> goflex that identifies as "armv5tel". I suppose both are too old to
> run armhf?
Right, they can't run armhf. Also, a build slave should have 1 GB RAM
minimum (preferably 2) and reasonably well performing storage (i.e. SATA
not SD). So, I think Beaglebone Black and other systems in that class
will not be sufficient.
I think we need ARM board(s) with performance comparable to the Novena.
The Novena itself would be a fine option, but I'm not willing to give
mine up for that task :)
Mark
next prev parent reply other threads:[~2015-01-19 18:17 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 [this message]
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
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnluws8c.fsf@netris.org \
--to=mhw@netris.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).