Hi Tom, On Fri, 9 Oct 2026 at 16:33, Tom Rini <[email protected]> wrote: > > On Fri, Oct 09, 2026 at 07:43:15AM +0100, Simon Glass wrote: > > Hi Ilias, > > > > On Thu, 8 Oct 2026 at 11:14, Ilias Apalodimas > > <[email protected]> wrote: > > > > > > On Tue, 6 Oct 2026 at 18:52, Michael Haener <[email protected]> > > > wrote: > > > > > > > > The Kria boards start the TPM with a 'tpm autostart' call in the board > > > > environment. Enable CONFIG_TPM_AUTOSTART instead and drop tpm_setup from > > > > the environment, so the TPM is started even when the preboot script is > > > > changed or skipped. > > > > > > > > The TPM is now started before preboot, so the TPM reset hints for some > > > > carrier card revisions are printed after the startup. Boards which still > > > > have the old environment saved run 'tpm autostart' a second time, which > > > > is harmless. > > > > > > > > Signed-off-by: Michael Haener <[email protected]> > > > > --- > > > Simon there's also configs/chromebook_coral_defconfig that call the > > > startup. Do we need to change that as well? > > > > Tom isn't running the tests on my lab, as I understand it, so I don't > > think it matters. > > Setting aside that none of your hardware is part of the project > currently, we don't intentionally break platforms, so I believe the > question is if the option needs to be enabled or not, for general > functionality.
How do you mean, 'none of your hardware is part of the project'? Do you just mean that you don't run the tests on my lab? Anyway, we can tidy this up later if / when it causes a problem. Regards, Simon
