From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: Re: wip blog post (v2): running Guix System on ARM Date: Sun, 17 Nov 2019 17:57:28 +0100 Message-ID: <20191117175720.071cd6b3@sybil.lepiller.eu> References: <20191113222154.6eb6a78c@sybil.lepiller.eu> <20191114131211.12ba9267@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36797) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iWNrg-0001xf-U0 for guix-devel@gnu.org; Sun, 17 Nov 2019 11:57:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iWNrf-00005L-OO for guix-devel@gnu.org; Sun, 17 Nov 2019 11:57:32 -0500 Received: from lepiller.eu ([2a00:5884:8208::1]:57898) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iWNrf-00004r-G3 for guix-devel@gnu.org; Sun, 17 Nov 2019 11:57:31 -0500 In-Reply-To: <20191114131211.12ba9267@scratchpost.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: guix-devel@gnu.org Le Thu, 14 Nov 2019 13:12:11 +0100, Danny Milosavljevic a =C3=A9crit : > Hi Julien, >=20 > On Wed, 13 Nov 2019 22:21:54 +0100 > Julien Lepiller wrote: >=20 > > 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? =20 >=20 > 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. >=20 > 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. >=20 > I'm not sure what buildroot does--whether we have kernels with > different built-in modules for different modules or what? >=20 > Some comments on your draft: >=20 > (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? >=20 > 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). >=20 > (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.