OpenBMC Image Management
anoo at linux.vnet.ibm.com
Mon Jun 19 05:48:28 AEST 2017
> On Jun 13, 2017, at 4:45 PM, Stewart Smith <stewart at linux.vnet.ibm.com> wrote:
> Adriana Kobylak <anoo at linux.vnet.ibm.com> writes:
>> Regarding the mailbox daemon, the mboxbridge repository is staying as a reference
>> implementation and has been cloned into phosphor-mboxd. Any system using mailbox and
>> running with a flashed ffs pnor image (instead of updating to the ubi layout) would still need
>> the reference mboxbridge implementation. The openbmc build is being updated to build
>> phosphor-mboxd as the default.
> Why is there mboxbridge separate from phosphor-mboxd?
Because the mboxbridge is being used by other companies as a reference to be able to implement the mailbox daemon in their own BMC firmware stack for other openpower systems, we didn’t want to “pollute” the repository with openbmc-specific and c++ implementation that could confuse them.
> Stewart Smith
> OPAL Architect, IBM.
More information about the openbmc