Lines Matching refs:you

16 To use this, you need an interface to an IPMI controller in your
20 This document describes how to use the IPMI driver for Linux.  If you
28 The Linux IPMI driver is modular, which means you have to pick several
33 No matter what, you must pick 'IPMI top-level message handler' to use
34 IPMI.  What you do beyond that depends on your needs and hardware.
37 Kernel code (like the watchdog) can still use it.  If you need access
38 from userland, you need to select 'Device interface for IPMI' if you
43 and just work.  If you have a board with a standard interface (These
56 If you have a standard interface and the board manufacturer has done
60 standard defaults, but they may not work.  If you fall into this
61 situation, you need to read the section below named 'The SI Driver' or
65 'IPMI Watchdog Timer' config option.  If you compile the driver into
66 the kernel, then via a kernel command-line option you can have the
69 Note that you can also have the watchdog continue to run if it is
81 If you want the driver to put an event into the event log on a panic,
83 you want the whole panic string put into the event log using OEM
90 The Linux IPMI driver is designed to be very modular and flexible, you
91 only need to take the pieces you need and you can use it in many
107 SMIC, and BT interfaces.  Unless you have an SMBus interface or your
108 own custom interface, you probably need to use this.
143 The IPMI addressing works much like IP addresses, you have an overlay
205 When using the IOCTL interface from userland, you must provide a block
250 To user the message handler, you must first create a user using
251 ipmi_create_user.  The interface number specifies which SMI you want
252 to connect to, and you must supply callback functions to be called
254 so be careful using the callbacks.  This also allows to you pass in a
255 piece of data, the handler_data, that will be passed back to you on
258 Once you are done, call ipmi_destroy_user() to get rid of the user.
271 use it for anything you like.
274 field of the "handler" that you passed in to ipmi_create_user().
278 From userland, you fill out an ipmi_req_t structure and use the
279 IPMICTL_SEND_COMMAND ioctl.  For incoming stuff, you can use select()
280 or poll() to wait for messages to come in.  However, you cannot use
281 read() to get them, you must call the IPMICTL_RECEIVE_MSG with the
282 ipmi_recv_t structure to actually get the message.  Remember that you
284 you must fill in the msg.data_len field with the size of the data.
287 If the message cannot fit into the data you provide, you will get an
289 queue.  If you want to get it and have it truncate the message, us
292 When you send a command (which is defined by the lowest-order bit of
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
302 that you should NEVER mess with the "done" field of a message, that is
306 that lets you supply the smi and receive message.  This is useful for
317 commands that other things on the IPMB bus have sent you).  To receive
318 these, you must register for them, they will not automatically be sent
319 to you.
321 To receive events, you must call ipmi_set_gets_events() and set the
327 For receiving commands, you have to individually register commands you
329 and command name for each command you want to receive.  You also
330 specify a bitmask of the channels you want to receive the command from
331 (or use IPMI_CHAN_ALL for all channels if you don't care).  Only one
376 The si_type may be either "kcs", "smic", or "bt".  If you leave it blank, it
379 If you specify addrs as non-zero for an interface, the driver will
383 If you specify ports as non-zero for an interface, the driver will
386 If you specify irqs as non-zero for an interface, the driver will
449 0xca2.  If you want to turn this off, set the "trydefaults" option to
457 force this thread on or off.  If you force it off and don't have
485 and these have the same meanings as discussed above.  Note that you
509 spaces, so if the name is "This is an I2C chip" you can say
528 the smb_addr parameter unless you have DMI or ACPI data to tell the
560 come or go, and to grab the information, you can use the function
577 assuming ipmi_smi_get_info returns success, you must call put_device
615 because you can't do data operations from an NMI.
644 Note that if you use the NMI preaction for the watchdog, you MUST NOT
650 Once you open the watchdog timer, you must write a 'V' character to the
660 events in the system event log if a panic occurs.  if you enable the
661 'Generate a panic event to all BMCs on a panic' option, you will get
662 one event on a panic in a standard IPMI event format.  If you enable
663 the 'Generate OEM events containing the panic string' option, you will
689 Because you cannot send OEM events using the standard interface, this
721 Note that if you have ACPI enabled, the system will prefer using ACPI to