Hi,
On Wed, Nov 21, 2018 at 10:39 AM frv <F.Vieren@...> wrote:

[Edited Message Follows]

Hi Carles,

Probably all is here for the qualification process, correct? : https://www.bluetooth.com/develop-with-bluetooth/qualification-listing

There is a listing for the Host Stack as well:

https://launchstudio.bluetooth.com/ListingDetails/70189

Just wondering do we have extra concerns should we rely on the BlueZ stack at Host side except for the GPL licensing.
Probably when relying on QT which is LGPL and wraps the BlueZ stack we don't have issues around strict GPL licensing?

Is your system going to run Zephyr or Linux/BlueZ as host stack? BlueZ
daemon is GPL but that exposes APIs over D-Bus so you are not really
linking to it, that said the qualification for BlueZ also depends on
the Kernel. There is quite a few listings of BlueZ:

https://launchstudio.bluetooth.com/ListingDetails/65535
https://launchstudio.bluetooth.com/ListingDetails/48333
https://launchstudio.bluetooth.com/ListingDetails/507
https://launchstudio.bluetooth.com/ListingDetails/12555
https://launchstudio.bluetooth.com/ListingDetails/7341
https://launchstudio.bluetooth.com/ListingDetails/17086
https://launchstudio.bluetooth.com/ListingDetails/7319

From looks of them the latest BlueZ listing is for version 5.48,
though depending on the product they may have only some layers
qualified not the entire stack.

Update 9h38 21/11/2018 :
Our company has a SIG account, so I have registered for a user account, to be able to fetch documentation and ask questions.

Best regards,
Frank

--
Luiz Augusto von Dentz