diff options
| author | Den Delimarsky <[email protected]> | 2019-03-13 13:01:43 -0700 |
|---|---|---|
| committer | Den Delimarsky <[email protected]> | 2019-03-13 13:01:43 -0700 |
| commit | b376cda09e60215ea229d55e19ade907d84cdf81 (patch) | |
| tree | aad88b2816ac5c59b67be032361eef955052dc20 /bluetooth | |
| parent | f70a523e2345250a2e6daa3a51babc2b0a08818f (diff) | |
Testing samples browser integration
Diffstat (limited to 'bluetooth')
| -rw-r--r-- | bluetooth/bthecho/bthsrv/README.md | 4 | ||||
| -rw-r--r-- | bluetooth/serialhcibus/README.md | 2 |
2 files changed, 2 insertions, 4 deletions
diff --git a/bluetooth/bthecho/bthsrv/README.md b/bluetooth/bthecho/bthsrv/README.md index 6d3c7215..22b969f7 100644 --- a/bluetooth/bthecho/bthsrv/README.md +++ b/bluetooth/bthecho/bthsrv/README.md @@ -226,6 +226,4 @@ One transition to note here is that if disconnect is received in the connecting **Sending and receiving data from server**: When application writes data to the client, client sends this data to server on the connection opened for the given handle. Server would echo back this data. This data is retrieved by the application using a read operation. Echo Sample Client doesn't do any draining of echoed data on its own. Application read/write are handled using a parallel WDF I/O queue. -**Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open. - - +**Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open.
\ No newline at end of file diff --git a/bluetooth/serialhcibus/README.md b/bluetooth/serialhcibus/README.md index 8e585493..9a8fe7cb 100644 --- a/bluetooth/serialhcibus/README.md +++ b/bluetooth/serialhcibus/README.md @@ -75,4 +75,4 @@ device.h - header file for device.c driver.rc - driver version and name -SerialBusWdk.inx - device specific INF file to install this driver. The vendor will need to add the hardware ID to match the "\_HID" for the Serial Bus Device (Bluetooth) in the DSDT.asl file. For example, in SerialBusWDK.inx, the hardware ID is "ACPI\\<*vendor*\>\_BTH0" where <*vendor*\> could be a 4 digit vendor name +SerialBusWdk.inx - device specific INF file to install this driver. The vendor will need to add the hardware ID to match the "\_HID" for the Serial Bus Device (Bluetooth) in the DSDT.asl file. For example, in SerialBusWDK.inx, the hardware ID is "ACPI\\<*vendor*\>\_BTH0" where <*vendor*\> could be a 4 digit vendor name
\ No newline at end of file |