|
1 This is an implementation of the Bluetooth USB HCTL for the Symbian |
|
2 USB Host driver interface. |
|
3 |
|
4 Note that this implementation is based on the classic "H2" |
|
5 specification, as such it is not completely compatible with the |
|
6 updated version published with the Bluetooth Core Specification |
|
7 3.0+HS (and onwards). |
|
8 |
|
9 There are two distinct components: |
|
10 * The HCTL Plugin - this provides the Bluetooth transport |
|
11 layer adaptation implementation through the USB driver |
|
12 interface. |
|
13 * The FDC Plugin - this is receives the driver information |
|
14 from the USB Function Driver Framework, it validates the |
|
15 device before supplying the notifications of device |
|
16 attachment/detachment to the HCTL. |
|
17 |
|
18 Both these components must be present for the system to be |
|
19 functional, they can be included in a ROM image with the provided |
|
20 iby file: |
|
21 hctl_usb_original.iby |
|
22 |
|
23 If the reference CoreHCI is in use then a simple macro definition |
|
24 is all that is required to include the iby file. The macro to use |
|
25 is HCI_USB; below is an example of its use: |
|
26 buildrom ... -DHCI_USB |
|
27 |
|
28 To configure the Bluetooth stack to use this driver, the CoreHCI |
|
29 implementation must be appropriately configured to use this |
|
30 implementation. Typically this is through an ini file in the |
|
31 ESock data cage - in the Symbian file system this would be located: |
|
32 |
|
33 z:\private\101f7989\bluetooth\corehci_symbian.ini |
|
34 |
|
35 In this file you should indicate the HCTL Plugin implementation |
|
36 UID (0x200345E7): |
|
37 |
|
38 hctl_uid= 0x200345E7 |
|
39 |
|
40 An example configuration is provided in the Symbian reference |
|
41 CoreHCI: |
|
42 |
|
43 corehci_symbian_usboriginal.ini |
|
44 |
|
45 This should be all that is required to configure the use of the |
|
46 driver. The FDF should automatically load the FDC plugin when |
|
47 a Bluetooth device is attached to the USB bus. When no device is |
|
48 attached then behaviour of the Bluetooth stack is the same as if |
|
49 Bluetooth controllers power had been switched off (i.e. through the |
|
50 power control API). |
|
51 |