From mboxrd@z Thu Jan  1 00:00:00 1970
From: Philippe REYNES <philippe.reynes@softathome.com>
Date: Mon, 9 Sep 2019 18:41:02 +0200 (CEST)
Subject: [U-Boot] [RFC][PATCH] bootcount: add support to customize
 bootcount variable name
In-Reply-To: <20190909160627.7E86A24003E@gemini.denx.de>
References: <1568037413-28155-1-git-send-email-philippe.reynes@softathome.com>
 <20190909160627.7E86A24003E@gemini.denx.de>
Message-ID: <992029351.2212296.1568047262683.JavaMail.zimbra@softathome.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Wolfgang,

> Dear Philippe,
> 
> In message <1568037413-28155-1-git-send-email-philippe.reynes@softathome.com>
> you wrote:
>> This commit add an option to customize the bootcount variable
>> name in the u-boot environment. To stay compatible with old config,
>> the default name is bootcount.
> 
> Which exact problem are you trying to fix with this commit?

I have severals layers in my boot chain, and I want to use bootcount
in severals layers to manage boot issues. If severals layers use the
same variable name (bootcount) and a boot issue happen, I can't find
the layer that fails.

So I propose to "customize" the bootcount variable name.

> I mean, we have a ton of variable names with fixed meaning, which
> have been in use for nearly 2 decades - bootcmd, bootargs,
> bootcount, ...
> 
> What is wrong with the "boootcount" name?

As it is "unique", I can't chain severals bootcount.
That's why I propose an option to customize the bootcount name variable.

I know that it's a "corner case" and that you could prefer to avoid
adding another option, that's why I've proposed this option as a RFC.

> Best regards,
> 
> Wolfgang Denk

Best regards,
Philippe Reynes