Bluetooth support in Oleg's firmware?

[Gart]

thank you.
Now, after loading bluez.o, and then rfcomm.o, I don't get any errors.
but when I plug in my bt dongle, I get in dmesg:
hub.c: new USB device 00:04.0-1.3, assigned address 15
usb.c: USB device 15 (vend/prod 0xa12/0x1) is not claimed by any active driver.

You also need to load hci_usb.o. This is the driver for the USB dongle itself.
Here are the modules which might be needed for Bluetooth:
bluez.o - main functionality
hci_usb.o - USB dongle driver
rfcomm.o - Radio COM-port
bnep.o - Bluetooth network
l2cap.o - L2CAP protocol, might be useful to ping Bluetooth devices
sco.o - for Bluetooth audio
After you load all the needed modules and insert the dongle it should print in the system log

Feb 23 21:39:48 kernel: BlueZ Core ver 2.2 Copyright (C) 2000,2001 Qualcomm Inc
Feb 23 21:39:48 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Feb 23 21:40:03 kernel: BlueZ L2CAP ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Feb 23 21:40:03 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Feb 23 21:40:17 kernel: BlueZ SCO ver 0.3 Copyright (C) 2000,2001 Qualcomm Inc
Feb 23 21:40:17 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Feb 23 21:40:32 kernel: BlueZ BNEP ver 1.0
Feb 23 21:40:32 kernel: Copyright (C) 2001,2002 Inventel Systemes
Feb 23 21:40:32 kernel: Written 2001,2002 by Clement Moreau <clement.moreau@inventel.fr>
Feb 23 21:40:32 kernel: Written 2001,2002 by David Libault <david.libault@inventel.fr>
Feb 23 21:40:32 kernel: Copyright (C) 2002 Maxim Krasnyanskiy <maxk@qualcomm.com>
Feb 23 21:40:38 kernel: BlueZ RFCOMM ver 0.4
Feb 23 21:40:38 kernel: Copyright (C) 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Feb 23 21:40:38 kernel: Copyright (C) 2002 Marcel Holtmann <marcel@holtmann.org>
Feb 23 21:40:44 kernel: BlueZ HCI USB driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Feb 23 21:40:44 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Feb 23 21:40:44 kernel: usb.c: registered new driver hci_usb

To make the router visible to other Bluetooth devices some additional steps may be required depending on your configuration

1. The latest version of hcid daemon from bluez-utils needs to get dbus-daemon running. Its config file /opt/etc/dbus-1/system.conf expects the root user to be named "root" so you may need to change that to <user>admin</user>, and then start dbus-daemon --system

2. Edit the hcid.conf file in /opt/etc/bluetooth . It's rather self-explanatory.

3. Start the hcid daemon. If everything goes fine it should print in the system log

Feb 23 21:41:50 hcid[309]: HCI dev 0 registered
Feb 23 21:41:50 hcid[309]: HCI dev 0 up
Feb 23 21:41:50 hcid[309]: Device hci0 has been added
Feb 23 21:41:50 input[311]: Bluetooth Input daemon
Feb 23 21:41:50 hcid[309]: Starting security manager 0
Feb 23 21:41:50 input[311]: Registered input manager path:/org/bluez/input
Feb 23 21:41:50 hcid[309]: Device hci0 has been activated

4. Type hciconfig hci0 up piscan to activate the dongle, and then hciconfig to check if the USB dongle is running. It should print something like this

hci0:   Type: USB
        BD Address: 00:02:5B:01:16:5E ACL MTU: 384:8 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:36390 acl:922 sco:0 events:1358 errors:0
        TX bytes:26231 acl:843 sco:0 commands:218 errors:0

5. Start the sdpd daemon and use the sdptool to add local services to the Bluetooth dongle. For example, if you need a Bluetooth serial port on channel 2 type sdptool add --channel 2 SP

6. After all that the router should be visible to other Bluetooth devices. You may use the rfcomm utility to make a serial port connection or dund to set up a PPP connection over Bluetooth.

Any comments and suggestions are welcome.