[Buildroot] BlueZ and Bluetooth-SIG

[Heiko Abraham]

Hi Baruch

I talk also with the bluez-mailing list, our bt-chip-distributor (u-blox) and our test-lab (7-layer).

As I can see, the problem exists with many LTS linux kernels. I don't know any combination that succeeds the tests.
If I understand the bluez mailing list well, some backports or patches are required.

So, my assumption is, that this patches are useful (or required) for buildroot.


Regards,
Heiko

> Am 12.07.2017 um 10:28 schrieb Baruch Siach <baruch at tkos.co.il>:
>
> Hi Heiko,
>
> On Wed, Jul 12, 2017 at 08:18:19AM +0000, Heiko Abraham wrote:
>> I test different versions of linux-kernels (3.10, 3.12, 3.18 for
>> i.MX5/i.MX6) and BlueZ (4.101, 5.43, 5,45) but all combinations failed with
>> Bluetooth-SIG test.
>> (Problems with eRTM and l2cap_disconnect for RFCOMM profile)
>>
>> My assumption is, that an lot of LTS-kernel/BlueZ combinations are not
>> compliant with Bluetooth-SIG. But that is required for an BT based embedded
>> system.
>> Please note, some targets required an older linux kernel for OpenGL support.
>>
>> Any suggestions, how to get an buildroot build, that compliant with
>> bluetooth-sig?
>
> Is this issue specific to Buildroot?
>
> Does the Bluetooth-SIG compliance test succeeds on other Linux distributions?
>
> baruch
>
> --
>     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


________________________________

--
Hella Gutmann Solutions GmbH * Unternehmensform: Gesellschaft mit beschraenkter Haftung *
Firmensitz: 79241 Ihringen * Eingetragen im Handelsregister: AG Freiburg i.Br., HRB 290194 * Geschaeftsfuehrer: Andreas Habeck * USt-IdNr.: DE142208666