OpenBMC Image Management

[Adriana Kobylak]

> On Jun 20, 2017, at 10:03 AM, Chris Austen <austenc at us.ibm.com> wrote:
> 
> "openbmc" <openbmc-bounces+austenc=us.ibm.com at lists.ozlabs.org <mailto:openbmc-bounces+austenc=us.ibm.com at lists.ozlabs.org>> wrote on 06/20/2017 09:38:40 AM:
> 
> 
> > 
> > For OpenBMC, we’re having the PNOR chip with a filesystem, so mboxd 
> > would read/write files instead of looking for the data at an offset 
> > in the chip. Nothing deficient with it, just a different 
> > implementation that needs to be handled.
> 
> 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?
> 
> 
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:

https://github.com/openbmc/openbmc/commit/dd05b963e1847a1f56b11825a7d39602b6151165 <https://github.com/openbmc/openbmc/commit/dd05b963e1847a1f56b11825a7d39602b6151165>

> > 
> > > 
> > > -- 
> > > Stewart Smith
> > > OPAL Architect, IBM.
> > 
> Chris Austen
> POWER Systems Enablement Manager 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170710/04f156e0/attachment.html>