![]() The controller shall always complete this command promptly with a Command Completed event. HCI_VS_MSFT_Read_Supported_Features provides a bitmap that describes which Microsoft-defined features the controller supports, and specifies the prefix for Microsoft-defined events that are returned by the controller. Windows doesn't send any Microsoft-defined subcommands unless the controller indicates support for the subcommand through a response to HCI_VS_MSFT_Read_Supported_Features. Support for other commands is optional and depends on the values returned by HCI_VS_MSFT_Read_Supported_Features. The first command parameter for the Microsoft-defined HCI command is an opcode that specifies the subcommand.Ĭontrollers must support HCI_VS_MSFT_Read_Supported_Features in order to support any other Microsoft HCI subcommands. The Microsoft-specific command set is extended by using an opcode. The controller understands there's only one Microsoft-specific HCI command. Microsoft-defined HCI command and subcommands Reads the absolute Received Signal Strength Indication (RSSI) value for a BR/EDR connection from the controller. Sets the state of the advertisement filters. HCI_VS_MSFT_LE_Set_Advertisement_Filter_Enable HCI_VS_MSFT_LE_Cancel_Monitor_AdvertisementĬancels a previously issued HCI_VS_MSFT_LE_Monitor_Advertisement command. Requests that the controller starts monitoring for advertisements that fall within the specified RSSI range and also satisfy other requirements. Requests that the controller starts monitoring the measured link RSSI for a specified connection, and generates an event when the connection's measured link RSSI goes outside of the specified bounds.Ĭancels a previously issued HCI_VS_MSFT_Monitor_Rssi command. ![]() Provides a bitmap that describes which Microsoft-defined features the controller supports, and specifies the prefix for Microsoft-defined events that are returned by the controller. Microsoft-defined HCI commands HCI Commands The add registry section should contain: HKR,"VsMsftOpCode",0x00010001, To specify the vendor specific opcode, use the AddReg directive under DDInstall.HW section in the driver's INF. The VsMsftOpCode registry key has a type of REG_DWORD and the key data is the vendor specific opcode. The Windows Bluetooth stack reads the vendor-specific command code from a registry key, VsMsftOpCode. Notifying Windows Bluetooth stack of the vendor specific command code Microsoft doesn't specify how to get the chosen code. The vendor must communicate the chosen value through a method other than the controller. The controller could interpret the command as a destructive operation such as updating the controller's firmware. It's unsafe to issue a vendor-specific command and depend on the controller to reject the command if it doesn't understand it. Microsoft can't choose a command code and assume that no other vendor uses the code for a conflicting purpose. ![]() The vendor must choose the value of the Microsoft-defined command code. Vendors define values in the range 0xFC00 through 0xFFFF, allowing for 1024 different possible vendor-assigned command codes. The Bluetooth organization defines values in the range 0x0000 through 0xFBFF. Requirementsīluetooth HCI commands are identified by a 16-bit command code. Bluetooth controller implementers can use these extensions to implement special features. Microsoft defines vendor-specific HCI commands and events that are consumed by Windows. Bluetooth specifications allow vendor-defined HCI commands and events to enable nonstandardized interaction between hosts and controllers. The Bluetooth Host-Controller Interface (HCI) specifies all interactions between a host and a Bluetooth radio controller.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |