summaryrefslogtreecommitdiff
path: root/meta-openembedded/meta-python/recipes-devtools/python/python-javaobj-py3.inc
diff options
context:
space:
mode:
authorMichael Tritz <mtritz@us.ibm.com>2017-12-16 00:35:14 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-01-16 23:22:38 +0300
commitcadef15028c480151a0997b604655bce29673c05 (patch)
tree41bf47ce92a2fe16bc8ab3e182c4901abb1171d1 /meta-openembedded/meta-python/recipes-devtools/python/python-javaobj-py3.inc
parente0a76388f8a4127cbb1008941ad5a314021587de (diff)
downloadopenbmc-cadef15028c480151a0997b604655bce29673c05.tar.xz
obmc-flash-bmc: write variables twice to ensure both banks are correct
The U-Boot environment maintains two banks of environment variables. The banks need to be consistent with each other to ensure that these variables can be reliably read from file, as they would be in the context of a C++ program. In order to guarantee that the two banks are both correct, we need to run fw_setenv twice when writing environment variables. This change accompanies a change to phosphor-bmc-code-mgmt for openbmc/openbmc#2666. Change-Id: I72d7fd79faf271d017703464fd9ad0cd20f4e2a0 Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python-javaobj-py3.inc')
0 files changed, 0 insertions, 0 deletions