<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 20, 2017, at 10:03 AM, Chris Austen <<a href="mailto:austenc@us.ibm.com" class="">austenc@us.ibm.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p style="font-family: ArialUnicodeMS; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><tt class=""><font size="2" class="">"openbmc" <<a href="mailto:openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org" class="">openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org</a>> wrote on 06/20/2017 09:38:40 AM:<br class=""><br class=""></font></tt><tt class=""><font size="2" class=""><br class="">><span class="Apple-converted-space"> </span><br class="">> For OpenBMC, we’re having the PNOR chip with a filesystem, so mboxd<span class="Apple-converted-space"> </span><br class="">> would read/write files instead of looking for the data at an offset<span class="Apple-converted-space"> </span><br class="">> in the chip. Nothing deficient with it, just a different<span class="Apple-converted-space"> </span><br class="">> implementation that needs to be handled.<br class=""></font></tt><br class=""><tt class=""><font size="2" class="">I have been recommending that if you want to try OpenBMC on your system (that is not running OpenBMC now) that the BMC chip be swapped. Does the offset vs filesystem change force the PNOR flash image to be forever changed too?</font></tt><br class=""><br class=""></p></div></blockquote>Not forever, it can be reflashed back to ffs using pflash. If the virtual pnor is not desired to be used on that system (since in this example the user just wants to try out openbmc) it can be disabled via a config flag when building the bmc image. Ex:</div><div><br class=""></div><div><a href="https://github.com/openbmc/openbmc/commit/dd05b963e1847a1f56b11825a7d39602b6151165" class="">https://github.com/openbmc/openbmc/commit/dd05b963e1847a1f56b11825a7d39602b6151165</a></div><div><br class=""><blockquote type="cite" class=""><div class=""><p style="font-family: ArialUnicodeMS; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><tt class=""><font size="2" class="">><span class="Apple-converted-space"> </span></font></tt><br class=""><tt class=""><font size="2" class="">> ><span class="Apple-converted-space"> </span><br class="">> > --<span class="Apple-converted-space"> </span><br class="">> > Stewart Smith<br class="">> > OPAL Architect, IBM.<br class="">><span class="Apple-converted-space"> </span><br class=""></font></tt><font size="2" class="">Chris Austen<br class="">POWER Systems Enablement Manager<span class="Apple-converted-space"> </span></font></p></div></blockquote></div><br class=""></body></html>