all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Jookia <166291@gmail.com>
Cc: 22384@debbugs.gnu.org
Subject: bug#22384: Requirements for an ARM port?
Date: Sun, 17 Jan 2016 10:10:27 +0200	[thread overview]
Message-ID: <20160117101027.65088e3b@debian-netbook> (raw)
In-Reply-To: <20160116102726.GA4482@novena-choice-citizen.lan>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Sat, 16 Jan 2016 21:27:26 +1100
Jookia <166291@gmail.com> wrote:

> Hey there,
> 
> I'm considering seeing if I can get GuixSD to work on an ARM board of mine. I'd
> like to know what the main blockers are that I'll need to pass. From what I've
> read and understood, the reason there's no ARM port now is lack of work and
> reliance on GRUB. Assuming I bootstrap and set up a u-boot package for my
> specific board, what else would I need to do?
> 
> Cheers,
> Jookia.
> 

According to the documentation, the arm board needs to be armv7 or later, and
support hard float, thumb-2, NEON, and support the EABI hard-float ABI.

I don't know a lot about setting up arm boards, but if I understand it
correctly, u-boot -> kernel -> guixsd image, where u-boot and the kernel get
updated in tandem.

I wish you much luck with getting GuixSD to run on an arm board, I think many
of us are looking forward to this working.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-17  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 10:27 bug#22384: Requirements for an ARM port? Jookia
2016-01-17  8:10 ` Efraim Flashner [this message]
2016-01-17 20:39 ` Ludovic Courtès
2016-01-17 21:01   ` Jookia
2016-01-18  8:03     ` Ludovic Courtès
2018-01-15 16:58 ` Mathieu Lirzin
2018-01-17 14:02   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160117101027.65088e3b@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=166291@gmail.com \
    --cc=22384@debbugs.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 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.