IPMI driver version 18 release
Subsystems (2)
I found a few stupid bugs in the IPMI driver dealing with certain error cases, and this also contains the documentation updates that I have not sent to Linus enough times to be included yet :-).
The 2.5 version is attached. The 2.4 version is at:
http://sourceforge.net/projects/openipmi/
-Corey
Documentation/IPMI.txt +12 -0
@@ -5,6 +5,18 @@ <[email protected]> <[email protected]> +The Intelligent Platform Management Interface, or IPMI, is a +standard for controlling intelligent devices that monitor a system. +It provides for dynamic discovery of sensors in the system and the +ability to monitor the sensors and be informed when the sensor's +values change or go outside certain boundaries. It also has a +standardized database for field-replacable units (FRUs) and a watchdog +timer. + +To use this, you need an interface to an IPMI controller in your +system (called a Baseboard Management Controller, or BMC) and +management software that can use the IPMI system. + This document describes how to use the IPMI driver for Linux. If you are not familiar with IPMI itself, see the web site at http://www.intel.com/design/servers/ipmi/index.htm. IPMI is a big
drivers/char/ipmi/Kconfig +8 -2
@@ -7,8 +7,14 @@ tristate 'IPMI top-level message handler' help This enables the central IPMI message handler, required for IPMI - to work. Note that you must have this enabled to do any other IPMI - things. See IPMI.txt for more details. + to work. + + IPMI is a standard for managing sensors (temperature, + voltage, etc.) in a system. + + See Documentation/IPMI.txt for more details on the driver. + + If unsure, say N. config IPMI_PANIC_EVENT bool 'Generate a panic event to all BMCs on a panic'
drivers/char/ipmi/ipmi_msghandler.c +1 -3
@@ -345,7 +345,7 @@unsigned int i;for (i=intf->curr_seq; - i!=(intf->curr_seq-1 ); + (i+1 )%IPMI_IPMB_NUM_SEQ != intf->curr_seq; i=(i+1 )%IPMI_IPMB_NUM_SEQ ) {if (! intf->seq_table[i].inuse)
@@ -906,8 +906,6 @@probably, so abort. */ spin_unlock_irqrestore (&(intf->seq_lock), flags); -ipmi_free_recv_msg (recv_msg); -ipmi_free_smi_msg (smi_msg); goto out_err; }