enable bluetooth

-- originally uploaded by VJ Spectra - (?)

++enable bluetooth protocol stacks
http://www.kernel.org
Kernel Device Drivers->Networking Support->
Bluetooth subsystem support->
+L2CAP
+RFCOMM
+RFCTTY
Bluetooth device drivers->HCI USB Driver


0. insmod hci_usb.ko
1. insmod bluebooth.ko
2. insmod l2cap.ko
3. insmod rfcomm.ko

4. hciconfig hci0 up name leflickrBT
5. hcitool dev
Devices:
hci0 00:02:5B:01:CD:FE
6. hcitool scan
Scanning ...
00:12:EE:07:C3:XX W800i
00:20:E0:24:A4:XX 888TIGER-D78C92
00:02:C7:F0:52:XX Xda_Atom_Exec
00:16:XX:XX:XX:XX LeechGSM





++build bluez utils
http://www.bluez.org/redirect.php?url=http%3A%2F%2Fbluez.sf.net%2Fdownload%2Fbluez-utils-3.2.tar.gz
http://www.bluez.org/
must run hcitool utility
Base on bluez-lib
bluez-lib depend on pkg-config
bluez-util depend on dbus
dbus depend on libxml 2.0+


--libxml 2.6
http://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/libxml2-2.6.20.tar.bz2
The libxml2 package contains XML libraries. These are useful for parsing XML files.


--dbus
http://www.freedesktop.org/wiki/Software/dbus
D-Bus is a message bus system, a simple way for applications to talk to
one another. D-Bus supplies both a system daemon (for events such as
"new hardware device added" or "printer queue changed") and a
per-user-login-session daemon (for general IPC needs among user
applications). Also, the message bus is built on top of a general
one-to-one message passing framework, which can be used by any two apps
to communicate directly (without going through the message bus daemon).
Currently the communicating applications are on one computer, but
TCP/IP option is available and remote support planned.

--pkg-config
The pkg-config package contains a tool for passing the include path
and/or library paths to build tools during the configure and make file
execution.
http://pkgconfig.freedesktop.org/releases/pkg-config-0.20.tar.gz

++build bluez-lib
http://www.bluez.org/redirect.php?url=http%3A%2F%2Fbluez.sf.net%2Fdownload%2Fbluez-libs-3.2.tar.gz


++pybluez
http://org.csail.mit.edu/pybluez/
PyBluez is an effort to create python wrappers around system Bluetooth
resources to allow Python developers to easily and quickly create
Bluetooth applications.

Thanks Albert Huang hint me the following information
(sshp-push/sobexsrv)

++sshp-push
http://www.xmailserver.org/ussp-push.html
ussp-push is a OBEX object pusher for Linux, using the BlueZ BlueTooth
stack. The original ussp-push implementation required explicit binding
to RFCOMM channels before the usage, that made it quite cumbersome to
use. I added BlueTooth name resolution, SDP service resolution, and
direct access to remote BlueTooth listening channels. The syntax now
supported by ussp-push is:

$ ussp-push [--dev DEVID] [--timeo TIMEO] {DEVICE, BTADDR@[BTCHAN]} LFILE RFILE


++sobexsrv
http://www.mulliner.org/bluetooth/sobexsrv.php
sobexsrv is a Bluetooth OBEX server with Bluetooth Security Mode-2
(application triggered security) support. It implements OPUSH (put),
OPULL (get) and OBEX-FTP (setpath + directory listing) and therefore is
a full OBEX server. Further it supports pulling generic mime-types and
provides a capability object. sobexsrv was designed with flexibility
and security in mind and supports chroot (if suid root drop to calling
uid immediately). For flexibility a scripting interface provides access
to all functionalities of the server and therefore allows
implementation of further OBEX services on top of sobexsrv.
Thanks Albert Huang hint me the following information
(sshp-push/sobexsrv)

++sshp-push
http://www.xmailserver.org/ussp-push.html
ussp-push is a OBEX object pusher for Linux, using the BlueZ BlueTooth
stack. The original ussp-push implementation required explicit binding
to RFCOMM channels before the usage, that made it quite cumbersome to
use. I added BlueTooth name resolution, SDP service resolution, and
direct access to remote BlueTooth listening channels. The syntax now
supported by ussp-push is:

$ ussp-push [--dev DEVID] [--timeo TIMEO] {DEVICE, BTADDR@[BTCHAN]} LFILE RFILE


++sobexsrv
http://www.mulliner.org/bluetooth/sobexsrv.php
sobexsrv is a Bluetooth OBEX server with Bluetooth Security Mode-2
(application triggered security) support. It implements OPUSH (put),
OPULL (get) and OBEX-FTP (setpath + directory listing) and therefore is
a full OBEX server. Further it supports pulling generic mime-types and
provides a capability object. sobexsrv was designed with flexibility
and security in mind and supports chroot (if suid root drop to calling
uid immediately). For flexibility a scripting interface provides access
to all functionalities of the server and therefore allows
implementation of further OBEX services on top of sobexsrv.
resources to allow Python developers to easily and quickly create
Bluetooth applications.

Thanks Albert Huang hint me the following information
(sshp-push/sobexsrv)

