From: Andy Shevchenko Date: Tue, 10 Mar 2020 16:51:27 +0200 Subject: [PATCH v3 0/7] x86: Improve support for chain-loading U-Boot In-Reply-To: <20200307232220.111052-1-sjg@chromium.org> References: <20200307232220.111052-1-sjg@chromium.org> Message-ID: <20200310145127.GP1922688@smile.fi.intel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sat, Mar 07, 2020 at 04:22:13PM -0700, Simon Glass wrote: > This little series adds a few checks into the code to allow better > operation when booting a build from a previous-state loader such as > coreboot. > > At present we have a 'coreboot' target but this runs very different code > from the bare-metal targets, such as coral. There is very little in common > between them. > > It is useful to be able to boot the same U-Boot on a device, with or > without a first-stage bootloader. For example, with chromebook_coral, it > is helpful for testing to be able to boot the same U-Boot (complete with > FSP) on bare metal and from coreboot. It allows checking of things like > CPU speed, comparing registers, ACPI tables and the like. > > This series allows U-Boot to detect that it ran from coreboot and > automatically do the right thing. > > This series makes the most important changes to allow the same u-boot.bin > for coral to boot after coreboot (by itself) or bare metal (via TPL->SPL). I see only this and one patch out of 7 (seven?). Please, (re)send it correctly. -- With Best Regards, Andy Shevchenko