Lines Matching refs:message

33 No matter what, you must pick 'IPMI top-level message handler' to use
36 The message handler does not provide any user-level interfaces.
96 system.  It handles all messages, message timing, and responses.  The
103 driver, each open file for this device ties in to the message handler
116 interface on top of the IPMI message handler.
208 will have no place to put the message.
210 Messages coming up from the message handler in kernelland will come in
217 	/* The type of message as defined in the "Receive Types"
226 	/* Call this when done with the message.  It will presumably free
227 	   the message and do any other necessary cleanup. */
235 You should look at the receive type and handle the message
250 To user the message handler, you must first create a user using
266 To send a message from kernel-land, the ipmi_request() call does
267 pretty much all message handling.  Most of the parameter are
270 passed back when the response for the message is returned.  You may
282 ipmi_recv_t structure to actually get the message.  Remember that you
285 This gives the receiver a place to actually put the message.
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
300 In kernelland, after you receive a message and are done with it, you
302 that you should NEVER mess with the "done" field of a message, that is
303 required to properly clean up the message.
306 that lets you supply the smi and receive message.  This is useful for
343 message handler, each of these is assigned an interface number when
344 they register with the message handler.  They are generally assigned
525 message as a block write to the I2C bus and waits for a response.
681 the message to the right place