[PATCH v3 00/18] bootstd: Add a bootmeth for ChromiumOS on x86

[Tom Rini]

On Fri, Jul 14, 2023 at 05:29:40PM +0800, Bin Meng wrote:
> Hi Simon,
> 
> On Thu, Jul 13, 2023 at 9:14 PM Bin Meng <bmeng.cn at gmail.com> wrote:
> >
> > On Wed, Jul 12, 2023 at 11:04 PM Simon Glass <sjg at chromium.org> wrote:
> > >
> > > This series adds a simple bootmeth for ChromiumOS on x86. It uses zimage
> > > to boot the kernel.
> > >
> > > Full verified boot is not included at this stage - that is still a
> > > separate chunk of code to be brought into standard boot at some point.
> > > For now it just obtains the kernel and command line and boots. This should
> > > be enough to boot Chrome OS from coreboot on all x86 machines in
> > > circulation, although only Brya (2022) and Coral (2017) have been tested.
> > >
> > > ChromiumOS needs quite large kernel parameters, to hold the DM verity
> > > settings and other pieces. This makes it painful to modify just one
> > > parameter, since the whole cmdline must be adjusted at once. To cope with
> > > this, a new cmdline-editing feature is provided: the 'bootflow cmdline'
> > > command allows individual parameters to be added, modified and deleted.
> > >
> > > To deal with enabling debug console, a variant supports setting 'earlycon'
> > > and 'console' automatically. The 'bdinfo' command is updated to show
> > > serial-port info also.
> > >
> > > Booting the zimage is now done programmatically, rather than running
> > > through the command-line interface. Minor tweaks are made to the coreboot
> > > and coral config so that booting works correctly.
> > >
> > > Note that the ACPI tables are not updated with the required firmware
> > > information in this series, so a warning is shown on boot. This will be
> > > addressed later since it requires quite a bit of configuration.
> > >
> > > Finally, this fixes a recently introduced bug in unit testing and updates
> > > the algorithm to avoid running flat-tree tests which don't actually use
> > > the devicetree.
> > >
> > > Changes in v3:
> > > - Drop CONFIG_MISC and CONFIG_NVMEM
> > > - Update commit message
> > > - Separate out patch to restore test behaviour on failure
> > >
> >
> > series applied to u-boot-x86, thanks!
> 
> Could you please look at the CI failure?
> https://source.denx.de/u-boot/custodians/u-boot-x86/-/pipelines/16890/failures

I _think_ if you rebase on master this should be fixed with
https://patchwork.ozlabs.org/project/uboot/patch/20230712024632.2365887-1-sjg@chromium.org/
applied.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20230714/b30d3fb2/attachment.sig>