Super Short OEM IPMI Proposal

Vernon Mauery vernon.mauery at
Thu Jul 18 06:37:22 AEST 2019

On 17-Jul-2019 01:10 PM, Patrick Venture wrote:
>Hi all;
>Undoubtedly you've been using IPMI out of necessity and ran into some
>limitations.  You've then worked to map out the commands you want, and
>dropped them into the OEM space.
>I was looking at how Intel handled one of their OEM commands and
>effectively want that command -- not all their commands, but just that
>one.  And I was curious if there was any value in OpenBMC as a
>community working to define some shared OEM commands.
>Is there value in this or will it just become a cumbersome camel?

  (__/ \  _  _
     \  \/ \/ \
     (         )\
      \_______/  \
       [[] [[]
       [[] [[]

As much as I don't want to tell someone to cut and paste code, I can't 
really think of a good way to share something like an OEM command that 
doesn't really have a shared spec. I guess it depends on the command 
that you are interested in. We have overridden a couple of standard 
commands to have behavior that is slightly different than the default 
and we have two whole netfns of OEM commands that we have carried along 
for generations of BMC implementations. Either way, the commands are 
subject to change over time that may or may not diverge from what anyone 
else might want, which is where the shared bit can become awkward. But 
copied code won't necessarily get any updates or bug fixes, so that is 
not great either.


More information about the openbmc mailing list