[IPMBD] ipmbSend handling

KFTING at nuvoton.com KFTING at nuvoton.com
Tue Aug 28 12:14:48 AEST 2018


Hi Ed:

> Not true in either the spec or the implementation.

Thank you for your description of the ipmbbridge design.

Now I get a better picture of it.

> It would help a lot if you could add your comments to the code in the gerrit review.  It might help track down where you think the issues are.

Sure, I'll do that.

Regards,
Tyrone
-----Original Message-----
From: Tanous, Ed [mailto:ed.tanous at intel.com]
Sent: Saturday, August 25, 2018 12:08 AM
To: CS00 KFTing; openbmc at lists.ozlabs.org
Subject: RE: [IPMBD] ipmbSend handling

>
> The direction is always from the master device to the slave device.
>
Not true in either the spec or the implementation.  The IPMB bridge was designed to operate two ways.  First, requests could be made from external entities, like an IPMB header on the board, or the Management Engine (On x86 platforms).  These requests first require the BMC to be a slave for the request, and a master for the response.  Second, the BMC could initiate a request (Probably to the management engine).  In that case, it would be an master for the request, then a slave for the response.  In theory, both scenarios are supported by the daemon, but only the first case might be enabled at this point.

>
> It seems to me that ipmbSend behavior doesn't get aligned with the description of request/response protocol in IPMB spec.
>

What do you refer to as ipmbSend here?

It would help a lot if you could add your comments to the code in the gerrit review.  It might help track down where you think the issues are.

-Ed


===========================================================================================
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.


More information about the openbmc mailing list