summaryrefslogtreecommitdiff
path: root/meta-phosphor/conf/machine/include/obmc-bsp-common.inc
diff options
context:
space:
mode:
authorMilton D. Miller II <miltonm@us.ibm.com>2016-01-28 05:18:16 +0300
committerMilton D. Miller II <miltonm@us.ibm.com>2016-01-29 00:46:41 +0300
commit8084d744423576c7466ed773f5d73cb4a7b0d841 (patch)
treecba4f8f829bb04ba87cdd5dbcff0589025050a8c /meta-phosphor/conf/machine/include/obmc-bsp-common.inc
parent6964081624ad44c462a94f20a19c57c93cb583e8 (diff)
downloadopenbmc-8084d744423576c7466ed773f5d73cb4a7b0d841.tar.xz
Hack to make fw_setenv work
The fw_setenv is not working with the kernel mtd driver. It works on a plain flat file, and flashcp which is used in /update works. Find the u-boot-env mtd, link it in run and copy the contents to a plain file in /run during init. In shutdown, check for the link, the file having data, no current image update for the u-boot-env, and that the content differs from the mtd via the link. If all are true create a symlink to the file and trigger the update. Along wtih changing the fw_env.config this causes the fw_setenv and fw_printenv utilities to set and update this cached file which will be synced during a normal bmc reboot. This will allow us to set the ethaddr variable which already requires a reboot to activate. Note: the links are directly in /run because the fw_{set,print}env utilities limit the env file name to 16 characters. Signed-off-by: Milton Miller <miltonmm@us.ibm.com>
Diffstat (limited to 'meta-phosphor/conf/machine/include/obmc-bsp-common.inc')
0 files changed, 0 insertions, 0 deletions