Bluetooth Driver services: Difference between revisions
No edit summary |
|||
| Line 430: | Line 430: | ||
This copies 0x400-bytes from state to the output buffer, copies the [[#EventType]] from state to output, and signals an event. | This copies 0x400-bytes from state to the output buffer, copies the [[#EventType]] from state to output, and signals an event. | ||
[12.0.0+] Mutex locking is now used, with the code prior to the event-signal. If a size field in state is 0, writing the output [[#EventType]]/buffer is skipped. Otherwise, the size field is reset to 0, the [[#EventType]] from state is copied to output, and the original size field is used to memcpy to the output buffer from state. | |||
This is used by [[BTM_services|btm]]. | This is used by [[BTM_services|btm]]. | ||
| Line 522: | Line 524: | ||
This copies 0x480-bytes from state to the output buffer. [[#HidEventType]] is set to: stateval!=0 ? 7 : 0. Once finished, this signals an event. | This copies 0x480-bytes from state to the output buffer. [[#HidEventType]] is set to: stateval!=0 ? 7 : 0. Once finished, this signals an event. | ||
[12.0.0+] Mutex locking is now used, with the code prior to the event-signal. If a size field in state is 0, writing the output [[#HidEventType]]/buffer is skipped. Otherwise, the size field is reset to 0, the [[#HidEventType]] from state is copied to output, and the original size field is used to memcpy to the output buffer from state. | |||
This is used by [[BTM_services|btm]]. | This is used by [[BTM_services|btm]]. | ||