From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 7D160E00CED; Tue, 1 Sep 2015 02:51:27 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.119 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx3.mail.bg (mx3.mail.bg [193.201.172.119]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 577F5E00AC1 for ; Tue, 1 Sep 2015 02:51:25 -0700 (PDT) Received: from [192.168.1.51] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx3.mail.bg (Postfix) with ESMTPSA id 827C22052F54; Tue, 1 Sep 2015 12:48:29 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1441100909; bh=0+rDDmsBGa6h/kLqePcZHUP7rO85NhH0rfF8V/GKGMc=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Fsmjpkt0E6U1uvILlYiW/k5V8D30cJrFtXR7fkE+mir9XU+ULIA6LrdmBMFNOSOQp wJDYOWcE8WNUpsquIwh8egrE4S4fSTJ/FUMEvaJOfM49nzIit/N0HApQxxGT5QsrYW OcojNr4SRxMZbfpxSI6zQ6LNDQXUtxsTSDZ/6YFE= Message-ID: <55E5746D.4050307@mail.bg> Date: Tue, 01 Sep 2015 12:48:29 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Otavio Salvador , Otavio Salvador References: <1440801304-11423-1-git-send-email-picmaster@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm][RFC][PATCH] image_types_fsl: Add extlinux support X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 09:51:27 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Otavio, On 08/31/2015 10:28 PM, Otavio Salvador wrote: > Hello Nikolay, > > (pressed too soon, Send) > > On Mon, Aug 31, 2015 at 1:27 PM, Otavio Salvador > wrote: >> On Fri, Aug 28, 2015 at 7:35 PM, Nikolay Dimitrov wrote: >>> Add support for booting via extlinux. This feature is supported only for U-Boot. >>> Here is how it works - during boot U-Boot scans through a list of boot drives >>> to find a partition containing the extlinux config file (this partition >>> should be either marked as a bootable, or should be the 1st one of all the >>> non-bootable partitions on the disk). The extlinux.conf file should be located >>> on one of the following paths: >>> >>> /boot/extlinux/extlinux.conf >>> /extlinux/extlinux.conf >>> >>> This patch uses the /extlinux/extlinux.conf path, in order to avoid funny paths >>> (/boot/boot/...) if later the vfat bootable partition needs to be mounted >>> (usually done at /boot). >>> >>> Here's an example extlinux.conf: >>> >>> default yocto >>> label yocto >>> kernel /zImage >>> devicetree /imx6dl-riotboard.dtb >>> append console=ttymxc1,115200 root=/dev/mmcblk0p2 rw >>> >>> And this is an example machine.conf that can use extlinux boot mechanism: >>> >>> EXTLINUX_CONF = "yes" >>> EXTLINUX_DEVICETREE = "imx6dl-riotboard.dtb" >>> EXTLINUX_CONSOLE = "ttymxc1,115200" >>> EXTLINUX_ROOTDEV = "/dev/mmcblk0p2 rw" >>> >>> Advantages: >>> - Boot parameters are not hardcoded in the bootloader and can be managed by >>> userspace tools (including package managers) >>> - One board can have multiple boot configurations >>> - Others? >>> >>> Disadvantages: >>> - My patch generates a simplified extlinux.conf with only 1 boot configuration. >>> Would be nice if we can have board-specific extlinux.conf, but I couldn't >>> find a proper way to do it >>> - Boot params (devicetree, console) are duplicated because the extlinux/kernel >>> needs them in a format different from the existing in the machine.conf >>> - Others? >>> >>> Signed-off-by: Nikolay Dimitrov >> >> First I would like to thank you > > ... for working on this. > > This is something we should really get moving and this is a very good base. > > However, I think we ought to reuse the syslinux class for this. Is it > possible for you to take a look on this? Sure, I'll look at it. Regards, Nikolay