The application would be responsible for issuing the GET MESSAGE FLAGS command and handling the response. One downside of this approach is that it prevents you
from ever making ipmi_kcs_cmd_api_ipmb event-driven. What do you two think?
From: Al Chu <address@hidden>
To: Matt Jerdonek <address@hidden>
Sent: Thu, February 18, 2010 10:58:06 AM
Subject: Re: [Freeipmi-devel] KCS Driver & SMS_ATN Register
Definitely open to patches. Looking over the IPMI spec, I agree w/
A.B., it seems to be more useful for a higher level monitoring, w/ the
Get Message Flags and similar commands. I can think of several patch
1) add a KCS driver flag for checking for SMS_ATN in addition to OBF (or
instead of??). Flags may be propogated up into higher level APIs too.
2) an additional function that checks for SMS_ATN in addition/or instead
of OBF that users can call instead.
It would be useful to understand your use case too. Are you using the
KCS driver and IPMI bridging commands to bridge from one BMC to another
On Wed, 2010-02-17 at 18:51 -0800, Matt Jerdonek wrote:
> The KCS driver appears to not use the SMS_ATN register. This register
> is useful for BMC-to-BMC communication to know when the remote BMC
> responded. Are there any plans to monitor this register in future
> releases? If not, are the maintainers open to including a patch?
> Freeipmi-devel mailing list
> address@hidden> http://*lists.gnu.org/mailman/listinfo/freeipmi-devel
High Performance Systems Division
Lawrence Livermore National Laboratory