public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: IPMI
Date: Tue, 14 Jan 2003 08:35:17 -0600	[thread overview]
Message-ID: <3E242025.1030408@mvista.com> (raw)
In-Reply-To: <15907.55035.787654.77224@argo.ozlabs.ibm.com>

I added the following to the top of the document.  Do you have any
other comments on the document or this text?

The Intelligent Peripheral 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.

-Corey

Paul Mackerras wrote:

>Rusty Russell writes:
>
>  
>
>>Telling me what IPMI is, and why I might need it, would be a good
>>thing...  Please, Corey, I'm feeling generation-gapped by the
>>acronyms...
>>    
>>
>
>There is a Documentation/IPMI.txt, which would serve as an excellent
>example of how _not_ to write a documentation file, should you ever
>decide to write a "Rusty's Unreliable Guide to Writing Kernel
>Documentation" and need an example to pillory.  I quote:
>
>
>  
>
>>			    The Linux IPMI Driver
>>			    ---------------------
>>				Corey Minyard
>>			    <minyard@mvista.com>
>>			      <minyard@acm.org>
>>
>>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
>>subject and I can't cover it all here!
>>    
>>
>
>Maybe it can't all be covered here, but some basic explanation of what
>IPMI is and does is essential, even if just so that people who don't
>need IPMI can work that out.
>
>Paul.
>
>
>  
>



  parent reply	other threads:[~2003-01-14 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  8:29 IPMI Rusty Russell
2003-01-14  9:23 ` IPMI Paul Mackerras
2003-01-14 11:55   ` IPMI Bruce Harada
2003-01-14 12:36     ` IPMI Arjan van de Ven
2003-01-14 13:07       ` IPMI Bruce Harada
2003-01-14 14:35   ` Corey Minyard [this message]
2003-01-15  3:36     ` IPMI Paul Mackerras
2003-01-15  3:55       ` IPMI Corey Minyard
2003-01-14 14:29 ` IPMI Corey Minyard
2003-01-14 14:46   ` IPMI Adrian Bunk
2003-01-14 14:59   ` IPMI Wichert Akkerman
2003-01-15  3:49   ` IPMI Rusty Russell
2003-01-15 20:46     ` IPMI Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15  5:08 IPMI Perez-Gonzalez, Inaky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E242025.1030408@mvista.com \
    --to=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox