hciattach.rst 4.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166
  1. =========
  2. hciattach
  3. =========
  4. -------------------------------------------------
  5. attach serial devices via UART HCI to BlueZ stack
  6. -------------------------------------------------
  7. :Authors: - Maxim Krasnyansky <maxk@qualcomm.com>
  8. - Nils Faerber <nils@kernelconcepts.de>
  9. :Version: BlueZ
  10. :Copyright: Free use of this software is granted under ther terms of the GNU
  11. Lesser General Public Licenses (LGPL).
  12. :Date: Jan 22, 2002
  13. :Manual section: 1
  14. :Manual group: Linux System Administration
  15. SYNOPSIS
  16. ========
  17. **hciattach** [*OPTIONS*] <*tty*> <*type|id*> [*speed*] [*flow*] [*sleep*] [*bdaddr*]
  18. **hciattach** -1
  19. DESCRIPTION
  20. ===========
  21. **hciattach(1)** is used to attach a serial UART to the Bluetooth stack as HCI
  22. transport interface.
  23. OPTIONS
  24. =======
  25. -i Send break
  26. -n Don't detach from controlling terminal.
  27. -p Print the PID when detaching.
  28. -t timeout Specify an initialization timeout. Default is 5 seconds.
  29. -s speed Specify an initial speed instead of the hardware default.
  30. -l List all available configurations.
  31. -r Set the HCI device into raw mode. The kernel and bluetooth daemon
  32. will ignore it.
  33. -h, --help Show help options
  34. ARGUMENTS
  35. =========
  36. *show*
  37. This specifies the serial device to attach. A leading /dev can be omitted.
  38. Examples: **/dev/ttyS1 ttyS2**
  39. *type|id*
  40. The *type* or *id* of the Bluetooth device that is to be attached,
  41. i.e. vendor or other device specific identifier.
  42. Currently supported types are
  43. .. list-table::
  44. :header-rows: 1
  45. :widths: auto
  46. * - *type*
  47. - Description
  48. * - any
  49. - Unspecified HCI_UART interface, no vendor specific options
  50. * - ericsson
  51. - Ericsson based modules
  52. * - digi
  53. - Digianswer based cards
  54. * - xircom
  55. - Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter
  56. * - csr
  57. - CSR Casira serial adapter or BrainBoxes serial dongle (BL642)
  58. * - bboxes
  59. - BrainBoxes PCMCIA card (BL620)
  60. * - swave
  61. - Silicon Wave kits
  62. * - bcsp
  63. - Serial adapters using CSR chips with BCSP serial protocol
  64. * - ath3k
  65. - Atheros AR300x based serial Bluetooth device
  66. * - intel
  67. - Intel Bluetooth device
  68. .. list-table::
  69. :header-rows: 1
  70. :widths: auto
  71. * - | Supported ID
  72. | (manufacturer id, product id)
  73. - Description
  74. * - 0x0105, 0x080a
  75. - Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter
  76. * - 0x0160, 0x0002
  77. - BrainBoxes PCMCIA card (BL620)
  78. *speed*
  79. The *speed* specifies the UART speed to use. Baudrates higher than 115200bps
  80. require vendor specific initializations that are not implemented for all
  81. types of devices. In general the following speeds are supported:
  82. Supported vendor devices are automatically initialised to their respective
  83. best settings.
  84. .. list-table::
  85. :header-rows: 0
  86. :widths: auto
  87. * - 9600
  88. * - 19200
  89. * - 38400
  90. * - 57600
  91. * - 115200
  92. * - 230400
  93. * - 460800
  94. * - 921600
  95. *flow*
  96. If the *flow* is appended to the list of options then hardware flow control
  97. is forced on the serial link (**CRTSCTS**). All above mentioned device
  98. types have flow set by default. To force no flow control use *noflow*
  99. instead.
  100. *sleep|nosleep*
  101. Enables hardware specific power management feature. If *sleep* is appended
  102. to the list of options then this feature is enabled. To disable this
  103. feature use *nosleep* instead. All above mentioned device types have
  104. *nosleep* set by default.
  105. Note: This option will only be valid for hardware which support hardware
  106. specific power management enable option from host.
  107. *bdaddr*
  108. The bdaddr specifies the Bluetooth Address to use. Some devices (like
  109. the STLC2500) do not store the Bluetooth address in hardware memory.
  110. Instead it must be uploaded during the initialization process. If this
  111. argument is specified, then the address will be used to initialize the
  112. device. Otherwise, a default address will be used.
  113. RESOURCES
  114. =========
  115. http://www.bluez.org
  116. REPORTING BUGS
  117. ==============
  118. linux-bluetooth@vger.kernel.org