Dear Philippe, In message <992029351.2212296.1568047262683.javamail.zim...@softathome.com> you wrote: > > 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.
I can't understand your problem description, sorry. > So I propose to "customize" the bootcount variable name. This makes no sense to me. > As it is "unique", I can't chain severals bootcount. > That's why I propose an option to customize the bootcount name variable. But that's the actual situation: there is only one boot count. Please keep in mind that this variable holds the number of boot attepmts since the last power-on that failed to successfully reach a specific "confirmation point" in your application (that, which is considered a complete, successfull boot of the whole system). For this single task there can be only a single counter, or? > 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. I do not see any practical use yet... Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de READ THIS BEFORE OPENING PACKAGE: According to Certain Suggested Ver- sions of the Grand Unified Theory, the Primary Particles Constituting this Product May Decay to Nothingness Within the Next Four Hundred Million Years. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
