From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57476) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUpUF-0003td-Nr for guix-patches@gnu.org; Mon, 18 Jun 2018 04:26:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fUpUA-00025u-2r for guix-patches@gnu.org; Mon, 18 Jun 2018 04:26:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:46448) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fUpU9-00025l-UQ for guix-patches@gnu.org; Mon, 18 Jun 2018 04:26:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fUpU9-0007Lk-OJ for guix-patches@gnu.org; Mon, 18 Jun 2018 04:26:01 -0400 Subject: [bug#31416] [PATCH 3/4] bootloader: Add make-u-boot-bootloader. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20180511143515.23435-1-dannym@scratchpost.org> <20180511143652.26935-1-dannym@scratchpost.org> <20180511143652.26935-3-dannym@scratchpost.org> <87603rnbi5.fsf@gnu.org> <20180513125925.66a91367@scratchpost.org> <87in7qbppv.fsf@gnu.org> <20180514182953.3d4c4f3c@scratchpost.org> <87r2l8wmjk.fsf@gnu.org> <20180617022855.671a3ef6@scratchpost.org> <87in6hkvb2.fsf@gnu.org> <20180617234138.725002ef@scratchpost.org> Date: Mon, 18 Jun 2018 10:25:00 +0200 In-Reply-To: <20180617234138.725002ef@scratchpost.org> (Danny Milosavljevic's message of "Sun, 17 Jun 2018 23:41:38 +0200") Message-ID: <874li0y00z.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Danny Milosavljevic Cc: 31416@debbugs.gnu.org Hi Danny, Danny Milosavljevic skribis: > On Sun, 17 Jun 2018 22:33:05 +0200 > ludo@gnu.org (Ludovic Court=C3=A8s) wrote: [...] >> IOW, we could definitely take Buildroot as an inspiration (it=E2=80=99s = probably >> one of the best tools in this area), but maybe not reuse the actual >> files. > > The advantage if we reused the actual files is that we'd not have to main= tain > it so much ourselves. [...] > Next would be to find those in buildroot, extract the relevant informatio= n from their genimage.cfg and unify them. > But that's a little involved. A path would be: > > (1) Extract possible SYS_SOC and SYS_VENDOR from all u-boot Kconfigs > (2) Find out which u-boot defconfigs would lead to those u-boot Kconfigs > (3) Find out which buildroot defconfigs would lead to those u-boot defcon= figs > (4) Find out which buildroot board directory is used by each buildroot de= fconfig > (5) Extract the genimage.cfg from each such buildroot board directory > (6) Extract the u-boot installation specific parts from the genimage.cfg > (7) Unify the set of "genimage.cfg" parts for this SOC and make sure they= are always the same Sounds like a plan. Though honestly, I think it=E2=80=99s fine if we have fewer configs availab= le as long as they=E2=80=99re known good. It=E2=80=99s not a goal IMO to have as= many supported boards as Buildroot. So I=E2=80=99d suggest defining the API and using it, taking inspirat= ion from those genimage.cfg files as needed. Thanks, Ludo=E2=80=99.