all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jookia <166291@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Supporting non-GRUB bootloaders?
Date: Sun, 24 Jan 2016 21:58:24 +0100	[thread overview]
Message-ID: <878u3elmof.fsf@gnu.org> (raw)
In-Reply-To: <20160123222736.GA6896@novena-choice-citizen.lan> (Jookia's message of "Sun, 24 Jan 2016 09:27:36 +1100")

Jookia <166291@gmail.com> skribis:

> I'm interested to know how hard it'd be to support a non-GRUB bootloader, such
> as u-boot. On NixOS this is relatively easy, but I'm under the impression that
> on Guix this is borderline impossible due to hard coding.

GuixSD currently pretty much assumes GRUB, because it’s the GNU
bootloader and, one would hope, it does the job.

That said, the (gnu system grub) module is less than 300 lines.  Then
there are also assumptions in (guix scripts system) and (gnu system).

> I'd like to do this:
>
> * Copy initramfs and kernels to /boot.
> * Write a extlinux.conf file for U-Boot to read.
> * Not have GRUB installed or running.
>
> How hard would this be?

You would need a module similar to (gnu system grub) for U-Boot and a
U-Boot package.  The you would need to abstract things in the
aforementioned modules.

> My motivation is that GRUB on ARM doesn't work on my system (Novena)

Too bad.  Would be nice to see exactly what’s missing.

> so the next best thing is to use U-Boot.

Yeah.

Apparently GRUB can also be used on top of U-Boot, FWIW:
<https://wiki.linaro.org/LEG/Engineering/Kernel/GRUBonUBOOT>.

So I would suggest that you get started and let us know when you
encounter specific stumbling blocks!

HTH,
Ludo’.

      reply	other threads:[~2016-01-24 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 22:27 Supporting non-GRUB bootloaders? Jookia
2016-01-24 20:58 ` 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=878u3elmof.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=166291@gmail.com \
    --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 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.