From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: ARMHF flash image - Put on website under GuixSD Date: Mon, 10 Sep 2018 17:12:50 +0200 Message-ID: <20180910171250.6dc5dad8@scratchpost.org> References: <20180907222110.50e6bac2@scratchpost.org> <877ejth6yj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/AKdJ66/SwXEzVnan.R2Ouoy"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fzNsB-0007gy-OR for guix-devel@gnu.org; Mon, 10 Sep 2018 11:13:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fzNs6-0001NL-OZ for guix-devel@gnu.org; Mon, 10 Sep 2018 11:13:07 -0400 In-Reply-To: <877ejth6yj.fsf@gnu.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: Ludovic =?ISO-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org --Sig_/AKdJ66/SwXEzVnan.R2Ouoy Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ludo, On Mon, 10 Sep 2018 14:28:52 +0200 ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > > Can we put it on the website at https://www.gnu.org/software/guix/downl= oad/ > > inside the GuixSD part? > > > > I think it would be nice to have something ready-to-go for ARM systems = as well, > > and this would be a good start. Apart from the bootloader, everything = should > > work as-is in there. And the user can either keep the original bootloa= der > > on the board or flash a new one after booting GuixSD - either in qemu or > > on a real machine. =20 >=20 > I agree that it would be nice, but to what extent is this image generic > to all ARM boards? My understanding is that images are necessarily > bound to a specific board. Yes, but only because of the bootloader (that's a pretty big "but"). It's possible to change it inside qemu, and in the end there has to be *som= e* way for a user to bootstrap the things (usually using the vendor image). ARM boards are very diverse - some load the bootloader and the root fs from= SD card, some load the bootloader from flash and the root fs from SD card, some load everything from flash, some load the bootloader from flash and the root fs from NFS etc. In the end we can also provide one image per board, but we should use a block-deduplicating filesystem then - because everything but ~30 kB of each= image will be the same! >Other considerations include the fact that it=E2=80=99s yet another image = to >build when we make a release, but perhaps the solution is simply to >improve our automation and build farm availability. I think if we want to support it it has to be built at least once. Otherwise we don't know whether it has a chance to work, no? Having the flash-image isn't really much more work on top of that. --Sig_/AKdJ66/SwXEzVnan.R2Ouoy Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAluWifIACgkQ5xo1VCww uqWbkAf/WYJy8u1i5QCswIBPTPhvA55ZMbhUYtvIx6jwKR021jbEcJ0T8eLnKyM7 s8JjDcnDeHr0jqvx6X4RmdbuDDdfkM7l0hC17vZaNhAoPhUdv2vDkTeIz8iuCnH/ o1w3DdM0gQz8Ek7BO2DaPIXbe7CpG7pzSwT74WEI66nH+k++2l8Bgl5S4RDLBqrE 9IfJPlIQZZ/t5ygaiRk3BXN73A7YbdK5ZN593KFsBuhmT8E9B6Ij5w6qgAhLbEnV Jw4sNNojQOQbo1/su8GUadwNvtJaNQJR7gox/WX9VR1qOJljAv6nJ6AjKy7Aam/H wHmLe/usZBgL/Q+W1xxQKd5M45Jnzg== =PGLy -----END PGP SIGNATURE----- --Sig_/AKdJ66/SwXEzVnan.R2Ouoy--