OpenBMC Image Management

[Stewart Smith]

Adriana Kobylak <anoo at linux.vnet.ibm.com> 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?

-- 
Stewart Smith
OPAL Architect, IBM.