summaryrefslogtreecommitdiff
path: root/bluetooth
diff options
context:
space:
mode:
authorDen Delimarsky <[email protected]>2019-03-13 20:01:10 -0700
committerDen Delimarsky <[email protected]>2019-03-13 20:01:10 -0700
commit18cabc43191fd82420adcfac56c0361de98360c9 (patch)
tree09550ec1eeb8a83aab5ac9bba6215e2b8d0b72c0 /bluetooth
parentdbc7785c3a7ced56ecac6b5a9dfb81ef45dedac6 (diff)
Diffstat (limited to 'bluetooth')
-rw-r--r--bluetooth/bthecho/bthsrv/README.md2
-rw-r--r--bluetooth/serialhcibus/README.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/bluetooth/bthecho/bthsrv/README.md b/bluetooth/bthecho/bthsrv/README.md
index dedc6646..bee26b0f 100644
--- a/bluetooth/bthecho/bthsrv/README.md
+++ b/bluetooth/bthecho/bthsrv/README.md
@@ -225,4 +225,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. \ No newline at end of file
+**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.
diff --git a/bluetooth/serialhcibus/README.md b/bluetooth/serialhcibus/README.md
index 460b3923..e93c9fee 100644
--- a/bluetooth/serialhcibus/README.md
+++ b/bluetooth/serialhcibus/README.md
@@ -74,4 +74,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. \ No newline at end of file
+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.