1*5e3eaea3SApple OSS Distributions<h2>device_reply_server</h2> 2*5e3eaea3SApple OSS Distributions<hr> 3*5e3eaea3SApple OSS Distributions<p> 4*5e3eaea3SApple OSS Distributions<strong>Function</strong> - Handle incoming data from kernel device driver. 5*5e3eaea3SApple OSS Distributions<h3>SYNOPSIS</h3> 6*5e3eaea3SApple OSS Distributions<pre> 7*5e3eaea3SApple OSS Distributions<strong>boolean_t device_reply_server</strong> 8*5e3eaea3SApple OSS Distributions <strong>(mach_msg_header_t</strong> <var>request_msg</var>, 9*5e3eaea3SApple OSS Distributions <strong>mach_msg_header_t</strong> <var>reply_msg</var><strong>);</strong> 10*5e3eaea3SApple OSS Distributions</pre> 11*5e3eaea3SApple OSS Distributions<h3>PARAMETERS</h3> 12*5e3eaea3SApple OSS Distributions<dl> 13*5e3eaea3SApple OSS Distributions<p> 14*5e3eaea3SApple OSS Distributions<dt> <var>request_msg</var> 15*5e3eaea3SApple OSS Distributions<dd> 16*5e3eaea3SApple OSS Distributions[pointer to in structure] 17*5e3eaea3SApple OSS DistributionsThe device driver message received from the 18*5e3eaea3SApple OSS Distributionskernel. 19*5e3eaea3SApple OSS Distributions<p> 20*5e3eaea3SApple OSS Distributions<dt> <var>reply_msg</var> 21*5e3eaea3SApple OSS Distributions<dd> 22*5e3eaea3SApple OSS Distributions[out structure] 23*5e3eaea3SApple OSS DistributionsA reply message. No messages from a device driver 24*5e3eaea3SApple OSS Distributionsexpect a direct reply, so this field is not used. 25*5e3eaea3SApple OSS Distributions</dl> 26*5e3eaea3SApple OSS Distributions<h3>DESCRIPTION</h3> 27*5e3eaea3SApple OSS Distributions<p> 28*5e3eaea3SApple OSS DistributionsThe <strong>device_reply_server</strong> function is the MIG generated server handling 29*5e3eaea3SApple OSS Distributionsfunction to handle messages from kernel device drivers. Such 30*5e3eaea3SApple OSS Distributionsmessages were sent in response to the various 31*5e3eaea3SApple OSS Distributions<strong>device_</strong>...<strong>_request</strong>... 32*5e3eaea3SApple OSS Distributionscalls. It is assumed when using 33*5e3eaea3SApple OSS Distributionsthose calls that some task is listening for reply messages on the port named as a 34*5e3eaea3SApple OSS Distributionsreply port to those calls. The <strong>device_reply_server</strong> 35*5e3eaea3SApple OSS Distributionsfunction performs all 36*5e3eaea3SApple OSS Distributionsnecessary argument handling for a kernel message and calls one 37*5e3eaea3SApple OSS Distributionsof the device server functions to interpret the message. 38*5e3eaea3SApple OSS Distributions<h3>RETURN VALUES</h3> 39*5e3eaea3SApple OSS Distributions<dl> 40*5e3eaea3SApple OSS Distributions<p> 41*5e3eaea3SApple OSS Distributions<dt> <strong>TRUE</strong> 42*5e3eaea3SApple OSS Distributions<dd> 43*5e3eaea3SApple OSS DistributionsThe message was handled and the appropriate function was called. 44*5e3eaea3SApple OSS Distributions<p> 45*5e3eaea3SApple OSS Distributions<dt> <strong>FALSE</strong> 46*5e3eaea3SApple OSS Distributions<dd> 47*5e3eaea3SApple OSS DistributionsThe message did not apply to this device handler interface and no other 48*5e3eaea3SApple OSS Distributionsaction was taken. 49*5e3eaea3SApple OSS Distributions</dl> 50*5e3eaea3SApple OSS Distributions<h3>RELATED INFORMATION</h3> 51*5e3eaea3SApple OSS Distributions<p> 52*5e3eaea3SApple OSS DistributionsFunctions: 53*5e3eaea3SApple OSS Distributions<a href="device_open.html"><strong>ds_device_open_reply<strong></a>, 54*5e3eaea3SApple OSS Distributions<a href="device_write.html"><strong>ds_device_write_reply<strong></a>, 55*5e3eaea3SApple OSS Distributions<a href="device_write_inband.html"><strong>ds_device_write_reply_inband<strong></a>, 56*5e3eaea3SApple OSS Distributions<a href="device_read.html"><strong>ds_device_read_reply<strong></a>, 57*5e3eaea3SApple OSS Distributions<a href="device_read_inband.html"><strong>ds_device_read_reply_inband<strong></a>, 58*5e3eaea3SApple OSS Distributions<a href="device_read_overwrite.html"><strong>ds_device_read_reply_overwrite<strong></a>. 59