[PATCH 0/2] Remove "saveenv" functionality from am57xx evms

Kumar, Udit u-kumar1 at ti.com
Mon Feb 10 05:25:22 CET 2025


Hi Tom

On 2/9/2025 10:50 PM, Tom Rini wrote:
> On Sat, Feb 08, 2025 at 10:09:36AM +0530, Anurag Dutta wrote:
>
>> Previously saved environment introduce discrepancies and may lead to
>> incompatibilities without default settings. This series removes the saved
>> environment functionality on am57xx evms so that the default configuration
>> is always loaded
>>
>> Test result: https://gist.github.com/anuragdutta731/b253ddb0a5538ab6588a3535d7bbecf7
>>
>> Anurag Dutta (2):
>>    configs: am57xx_hs: Remove saved environments
>>    configs: am57xx: Remove saved environments
>>
>>   configs/am57xx_evm_defconfig    | 4 +---
>>   configs/am57xx_hs_evm_defconfig | 4 +---
>>   2 files changed, 2 insertions(+), 6 deletions(-)
> I'm not sure what this is intended to solve. A persistent environment
> can be reset to the defaults with "env default -f -a" and telling users
> to do this when needed when upgrading is a long standing practice.

There are few inconsistencies in development flow with saved env.

There we revert already for k3 platforms.  Please see

https://github.com/u-boot/u-boot/commit/a5e8678e0a32f85ad012aea7641e9534ada5c0fe 




More information about the U-Boot mailing list