Lines Matching refs:it

23 subject and I can't cover it all here!
29 things to have it work right depending on your hardware.  Most of
37 Kernel code (like the watchdog) can still use it.  If you need access
42 properly provides the SMBIOS info for IPMI, the driver will detect it
47 support this, but it is unknown if it will work on every board.  For
49 figuring to see if it will work on your system if the SMBIOS/APCI
67 watchdog timer start as soon as it initializes.  It also have a lot
69 Note that you can also have the watchdog continue to run if it is
70 closed (by default it is disabled on close).  Go into the 'Watchdog
91 only need to take the pieces you need and you can use it in many
92 different ways.  Because of that, it's broken into many chunks of
124 is no longer supported and has been removed because it was impossible
125 to do 32 bit emulation on 64-bit kernels with it.
180 than one channel, it corresponds to the channel as defined in the IPMI
201 the first item in "data", it is not stripped out because that is how
206 of data for "data", fill it, and set data_len to the length of the
231 	   the size or existence of this, since it may change. */
268 self-explanatory.  However, it takes a "msgid" parameter.  This is NOT
271 use it for anything you like.
289 queue.  If you want to get it and have it truncate the message, us
296 seconds, it will generate a response automatically saying the command
297 timed out.  If an unsolicited response comes in (if it was after 5
300 In kernelland, after you receive a message and are done with it, you
301 MUST call ipmi_free_recv_msg() on it, or you will leak messages.  Note
310 though, since it is tricky to manage your own buffers.
357 if it doesn't find any the driver will attempt to register one KCS
376 The si_type may be either "kcs", "smic", or "bt".  If you leave it blank, it
391 tries it, set this value to zero to turn this off.
409 data used by IPMI is 8-bits wide, but it may be inside a larger
418 usually 0x20 and the driver defaults to that, but in case it's not, it
425 want the CPU hit) can disable it.
427 If unload_when_empty is set to 1, the driver will be unloaded if it
457 force this thread on or off.  If you force it off and don't have
495 system.  By default, the driver will only register with something it
510 adapter_name=ThisisanI2cchip.  This is because it's hard to pass in
520 usually 0x20 and the driver defaults to that, but in case it's not, it
586 used to control it:
640 The watchdog will panic and start a 120 second reset timeout if it
642 start a 120 timer if it is running to make sure the reboot occurs.
646 comes from the IPMI controller, so it must assume that if it gets an
647 otherwise unhandled NMI, it must be from IPMI and it will panic
651 device to close it, or the timer will not stop.  This is a new semantic
652 for the driver, but makes it consistent with the rest of the watchdog
692 If it has an SEL, then they will be stored in the SEL of the local
706 it will send the proper IPMI commands to do this.  This is supported on
711 the system off, then power it on in a few seconds).  Setting
715 does not support power cycling, it will always do the power off.