unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jookia <166291@gmail.com>
Cc: 22384@debbugs.gnu.org
Subject: bug#22384: Requirements for an ARM port?
Date: Sun, 17 Jan 2016 21:39:24 +0100	[thread overview]
Message-ID: <87h9ic54ar.fsf@gnu.org> (raw)
In-Reply-To: <20160116102726.GA4482@novena-choice-citizen.lan> (Jookia's message of "Sat, 16 Jan 2016 21:27:26 +1100")

Jookia <166291@gmail.com> skribis:

> 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?

I think getting a working bootloader and kernel are the main blockers
(the current ‘linux-libre’ package might work already, or it might need
more tweaks; I don’t think anyone has tried to boot it on ARM.)

I would prefer if we could use GRUB with ARM support¹ if possible.
Using U-Boot would be OK if GRUB doesn’t work as expected, but it’s more
work; namely, a module equivalent to (gnu system grub) would need to be
made, and (gnu system) would need to be made independent of GRUB.

At any rate, GuixSD on ARM would be very nice!

Ludo’.

¹ https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB (GRUB 2.02 should
  work)

  parent reply	other threads:[~2016-01-17 20:40 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
2016-01-17 20:39 ` Ludovic Courtès [this message]
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

  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=87h9ic54ar.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 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).