Description

Status: Assigned
Target: $2000
Developer: Oliver Ruiz Dorantes
Deadline: Before the start of GSOC 2008

Bluetooth is wireless low-power network stack. The target of this project is to implement Bluetooth 2.0 in Haiku. Please note, the stack will be written from scratch, the $2000 target would imply motivation to complete the task for a guaranteed deadline before the start of the 2008 GSOC.
 
The major differences between version 2.0 and 1.1 are in the HW specs. The specifications and documentation for the Bluetooth protocol, depending on the version, vary between 1200 and 1500 pages and covers phase 1 and 2 (of this project) plus hardware device specifications. The project I'm proposing has been divided into 3 phases.

The development of the stack will be done while keeping an eye on how Bluetooth was/is implemented in other operating systems, such as Linux and FreeBSD for bluetooth kernel land implementations, MacOS for the user land integration, and SymbianOS or JSR-82 for the possible bluetooth kit.

The reading specs process can be mostly skipped, although it will be used  as well as other OS source code as consulting material. All non-started parts are still to be designed before implementation.

Troubleshooting:

1. Strong dependency with Haiku network stack, which is making it hard to keep developing in R5 (with the self-compiling problem that it implies).
   
2. Hardware availability (1 dongle (damaged), 1 telephone) 

As many of you know from my blog, the project started from scratch with some success. blog, the project started from scratch with some success.

Technical information

Phase 1: Base Stack:
In this phase, the intention is to lay a base for further development, user feedback of the technology, and real communication. In an overview, provide:

• Physical layer of the architecture
  

• User interaction for managing with devices local & remote(discovery, pairing, properties)
  
• Connection oriented / Connectionless services through L2CAP

H2: USB Transport driver (Commands/Events/ACL) 90%

HCI:

•     Core layer
  
•     Userland interface(ioctls/rawsocket) 5%
  
•     Managing tools(bluetoot_server, bluetooth kit) 5%
  

L2CAP (core protocol/sockets)

Deadline: The plan would be having this finished before the start of the GSoC 2008 so that phase 2 or another related bluetooth project could be started within GSoC 2008. In this possible case, we may have such luck again (fingers crossed).


Phase 2: Basic Stack:

The intention of this phase would be complete the stack, and lay the foundation for the 3rd phase.

H2: USB Transport driver (SCO)

Technical Information

Phase 1: Base Stack:

In this phase the intention would be give a a base for further development, user feedback of the technology and real communication. In an overview provide:

• Physical layer of the architecture
  

• User interaction for managing with devices local & remote(discovery, pairing, properties)
  
• Connection oriented / Connectionless services through L2CAP

H2: USB Transport driver (Commands/Events/ACL) 90%

HCI:

•     Core layer
  
•     Userland interface(ioctls/rawsocket) 5%
  
•     Managing tools(bluetoot_server, bluetooth kit) 5%
  

L2CAP (core protocol/sockets)


Deadline: The plan would be having this finish before the starting of the GSoC 2008. So that Phase 2 or another related bluetooth projects could be started within GSoC 2008. In the possible case we have that luck again.


Phase 2: Basic Stack:

The intention of this phase would be complete the stack, and let all prepared for the 3rd phase.


H2: USB Transport driver (SCO)

HCI:

• SCO interface
  
• Managing tools(SDP server & client)

RFCOMM: (core protocol/sockets)


Deadline: To be determined

Phase 3: Upper Protocols, Profiles and Applications:

Bluetooth profiles define how the bluetooth technology functionality is used, while the protocols is the implementation of the technology.

An overview of all these functionalities .

The specifications for each of these profiles do not go beyond 100 pages. So, individuals could easily implement one of these functionalities.

Relevant information

Some links to relevant info:

Project status
General info
Document approach