Jehudi Maes

After going through the documentation once more I think it is basically the same. IMO this should be the standard method as it allows removing the swap status from the...

@LoupVaillant, regarding the 50kB, this is a lot on devices that have only 256kB of flash. Probably a general `NO_UNROLLING` option should provide sufficient optimisation. Regarding the necessity for blake2s,...

> @Laczen, when a new entry is stored in settings, it is cached regardless of the hash collision (`settings_nvs_cache_add` always adds new entry). Until `cache_next` wraps around, provided that all...

@d3zd3z, it isn't immediately clear to me, but does this mean a rogue application could be "piggybacked" (added) on a valid application as a tlv ?

> @Laczen I haven't had time to review this patch yet, however, it seems very problematic to me at first glance; changing an obviously public API in such a way...

@d3zd3z, the change in PR #1692 is more than just a change in the parameters of `boot_save_shared_data()`. It also enables a config option that makes this routine unusable externally. When...

> > Wether this is an "internal" of an "external" api should be decided based upon the usage, the tf-m/bl2 bootloader is using this api. > > It's great you...

> > @nordicjm any comments on Laczen's proposal on how to solve the issue that you have? > > There is no merit in his proposal I am feeling really...

@kasjer , i think this is by design to allow a newer build hut with the same version to overwrite the older. This also means that the same image will...

@kasjer, imho it is never a good idea to have a difference between a production build bootloader and a development bootloader. This will create an opportunity to miss an error...