1 <h2>device_reply_server
</h2>
4 <strong>Function
</strong> - Handle incoming data from kernel device driver.
7 <strong>boolean_t device_reply_server
</strong>
8 <strong>(mach_msg_header_t
</strong> <var>request_msg
</var>,
9 <strong>mach_msg_header_t
</strong> <var>reply_msg
</var><strong>);
</strong>
14 <dt> <var>request_msg
</var>
16 [pointer to in structure]
17 The device driver message received from the
20 <dt> <var>reply_msg
</var>
23 A reply message. No messages from a device driver
24 expect a direct reply, so this field is not used.
28 The
<strong>device_reply_server
</strong> function is the MIG generated server handling
29 function to handle messages from kernel device drivers. Such
30 messages were sent in response to the various
31 <strong>device_
</strong>...
<strong>_request
</strong>...
32 calls. It is assumed when using
33 those calls that some task is listening for reply messages on the port named as a
34 reply port to those calls. The
<strong>device_reply_server
</strong>
36 necessary argument handling for a kernel message and calls one
37 of the device server functions to interpret the message.
38 <h3>RETURN VALUES
</h3>
41 <dt> <strong>TRUE
</strong>
43 The message was handled and the appropriate function was called.
45 <dt> <strong>FALSE
</strong>
47 The message did not apply to this device handler interface and no other
50 <h3>RELATED INFORMATION
</h3>
53 <a href=
"device_open.html"><strong>ds_device_open_reply
<strong></a>,
54 <a href=
"device_write.html"><strong>ds_device_write_reply
<strong></a>,
55 <a href=
"device_write_inband.html"><strong>ds_device_write_reply_inband
<strong></a>,
56 <a href=
"device_read.html"><strong>ds_device_read_reply
<strong></a>,
57 <a href=
"device_read_inband.html"><strong>ds_device_read_reply_inband
<strong></a>,
58 <a href=
"device_read_overwrite.html"><strong>ds_device_read_reply_overwrite
<strong></a>.