Bluetopia? Buletooth stack for AmigaOS4.x maybe?

@LiveForIt

Unfortunately, you can forget bluetooth on Amigoid platform. Platon (poseidon author) looked into this as did rest of morphos guys and its extremely cost prohibitive.

@all

Bounty? I would donate for sure!

For me Wireless support is much higher priority.

What about open-source instead of proprietary port?

https://www.broadcom.com/press/release.php?id=s721534

http://www.bluez.org/faq/common/

https://code.google.com/p/btstack/

etc...

@magnetic
Licensing?

@magnetic

is it possible that you are confusing Bluetooth wiht Blueray?

@DrZarkov

Quote:

I don't think so. IIRC, to be allowed to use the Bluetooth name and logo with your Bluetooth stack, you have to pay a license fee and get certified. I can't remember if its a one time fee, or an annual one. Regardless, it costs a lot of money.

Hans

@Hans

Do you need to call it "bluetooth" though? Or is the functionality itself in need of licensing?

Bluetooth isn't very high priority for me, but if it were and was called redgum, I really wouldn't care

@broadblues

Well, you probably need to at least mention "Bluetooth" somewhere, for people to know what it is. I have no idea if the functionality itself needs licensing; that would depend on whether any patents are involved.

I personally never looked into this in any great detail. However, I also remember Poseidon's author saying something about legal/licensing issues killing his Bluetooth stack plans.

Hans

Call it RedTooth....

I don't care about the logo and the name. IMHO they can call the stack "Harald" and write about the IEEE 802.15.1 compatible WPAN-stack in the manual. As long as it works it's fine for me.

@DrZarkov

No, i'm not confused at all. look into it.

Maybe you can call the stack what you want,but the end device will have a bluetooth logo on it,so there may still be a problem.

There's also the frequency range reserved for bluetooth,so if this is used this could be another problem.

@delshay

I do not get what you are trying to say. The fact the device has a logo does not imply anything: they already paid the licence fee to stick this logo on them. As with the frequency used: that is the device maker's responsibility: neither the user, nor the stack developer can be liable for it (device should have obtained an FCC agreement or similar).

Moreover as for the Bluetooth fees according to Bluetooth SIG website (here) you should be member to develop anything based upon their specifications, but from the above mentioned webpage one can read that "Adopter membership" is free. Qualification process and listing product are not free (~$8.000 USD) however I was not able to determine if those are *required*.

@abalaban

Okay,disregard my posting in this thread,I now have better understanding from the link you provided.

Thanks.