From: Danny Milosavljevic <dannym@scratchpost.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gnu/system/u-boot.scm
Date: Fri, 22 Jul 2016 20:21:57 +0200 [thread overview]
Message-ID: <20160722202157.68317e11@scratchpost.org> (raw)
In-Reply-To: <87wpke3se1.fsf@gmail.com>
Hi,
On Fri, 22 Jul 2016 02:59:34 -0700
Chris Marusich <cmmarusich@gmail.com> wrote:
> I'm not familiar with u-boot, but based on recent emails, it sounds like it's important for getting GuixSD to run on ARM.
Yeah, because many ARM platforms don't have a BIOS (or any similar replacement), the bootloader has to do things you wouldn't believe. U-Boot has support for that.
There would be support for Grub as an U-Boot payload (in a fork), but I figured it's not really necessary [for now?] and complicates things too much - see how similar the U-Boot config body is to the Grub config body...
> I wonder if it would be possible to create a bootloader abstraction of
> some kind so that the installation mechanism can work with either u-boot
> or grub, without caring about which one it uses? It would be nice if
> the installation mechanism were generic enough so that the same
> mechanism could be used to install either bootloader.
That would be nice. I'm not sure whether different bootloaders are similar in their installation mechanism, though.
ARM platforms have... weird ways of booting - so getting all ARM boards to boot in the first place is difficult. Supporting those and Grub should be easy afterwards.
> > (define-record-type* <u-boot-configuration>
> > u-boot-configuration make-u-boot-configuration
> > u-boot-configuration?
> > (board u-boot-configuration-board) ; string ; not optional!
> > (u-boot u-boot-configuration-u-boot ; package
> > (default (@ (gnu packages u-boot) (make-u-boot-package board))))
> > (device u-boot-configuration-device) ; string
> > (menu-entries u-boot-configuration-menu-entries ; list
> > (default '()))
> > (default-entry u-boot-configuration-default-entry ; integer
> > (default 0))
> > (timeout u-boot-configuration-timeout ; integer
> > (default 5)))
>
> This looks a little different from the grub-configuration record type
> (defined in guix/gnu/system/grub.scm).
It should be very similar.
I added "board" and removed the theme stuff since it's unsupported. I don't think leaving the theme stuff in there would hurt either - it would just be ignored.
>How do you intend to integrate it with the existing bootloader installation mechanism?
I have no idea yet. Have to read up on what's there first :)
next prev parent reply other threads:[~2016-07-22 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 20:35 gnu/system/u-boot.scm Danny Milosavljevic
2016-07-22 9:59 ` gnu/system/u-boot.scm Chris Marusich
2016-07-22 18:21 ` Danny Milosavljevic [this message]
2016-07-26 20:49 ` gnu/system/u-boot.scm Ludovic Courtès
2016-07-27 9:32 ` gnu/system/u-boot.scm Danny Milosavljevic
2016-07-27 20:29 ` guix bootloader selection - wip patch Danny Milosavljevic
2016-07-28 12:34 ` Ludovic Courtès
2016-07-29 8:21 ` Danny Milosavljevic
2016-08-02 9:49 ` Ludovic Courtès
2016-08-02 9:49 ` Ludovic Courtès
2016-07-28 12:26 ` gnu/system/u-boot.scm Ludovic Courtès
2016-10-06 8:12 ` gnu/system/u-boot.scm Danny Milosavljevic
2016-10-06 17:24 ` gnu/system/u-boot.scm David Craven
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=20160722202157.68317e11@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=cmmarusich@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 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).