From: Julien Lepiller <julien@lepiller.eu>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: wip blog post (v2): running Guix System on ARM
Date: Sun, 17 Nov 2019 17:57:28 +0100 [thread overview]
Message-ID: <20191117175720.071cd6b3@sybil.lepiller.eu> (raw)
In-Reply-To: <20191114131211.12ba9267@scratchpost.org>
Le Thu, 14 Nov 2019 13:12:11 +0100,
Danny Milosavljevic <dannym@scratchpost.org> a écrit :
> Hi Julien,
>
> On Wed, 13 Nov 2019 22:21:54 +0100
> Julien Lepiller <julien@lepiller.eu> wrote:
>
> > Hi, attached is a draft for a blog post (or a section in the
> > cookbook) for explaining how to install the Guix System on an ARM
> > board. WDYT?
>
> I guess it can't hurt to describe this stuff as it works now, but the
> goal is not to need to do any of this complicated stuff--and there's
> no fundamental reason why one would have to. There are projects like
> buildroot which have all the u-boot configuration (and more--like the
> partitioning, which also can sometimes have funny requirements, for
> example on Allwinner) that Guix could import to generically install
> Guix on any ARM board. Eventually there will be an importer for those.
>
> The kernel module situation is awful. It would be good if we could
> automate it more in the future (if the information is statically
> available in the first place). If the foreign distribution doesn't
> have it, not much can be done.
>
> I'm not sure what buildroot does--whether we have kernels with
> different built-in modules for different modules or what?
>
> Some comments on your draft:
>
> (1) You absolutely can use an existing u-boot to boot Guix (bugs
> nonwithstanding). Guix only generates "extlinux.conf" and doesn't
> touch the other u-boot config. The default u-boot-bootloader
> installer (as opposed to config installer) is "do nothing". So your
> existing u-boot (for example in NAND flash) would display a boot menu
> and then you could boot from SSD or SD, for example. If this doesn't
> work, please file a bug report. Also, the old generations should be
> able to be selected, too. Doesn't it work?
>
> FWIW, I'm also using an existing Grub inside Libreboot to boot Guix
> on X86, with exactly the same mechanism (grub.conf generated,
> grub-install not invoked).
>
> (2) If possible, can you mention that non-exported, non-documented
> variables are subject to change? I mean I like that "@@" is
> possible, but let's make sure the user knows that it would be better
> to contact us for including his stuff if it's supposed to continue to
> work.
Thank you! attached is a new version of that blog post. I think I'll
convert it to texinfo and add it to the cookbook, instead of making it
a blog post, as we then could change or remove it more easily if we
make progress on this :)
I've changed the first paragraph of the u-boot section and the comment
before using @@. I also fixed a few typos others found. If it looks
good, I'll push the change to master in a few days.
next prev parent reply other threads:[~2019-11-17 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 21:21 wip blog post: running Guix System on ARM Julien Lepiller
2019-11-14 9:10 ` Giovanni Biscuolo
2019-11-14 9:29 ` Pierre Neidhardt
2019-11-14 10:32 ` zimoun
2019-11-14 11:05 ` pelzflorian (Florian Pelz)
2019-11-17 16:53 ` Julien Lepiller
2019-11-17 19:39 ` Ludovic Courtès
2019-11-14 12:12 ` Danny Milosavljevic
2019-11-17 16:57 ` Julien Lepiller [this message]
2019-11-18 17:03 ` wip blog post (v2): " Danny Milosavljevic
2019-11-23 17:19 ` Ludovic Courtès
2019-11-24 7:56 ` Julien Lepiller
2019-11-17 19:37 ` wip blog post: " Ludovic Courtès
2019-11-17 19:43 ` Ludovic Courtès
2019-11-18 8:25 ` Pjotr Prins
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=20191117175720.071cd6b3@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=dannym@scratchpost.org \
--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).