<html><body><p><tt><font size="2">"openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org> wrote on 06/20/2017 09:38:40 AM:<br><br>> From: Adriana Kobylak <anoo@linux.vnet.ibm.com></font></tt><br><tt><font size="2">> To: Stewart Smith <stewart@linux.vnet.ibm.com></font></tt><br><tt><font size="2">> Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org></font></tt><br><tt><font size="2">> Date: 06/20/2017 09:38 AM</font></tt><br><tt><font size="2">> Subject: Re: OpenBMC Image Management</font></tt><br><tt><font size="2">> Sent by: "openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org></font></tt><br><tt><font size="2">> <br>> <br>> > On Jun 19, 2017, at 12:44 AM, Stewart Smith <br>> <stewart@linux.vnet.ibm.com> wrote:<br>> > <br>> > Adriana Kobylak <anoo@linux.vnet.ibm.com> writes:<br>> >>> Why is there mboxbridge separate from phosphor-mboxd?<br>> >> <br>> >> Because the mboxbridge is being used by other companies as a reference<br>> >> to be able to implement the mailbox daemon in their own BMC firmware<br>> >> stack for other openpower systems, we didn’t want to “pollute” the<br>> >> repository with openbmc-specific and c++ implementation that could<br>> >> confuse them.<br>> > <br>> > Why are there OpenBMC specific things in mboxd?<br>> > <br>> > Why can't the reference implementation be used? What's deficient in it?<br>> <br>> For OpenBMC, we’re having the PNOR chip with a filesystem, so mboxd <br>> would read/write files instead of looking for the data at an offset <br>> in the chip. Nothing deficient with it, just a different <br>> implementation that needs to be handled.<br></font></tt><br><tt><font size="2">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><br><tt><font size="2">> </font></tt><br><tt><font size="2">> > <br>> > -- <br>> > Stewart Smith<br>> > OPAL Architect, IBM.<br>> <br></font></tt><font size="2">Chris Austen<br>POWER Systems Enablement Manager </font><BR>
</body></html>