Hello.


I have several bluetooth devices.

Sony mini-HiFi system
Playstation 3
Nokia E90
etc... and list goes on and on...

Wonder if it would be possible to develop a Bluetooth driver for MorphOS? There are several bluetooth usb sticks on the marked which would be perfect for streaming music to a Bluetooth device like my Sony mini-HiFi system etc.

I am sure there are lots having Bluetooth devices that would be great to control from a mediacenter made of Efika or even macmini G4. Also a good reason for this is that your wife will be happier :) less cables, then better :) hehe...


Michal

The problem is that you need far more than just the driver: You need a bluetooth stack (much like USB stack I believe).

Just like USB doesn't quite work with just the USB driver, bluetooth won't either.

[ Edited by Piru on 2009/7/9 10:49 ]

Chris Hodge has made a BT class to use BT dongle trough USB.
It's only the interface between USB <-> BT HCI (Host Controller Interface).
Then HCI is also only a logic layer before the L2CAP (Logical Link Control and Adaptation Protocol) layer.

So:

1 - we need to develop a HCI driver.
2 - we need to develop a L2CAP driver.

It's not finished because we need to develop a class for each profile (like HID profile for the Wiimote )

[ Edited by Yomgui on 2009/7/9 11:02 ]

An old thread about this, so first target would be the license at USD 10k and then you need to pay the developer.

My Bluetooth stack sources from 2005/2006 (?) are currently in the MorphOS repository. They include a basic HCI layer, ACL layer, L2CAP layer, Service Discovery Profile, incomplete RFCOMM, AVDTP layer and an incomplete A2DP implementation (but I had my A2DP headphones streaming MP3s from the Amiga at that time).

If somebody wants to pick up the project, he's welcome. Notice that once the product is finished, official qualification testing must be done with the BT Sig -- otherwise the release is illegal. This requires BT Sig membership for 3500 to 7000 USD per year.

Is releasing sources only illegal too ?
maybe LABS Ain't an Bluetooth Stack project ?

@Chris

isn't possible to release the stack as "TeethBrush" and avoiding any reference to BlueTooth devices? Even more, you could state that your stack is incompatible with BlueTooth and shouldn't be used with BlueTooth devices.

"TeethBrush, the stack that shouldn't be used with BlueTooth devices"

In the worst case perhaps the sources could be distributed with a makefile and an script that compiles and installs it with the SDK.

About the Linux stack: it's listed on the linux BT stack site firms that use Linux + BlueZ on their devices, like Nokia or TomTom. These ones have paid the BlueTooth SIG, you can search BlueZ on the SIG web site to check that.

But... not all PC constructors, nor the FSF has paid for the usage of the stack on PC. So it comes to my mind this: the distribution and the usage of the software (the BT stack so) seems to be possible if no incomes are made with it. The Linux BT stack is distributed as an OpenSource software under the GPL license.

Now, Nokia or TomTom use it also, but make incomes by selling their devices.

I don't know the matter and content of the discution between Chris and the SIG, but Chris, have you talked about this fact with them?
In this case, the code of the BT stack shall be freely distributed and not included with the MorphOS iso (not free, for the 2.x).
And also, maybe the code shall be open-sourced...

Don't know... We should ask to the SIG to have the final word.

Note: it seems that Samsung has paid for the Stack qualification.

so there's quite a number of obstacles for now (especially the licence stuff). But having BT keyboard support would be fantastic for the release of MorphOS for Mac Mini. I have an apple bt keyboard that i use with OSX and switching back to a wired usb keyboard for MorphOS won't make my mac mini as sexy as it is now.

Would it help to keep it in a prerelease state, so that it's permanently kept in a testing state?

[ Edited by analogkid on 2009/7/14 11:54 ]

And would it be possible to use small parts of BlueZ and claim that it *is* BlueZ on MorphOS?