cr50: move major version number component to 1
It is beneficial to have the 'major' version number component advanced
with every major Cr50 code release: this will allow to use the 'minor'
version number component when it is necessary to release a bug fix or
a small addition to the current release.
BRANCH=cr50
BUG=none
TEST=verified proper version number reported by 'version' command
Change-Id: Ie87a2b676b59b46be243fa6367571a1d0877f13d
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/820270
Reviewed-by: Mary Ruthven <mruthven@chromium.org>
(cherry picked from commit 1b53782145
)
Reviewed-on: https://chromium-review.googlesource.com/820565
This commit is contained in:
parent
9c8c0497f9
commit
ad5518329b
|
@ -39,8 +39,8 @@
|
|||
|
||||
"timestamp": 0,
|
||||
"epoch": 0, // FWR diversification contributor, 32 bits.
|
||||
"major": 0, // FW2_HIK_CHAIN counter.
|
||||
"minor": 26, // Mostly harmless version field.
|
||||
"major": 1, // FW2_HIK_CHAIN counter.
|
||||
"minor": 0, // Mostly harmless version field.
|
||||
"applysec": -1, // Mask to and with fuse BROM_APPLYSEC.
|
||||
"config1": 13, // Which BROM_CONFIG1 actions to take before launching.
|
||||
"err_response": 0, // Mask to or with fuse BROM_ERR_RESPONSE.
|
||||
|
|
|
@ -43,8 +43,8 @@
|
|||
// epoch/major/minor would be preferred
|
||||
"timestamp": 1,
|
||||
"epoch": 0, // FWR diversification contributor, 32 bits.
|
||||
"major": 0, // FW2_HIK_CHAIN counter.
|
||||
"minor": 26, // Mostly harmless version field.
|
||||
"major": 1, // FW2_HIK_CHAIN counter.
|
||||
"minor": 0, // Mostly harmless version field.
|
||||
"applysec": -1, // Mask to and with fuse BROM_APPLYSEC.
|
||||
"config1": 13, // Which BROM_CONFIG1 actions to take before launching.
|
||||
"err_response": 0, // Mask to or with fuse BROM_ERR_RESPONSE.
|
||||
|
|
Loading…
Reference in New Issue