Corey,
Okay. I will go with OEM event.
We received notification this week that Pigeon Point has implemented "hpm.1"
(?) firmware upgrade method in their code.
They indicated that this is a true IPMI standard that others will be using
as well. I haven't found anything on this yet. Is it truly a standard?
Will code for it reside in user space or will kernel drivers need to be
modified to use it?
Thanks
David
On 4/20/07, Corey Minyard <[EMAIL PROTECTED]> wrote:
I've been waffling a little, too, but I still think it should be an
event, and an OEM event at that. I have two basic reasons for this:
* Events are meant for asynchronous notification, and this is
asynchronous.
* Though the IPMC may ignore this now, I'd like to not send anything
that might perturb the IPMC after a firmware upgrade or some new
version.
* It's possible to pick up an event that has occurred in the past,
if you are interested.
So I really think an event is the right way to go. Make sure to follow
the proper event format for an OEM event.
Thanks,
-corey
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
