Openbmc u-boot trees (was Re: u-boot:rsa adds rsa3072 algorithm)

[Joel Stanley]

On Wed, 9 Feb 2022 at 02:29, ChiaWei Wang <chiawei_wang at aspeedtech.com> wrote:
> > I would like to see fewer trees.
> >
> > In the short term, one option is we put all of the openbmc patches in the SDK,
> > and continue using that for openbmc. Would this work for aspeed?
>
> Yes.
> Are we going to do this through PRs as usual?

Works for me. I've sent two PRs with the obvious changes:

 https://github.com/AspeedTech-BMC/u-boot/pull/9

 https://github.com/AspeedTech-BMC/u-boot/pull/8

We need to work out how to arrange the defconfigs. Would you like to
see openbmc using one of the defconfigs you maintain, or should we
keep a seperate one?

configs/evb-ast2600-cot_defconfig
configs/evb-ast2600_defconfig
configs/evb-ast2600-ecc_defconfig
configs/evb-ast2600-emmc_defconfig
configs/evb-ast2600-spl_defconfig
configs/evb-ast2600-spl-ecc_defconfig
configs/evb-ast2600-spl-ncsi_defconfig
configs/evb-ast2600-spl-tiny_defconfig

The openbmc ones are here:

configs/ast2600_openbmc_defconfig
configs/ast2600_openbmc_spl_defconfig
configs/ast2600_openbmc_spl_emmc_defconfig

The openbmc and openbmc_spl defconfigs are legacy and not tested by
myself. I actively maintain the openbmc_spl_emmc configuration as it
supports the rainier/everest

> > In the medium term, we should start using upstream releases. There may still
> > be some downstream code (as we have for Linux in our dev branches), but this
> > will go to zero over time.
>
> Agree.
> We are also working on upstreaming fundamental drivers to U-Boot mainline.
> Once it is sufficient for most frequently used booting paths, Aspeed will start using it.

Excellent. Thank you for your work in this area.

Cheers,

Joel