[PATCH v3 00/31] Initial implementation of standard boot

[Simon Glass]

Hi Michael,

On Sun, 6 Mar 2022 at 04:03, Michael Walle <michael at walle.cc> wrote:
>
> Hi Simon,
>
> Am 2022-03-06 04:08, schrieb Simon Glass:
> > On Thu, 20 Jan 2022 at 11:16, Simon Glass <sjg at chromium.org> wrote:
> >> On Thu, 20 Jan 2022 at 01:38, Michael Walle <michael at walle.cc> wrote:
> >> > Am 2022-01-19 15:56, schrieb Simon Glass:
> >> > > On Wed, 19 Jan 2022 at 01:09, Michael Walle <michael at walle.cc> wrote:
> >> > >>
> >> > >>
> >> > >> > 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.
> >> > >
> >> > > Yes that's not working yet. Can you try an mmc device for testing?
> >> >
> >> > Ok thanks for confirming. Yes I can test with a sd card,
> >> > but I'll probably do it when there is support for loading
> >> > a device tree by the fdtfile.
> >>
> >> Yes I need to look at that one.
> >
> > Can you please point me to the OS image you are using.
>
> I'm not testing this on a raspberry pi, if that's what you had
> in mind.
>
> but for what it's worth, the image i'm building is for a kontron
> sl28 board and it is based on vanilla buildroot. the config
> and be found at the vanilla buildroot repo:
>   configs/kontron_smarc_sal28_defconfig

OK, thanks. I'll spin up buildroot at some point.

For now I am just going to send the base series. The conversion needs
to be done case by case with manual testing on specific distros and
boards, so I'll worry about that we have something in there.

Regards,
Simon