OpenBMC Image Management

Adriana Kobylak anoo at
Wed Jun 21 00:38:40 AEST 2017

> On Jun 19, 2017, at 12:44 AM, Stewart Smith <stewart at> wrote:
> Adriana Kobylak <anoo at> writes:
>>> 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.
> Why are there OpenBMC specific things in mboxd?
> Why can't the reference implementation be used? What's deficient in it?

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.

> -- 
> Stewart Smith
> OPAL Architect, IBM.

More information about the openbmc mailing list