1HCIATTACH(8)              Linux System Administration             HCIATTACH(8)
2
3
4

NAME

6       hciattach - attach serial devices via UART HCI to BlueZ stack
7

SYNOPSIS

9       hciattach [-n] [-p] [-t timeout] tty type|id speed flow
10

DESCRIPTION

12       Hciattach is used to attach a serial UART to the Bluetooth stack as HCI
13       transport interface.
14

OPTIONS

16       -n     Don't detach from controlling terminal.
17
18       -p     Print the PID when detaching.
19
20       -t timeout
21              Specify an initialization timeout.  (Default is 5 seconds.)
22
23       tty    This specifies the serial device to attach. A leading  /dev  can
24              be omitted. Examples: /dev/ttyS1 ttyS2
25
26       type|id
27              The  type  or id of the Bluetooth device that is to be attached,
28              i.e. vendor or other device specific identifier. Currently  sup‐
29              ported types are
30
31              type   description
32
33              any    Unspecified   HCI_UART   interface,  no  vendor  specific
34                     options
35
36              ericsson
37                     Ericsson based modules
38
39              digi   Digianswer based cards
40
41              xircom Xircom PCMCIA cards: Credit Card Adapter  and  Real  Port
42                     Adapter
43
44              csr    CSR  Casira  serial  adapter  or BrainBoxes serial dongle
45                     (BL642)
46
47              bboxes BrainBoxes PCMCIA card (BL620)
48
49              swave  Silicon Wave kits
50
51              bcsp   Serial adapters using CSR chips with BCSP serial protocol
52
53       Supported IDs are (manufacturer id, product id)
54
55              0x0105, 0x080a
56                     Xircom PCMCIA cards: Credit Card Adapter  and  Real  Port
57                     Adapter
58
59              0x0160, 0x0002
60                     BrainBoxes PCMCIA card (BL620)
61
62
63       speed  The speed specifies the UART speed to use. Baudrates higher than
64              115.200bps require vendor specific initializations that are  not
65              implemented  for  all types of devices. In general the following
66              speeds are supported:
67
68              9600, 19200, 38400, 57600, 115200, 230400, 460800, 921600
69
70              Supported vendor devices are automatically initialised to  their
71              respective best settings.
72
73       flow   If  the  keyword  flow  is  appended to the list of options then
74              hardware flow control is forced on the serial link ( CRTSCTS  ).
75              All  above  mentioned  device types have flow set by default. To
76              force no flow control use noflow instead.
77
78

AUTHORS

80       Written by Maxim Krasnyansky <maxk@qualcomm.com>
81
82       Manual page by Nils Faerber <nils@kernelconcepts.de>
83
84
85
86BlueZ                             Jan 22 2002                     HCIATTACH(8)
Impressum