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 10:29:52 +0100 Message-ID: <87tvvchqi7.fsf@gmail.com> References: <87shc2c3fh.fsf@gmail.com> <20180122211500.GA2400@jurong> <20180122225127.28494aa4@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51133) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edutz-00079T-Kx for guix-devel@gnu.org; Tue, 23 Jan 2018 04:30:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edutv-0003HQ-Mb for guix-devel@gnu.org; Tue, 23 Jan 2018 04:29:59 -0500 Received: from mail-wr0-x232.google.com ([2a00:1450:400c:c0c::232]:41570) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1edutv-0003Gz-Ff for guix-devel@gnu.org; Tue, 23 Jan 2018 04:29:55 -0500 Received: by mail-wr0-x232.google.com with SMTP id v15so8879225wrb.8 for ; Tue, 23 Jan 2018 01:29:55 -0800 (PST) In-reply-to: <20180122225127.28494aa4@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 Hi Danny, > I've also tested our new "--system" facility which allows us to build the > ARM image on x86_64 - but I'm sad to say that glibc has a bug which makes > the build fail > . Oh too bad :( > We could add a new argument to the kernel command line, or fish the tty > out of the existing "console" kernel argument. > > We can boot the system via the vendor's u-boot (all ARM systems I've used > have one) and our Linux kernel & GNU system. > > In the booted system, one can then reconfigure with u-boot (or not). > > That way, we'd have only one ARM image for all ARM (v7) systems. The problem with the approach of no writing u-boot is when you're preparing a blank SD card and expect to boot from it. However, I agree we could try to generalize the agetty configuration part by fishing the right console to user. An other problem would be in the initrd were some target specific module can be required to mount the rootfs ("omap_hsmmc" on BBB for example). WDYT ? Thanks, Mathieu