[PATCH v4 0/5] rpi: Tidy up booting

[Peter Robinson]

On Thu, 30 Jan 2025 at 19:55, Simon Glass <sjg at chromium.org> wrote:

> Hi,
>
> On Thu, 19 Dec 2024 at 17:34, Simon Glass <sjg at chromium.org> wrote:
> >
> > This series allows rpi to boot a compressed Ubuntu kernel with ~100MB
> > ramdisk, by expanding the available space.
> >
> > It also tidies up some strange behaviour with the provided FDT, where a
> > separate pointer is maintained to it, even though U-Boot has copied it
> > and placed it in its own space. This avoids strange bugs where it
> > accidentally gets overwritten when loading a file into memory.
> >
> > The patch to expand the devicetree was dropped, meaning that people
> > should be careful to unset fdt_addr in the environment.
> >
> > In version 2, it incorporates some changes to fdt_addr, etc. suggested
> > by Tom, as well as adding myself as a maintainer.
> >
> > Changes in v4:
> > - Expand the comment on set_fdt_addr()
> > - Update the commit message to talk in terms of my testing
> >
> > Changes in v3:
> > - Add to the existing comment block
> > - Update the comment block with the new values, including compression
> >
> > Changes in v2:
> > - Add new patch to make myself an rpi maintainer
> > - Add new patch to set bootm_size
> > - Add new patch to drop fdt_high and initrd_high
> > - Drop patch to allow expanding the devicetree during relocation
> >
> > Simon Glass (5):
> >   rpi: Add myself to the list of maintainers
> >   rpi: Set bootm_size to 512MB
> >   rpi: Drop fdt_high and initrd_high
> >   rpi: Update environment to support booti and large initrd
> >   rpi: Use the U-Boot control FDT for fdt_addr
> >
> >  MAINTAINERS                   |  1 +
> >  board/raspberrypi/rpi/rpi.c   | 20 +++++++++----------
> >  board/raspberrypi/rpi/rpi.env | 37 +++++++++++++++++++----------------
> >  3 files changed, 31 insertions(+), 27 deletions(-)
> >
> > --
> > 2.34.1
> >
>
> We have hit rc1 now. Is there any interest in applying this series?
>

I have started testing it but I am traveling so have limited devices (and
time) to test and I want to do more thorough testing on my return later in
the week.