++sshp-push
http://www.xmailserver.org/ussp-push.html
ussp-push is a OBEX object pusher for Linux, using the BlueZ BlueTooth
stack. The original ussp-push implementation required explicit binding
to RFCOMM channels before the usage, that made it quite cumbersome to
use. I added BlueTooth name resolution, SDP service resolution, and
direct access to remote BlueTooth listening channels. The syntax now
supported by ussp-push is:

$ ussp-push [--dev DEVID] [--timeo TIMEO] {DEVICE, BTADDR@[BTCHAN]} LFILE RFILE


++sobexsrv
http://www.mulliner.org/bluetooth/sobexsrv.php
sobexsrv is a Bluetooth OBEX server with Bluetooth Security Mode-2
(application triggered security) support. It implements OPUSH (put),
OPULL (get) and OBEX-FTP (setpath + directory listing) and therefore is
a full OBEX server. Further it supports pulling generic mime-types and
provides a capability object. sobexsrv was designed with flexibility
and security in mind and supports chroot (if suid root drop to calling
uid immediately). For flexibility a scripting interface provides access
to all functionalities of the server and therefore allows
implementation of further OBEX services on top of sobexsrv.
3. insmod rfcomm.ko

4. hciconfig hci0 up name leflickrBT
5. hcitool dev
Devices:
hci0 00:02:5B:01:CD:FE
6. hcitool scan
Scanning ...
00:12:EE:07:C3:XX W800i
00:20:E0:24:A4:XX 888TIGER-D78C92
00:02:C7:F0:52:XX Xda_Atom_Exec
00:16:XX:XX:XX:XX LeechGSM





++build bluez utils
http://www.bluez.org/redirect.php?url=http%3A%2F%2Fbluez.sf.net%2Fdownload%2Fbluez-utils-3.2.tar.gz
http://www.bluez.org/
must run hcitool utility
Base on bluez-lib
bluez-lib depend on pkg-config
bluez-util depend on dbus
dbus depend on libxml 2.0+


--libxml 2.6
http://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/libxml2-2.6.20.tar.bz2
The libxml2 package contains XML libraries. These are useful for parsing XML files.


--dbus
http://www.freedesktop.org/wiki/Software/dbus
D-Bus is a message bus system, a simple way for applications to talk to
one another. D-Bus supplies both a system daemon (for events such as
"new hardware device added" or "printer queue changed") and a
per-user-login-session daemon (for general IPC needs among user
applications). Also, the message bus is built on top of a general
one-to-one message passing framework, which can be used by any two apps
to communicate directly (without going through the message bus daemon).
Currently the communicating applications are on one computer, but
TCP/IP option is available and remote support planned.

--pkg-config
The pkg-config package contains a tool for passing the include path
and/or library paths to build tools during the configure and make file
execution.
http://pkgconfig.freedesktop.org/releases/pkg-config-0.20.tar.gz

++build bluez-lib
http://www.bluez.org/redirect.php?url=http%3A%2F%2Fbluez.sf.net%2Fdownload%2Fbluez-libs-3.2.tar.gz


++pybluez
http://org.csail.mit.edu/pybluez/
PyBluez is an effort to create python wrappers around system Bluetooth
resources to allow Python developers to easily and quickly create
Bluetooth applications.

Thanks Albert Huang hint me the following information
(sshp-push/sobexsrv)

++sshp-push
http://www.xmailserver.org/ussp-push.html
ussp-push is a OBEX object pusher for Linux, using the BlueZ BlueTooth
stack. The original ussp-push implementation required explicit binding
to RFCOMM channels before the usage, that made it quite cumbersome to
use. I added BlueTooth name resolution, SDP service resolution, and
direct access to remote BlueTooth listening channels. The syntax now
supported by ussp-push is:

$ ussp-push [--dev DEVID] [--timeo TIMEO] {DEVICE, BTADDR@[BTCHAN]} LFILE RFILE


++sobexsrv
http://www.mulliner.org/bluetooth/sobexsrv.php
sobexsrv is a Bluetooth OBEX server with Bluetooth Security Mode-2
(application triggered security) support. It implements OPUSH (put),
OPULL (get) and OBEX-FTP (setpath + directory listing) and therefore is
a full OBEX server. Further it supports pulling generic mime-types and
provides a capability object. sobexsrv was designed with flexibility
and security in mind and supports chroot (if suid root drop to calling
uid immediately). For flexibility a scripting interface provides access
to all functionalities of the server and therefore allows
implementation of further OBEX services on top of sobexsrv.
stack. The original ussp-push implementation required explicit binding
to RFCOMM channels before the usage, that made it quite cumbersome to
use. I added BlueTooth name resolution, SDP service resolution, and
direct access to remote BlueTooth listening channels. The syntax now
supported by ussp-push is:

$ ussp-push [--dev DEVID] [--timeo TIMEO] {DEVICE, BTADDR@[BTCHAN]} LFILE RFILE


++sobexsrv
http://www.mulliner.org/bluetooth/sobexsrv.php
sobexsrv is a Bluetooth OBEX server with Bluetooth Security Mode-2
(application triggered security) support. It implements OPUSH (put),
OPULL (get) and OBEX-FTP (setpath + directory listing) and therefore is
a full OBEX server. Further it supports pulling generic mime-types and
provides a capability object. sobexsrv was designed with flexibility
and security in mind and supports chroot (if suid root drop to calling
uid immediately). For flexibility a scripting interface provides access
to all functionalities of the server and therefore allows
implementation of further OBEX services on top of sobexsrv.