From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Othacehe Subject: Re: Porting GuixSD to ARM article. Date: Tue, 23 Jan 2018 11:42:55 +0100 Message-ID: <87o9lkhn4g.fsf@gmail.com> References: <87shc2c3fh.fsf@gmail.com> <20180122211500.GA2400@jurong> <20180122225127.28494aa4@scratchpost.org> <87tvvchqi7.fsf@gmail.com> <20180123110410.17b55a5f@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edw2f-0001SG-DN for guix-devel@gnu.org; Tue, 23 Jan 2018 05:43:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edw2c-0004nB-B8 for guix-devel@gnu.org; Tue, 23 Jan 2018 05:43:01 -0500 Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]:43306) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1edw2c-0004mt-3q for guix-devel@gnu.org; Tue, 23 Jan 2018 05:42:58 -0500 Received: by mail-wm0-x235.google.com with SMTP id g1so869685wmg.2 for ; Tue, 23 Jan 2018 02:42:57 -0800 (PST) In-reply-to: <20180123110410.17b55a5f@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 > We could ship the generic ARM image, let the user use > qemu-system-arm to boot it and set up the correct u-boot in > there, and only then write it to SD card. > > There could even be a small part in the wip-installer-2 > that asks you which u-boot you want and set that up. > > I'm just trying to prevent Hydra from building ~1000 huge disk images > with minimal differences in the future... :) I agree a single ARMv7 would be better too :) On that point, NixOS seem to provide a generic image an gives the instructions to write the bootloader afterwards for every target: https://nixos.wiki/wiki/NixOS_on_ARM and here, https://nixos.wiki/wiki/NixOS_on_ARM/BeagleBone_Black I'm not found of this approach as it requires more manual steps but we could maybe try the same thing. What do other people think ? > Yeah, I saw that now. I wonder how to generalize that. Maybe try to > include a union of all possible boot-required modules? That would be tricky to create and maintain. Arch Linux does the same thing as NixOS and requires some specific manipulations for every supported platform: https://archlinuxarm.org/platforms Maybe we should look for a distribution that has a generic image with automatic initrd module list detection ? Thanks, Mathieu