Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 77A4EC433EF for ; Wed, 19 Jan 2022 08:09:28 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 40591835CA; Wed, 19 Jan 2022 09:09:26 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=walle.cc Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; secure) header.d=walle.cc header.i=@walle.cc header.b="I4FvooE3"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 1A00B8319C; Wed, 19 Jan 2022 09:09:24 +0100 (CET) Received: from ssl.serverraum.org (ssl.serverraum.org [IPv6:2a01:4f8:151:8464::1:2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 91E42837CB for ; Wed, 19 Jan 2022 09:09:21 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=walle.cc Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=michael@walle.cc Received: from mwalle01.kontron.local. (unknown [213.135.10.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 6855D223EF; Wed, 19 Jan 2022 09:09:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1642579759; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=i0hTvZPmKl9SmMepmuImS9PbTI2EP1p0GDrVTDAQosI=; b=I4FvooE3IF6FLffKOYCYuFhVfSmmJXf8WJDO99p1B2q0ywzpTxNETYh7Vs5Mo9h/1PNvLo WPLFnblm0zZAi4kAKr0ldCf6bMvNa9uuE4WgTlYnt6Togv9HalBZf3k0iSdsRPcxTSD79C mmc6bfu6j6DLpzmpmABj2Z8gWKCSkec= From: Michael Walle To: sjg@chromium.org Cc: daniel.schwierzeck@gmail.com, dennis@ausil.us, ilias.apalodimas@linaro.org, jaeckel-floss@eyet-services.de, jh80.chung@samsung.com, lukas.auer@aisec.fraunhofer.de, marex@denx.de, michal.simek@xilinx.com, morpheus.ibis@gmail.com, peng.fan@nxp.com, trini@konsulko.com, u-boot@lists.denx.de, xypron.glpk@gmx.de, Michael Walle Subject: Re: [PATCH v3 00/31] Initial implementation of standard boot Date: Wed, 19 Jan 2022 09:09:08 +0100 Message-Id: <20220119080908.2899725-1-michael@walle.cc> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220119014315.1938157-1-sjg@chromium.org> References: <20220119014315.1938157-1-sjg@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean > The bootflow feature provide a built-in way for U-Boot to automatically > boot an Operating System without custom scripting and other customisation. > This is called 'standard boot' since it provides a standard way for > U-Boot to boot a distro, without scripting. > > It introduces the following concepts: > > - bootdev - a device which can hold a distro > - bootmeth - a method to scan a bootdev to find bootflows (owned by > U-Boot) > - bootflow - a description of how to boot (owned by the distro) > > This series provides an implementation of these, enabled to scan for > bootflows from MMC, USB and Ethernet. It supports the existing distro > boot as well as the EFI loader flow (bootefi/bootmgr). It works > similiarly to the existing script-based approach, but is native to > U-Boot. > > With this we can boot on a Raspberry Pi 3 with just one command: > > bootflow scan -lb > > which means to scan, listing (-l) each bootflow and trying to boot each > one (-b). The final patch shows this. I wanted to give this a try, but I only get the following output: => setenv boot_targets usb0 => bootflow scan -lb Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Unknown seq 0 for label 'usb0' --- ----------- ------ -------- ---- ------------------------ ---------------- (0 bootflows, 0 valid) where usb0 is a debian installation medium. -michael