[SOLVED] BlueZ + RN42 Bluetooth module, hciattach fails

[mmaaxx]

Hello, I'm trying to make RN42 (HCI mode), connected to a serial port to ARM9 based SBC, to work under Linux (kernel 2.6.35).

I built kernel with Pretty much all available Bluetooth Options. Installed BlueZ, and DBUS. But, when I'm trying to use hciattach to enumerate the RN42 module it fails:

$ hciattach /dev/ttySP0 csr 115200 nodflow
CSR build ID 0x13-0x33
Can't set line discipline: Invalid argument
Can't initialize device: Invalid argument

Anyone has an idea how to fix this problem?
Thanks!

[mmaaxx]

Just figured it out, posting solution for future reference.

Bluetooth driver registers new TTY discipline (N_HCI), which is used by the hciattach. And this kind of error message means that hciattach tool is missing actual bluetooth kernel driver (or something is wrong with it).

Here is what bluetooth driver prints during a boot:

[    3.140000] Bluetooth: HCI UART driver ver 2.2
[    3.150000] Bluetooth: HCI H4 protocol initialized
[    3.150000] Bluetooth: HCI BCSP protocol initialized
[    3.150000] Bluetooth: HCILL protocol initialized
....
[    4.030000] Bluetooth: L2CAP ver 2.14
[    4.040000] Bluetooth: L2CAP socket layer initialized
[    4.040000] Bluetooth: SCO (Voice Link) ver 0.6
[    4.050000] Bluetooth: SCO socket layer initialized
[    4.050000] Bluetooth: RFCOMM TTY layer initialized
[    4.060000] Bluetooth: RFCOMM socket layer initialized
[    4.060000] Bluetooth: RFCOMM ver 1.11
[    4.070000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.070000] Bluetooth: HIDP (Human Interface Emulation) ver 1.2