bluetooth

[Hans_]

@platon42

Are you still developing the Bluetooth stack? You could initially release it without qualifying. I know that this is not the way you'd prefer to go, but it is an option. You would not be allowed to include the Bluetooth logo and would have to state that it's "Bluetooth compatible but not qualified".

Another option would be to set up a donation site. If you design the stack to work with the 68k AmigaOS, AmigaOS4, Morphos, and AROS, we might be able to scrape together the cash. It'll be a pity that all the money will go toward qualification, instead of rewarding you for your hard work.

The BlueZ stack for Linux was qualified with the help from TomTom who probably paid for it. Have you tried contacting Amiga Inc., Hyperion or Genesi? It's worth a try. Contacting DiscreetFX might be an idea as well. They've announced an interest in buying Amiga Inc. and appear to be interested in pushing the Amiga forward.

I hope you can find a way to proceed somehow as Bluetooth is becoming more and more important. It would be a real shame for all your work to go to waste.

Hans

[Hans_]

Does anyone else have any suggestions? From the sounds of it, Platon42 has already done quite a bit of work on a Bluetooth stack. Bluetooth devices are becoming more and more numerous. Wii's controller, for example, uses Bluetooth.

All we need is to either come up with $10,000 USD, or, find a way that Platon42 can release his work without it. The way I see it, there's nothing wrong with using a non qualified stack to communicate with Bluetooth devices. This is the same thing as MESA being OpenGL compatible, but not OpenGL certified. MESA can't use the OpenGL logo, but OpenGL apps still compile and run with it. Surely Platon42 could release it under a name other than Bluetooth and provide necessary disclaimers saying it hasn't been qualified and hence is not guaranteed to work with all devices (just because it hasn't gone through the testing procedures)?

So, any other creative ideas?

Hans