[Buildroot] Which package for bluetooth management?

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Hi! I've searched through the available packages - I'm looking for 
something like bluetoothctl in debian.
I have a working bluez+pulseaudio/alsa system, but I need a way to 
request a pin for incoming connection requests, to trust some addresses 
and to enable BT and BLE profiles as desired.

Is there anything about?
Otherwise I will try to add a package by myself.

Best regards
Marco

[Buildroot] Which package for bluetooth management?

[Arnout Vandecappelle]

On 05/04/16 22:55, Marco Trapanese wrote:
> Hi! I've searched through the available packages - I'm looking for something
> like bluetoothctl in debian.
> I have a working bluez+pulseaudio/alsa system, but I need a way to request a pin
> for incoming connection requests, to trust some addresses and to enable BT and
> BLE profiles as desired.

  Isn't it part of bluez5_utils?

  Regards,
  Arnout

>
> Is there anything about?
> Otherwise I will try to add a package by myself.
>
> Best regards
> Marco
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 05/05/2016 00:40, Arnout Vandecappelle ha scritto:
>
>  Isn't it part of bluez5_utils?

I apologize. I need to use bluez4 due to the issues of bluez5 with 
pulseaudio about HFP profiles.

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 05/05/2016 08:41, Marco Trapanese ha scritto:
>
> I apologize. I need to use bluez4 due to the issues of bluez5 with 
> pulseaudio about HFP profiles.

Anyway I'm rebuilding with bluez5 to see if I can reach my goals. Because:

- bluez4 is recommended with pulseaudio due to simpler configuration of 
A2DP and HFP
- but connman 1.32 doesn't support bluez4 anymore
- but QtConnectivity doesn't support bluez5

It's a bit frustrating :)
So I selected:

- bluez5
- pulseaudio
- connman

Let's see if I can manage A2DP/HFP/BLE services at the same time.

[Buildroot] Which package for bluetooth management?

[Thomas Petazzoni]

Hello,

On Thu, 5 May 2016 09:54:07 +0200, Marco Trapanese wrote:

> - bluez4 is recommended with pulseaudio due to simpler configuration of 
> A2DP and HFP
> - but connman 1.32 doesn't support bluez4 anymore
> - but QtConnectivity doesn't support bluez5

I think it does, see https://patchwork.ozlabs.org/patch/612073/.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 05/05/2016 14:25, Thomas Petazzoni ha scritto:
> - but QtConnectivity doesn't support bluez5
> I think it does, see https://patchwork.ozlabs.org/patch/612073/.


Great!
I will try it... another full rebuild on sight!

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 05/05/2016 14:25, Thomas Petazzoni ha scritto:
> I think it does, see https://patchwork.ozlabs.org/patch/612073/. Thomas 

I apologize, I haven't yet much knowledge about applying patches.
This is what I did:

$git pull
$git apply --stat 
v2-2-2-qt5connectivity-add-bluez5_utils-option-for-QtBluetooth-submodule.patch
$git apply --check 
v2-2-2-qt5connectivity-add-bluez5_utils-option-for-QtBluetooth-submodule.patch

but I got:

error: patch non riuscita: package/qt5/qt5connectivity/Config.in:4
error: package/qt5/qt5connectivity/Config.in: la patch non pu? essere 
applicata
error: patch non riuscita: package/qt5/qt5connectivity/qt5connectivity.mk:20
error: package/qt5/qt5connectivity/qt5connectivity.mk: la patch non pu? 
essere applicata

Thus I opened the file package/qt5/qt5connectivity/Config.in and in fact 
I see a content very different from the "old version" reported in the patch.

My file:

config BR2_PACKAGE_QT5CONNECTIVITY
     bool "qt5connectivity"
     select BR2_PACKAGE_BLUEZ_UTILS
     select BR2_PACKAGE_QT5BASE
     select BR2_PACKAGE_QT5BASE_CONCURRENT
     select BR2_PACKAGE_QT5BASE_DBUS
     depends on !BR2_STATIC_LIBS # bluez_utils
     depends on BR2_USE_WCHAR # bluez_utils
     depends on BR2_TOOLCHAIN_HAS_THREADS # bluez_utils
     depends on BR2_USE_MMU # bluez_utils

what the patch expects:

select BR2_PACKAGE_QT5BASE_CONCURRENT
  	select BR2_PACKAGE_QT5BASE_DBUS
  	depends on !BR2_STATIC_LIBS
- depends on BR2_PACKAGE_NEARD || BR2_PACKAGE_BLUEZ_UTILS
+ depends on BR2_PACKAGE_NEARD || BR2_PACKAGE_BLUEZ_UTILS || 
BR2_PACKAGE_BLUEZ5_UTILS

It seems I have an outdated file, but it's not enough git pull to sync 
with the latest version?
By the way I'm running this one: Buildroot 2016.05-git-01197-gda433d6-dirty

Is there a way to understand on which version the patch was created against?

Thanks for the support
Marco

[Buildroot] Which package for bluetooth management?

[Thomas Petazzoni]

Hello,

On Thu, 5 May 2016 23:29:20 +0200, Marco Trapanese wrote:

> but I got:
> 
> error: patch non riuscita: package/qt5/qt5connectivity/Config.in:4
> error: package/qt5/qt5connectivity/Config.in: la patch non pu? essere 
> applicata
> error: patch non riuscita: package/qt5/qt5connectivity/qt5connectivity.mk:20
> error: package/qt5/qt5connectivity/qt5connectivity.mk: la patch non pu? 
> essere applicata

Please use LANG=C before posting messages to mailing lists. Not
everybody speaks italian :)

> Thus I opened the file package/qt5/qt5connectivity/Config.in and in fact 
> I see a content very different from the "old version" reported in the patch.

The patch I pointed to depends on patch
https://patchwork.ozlabs.org/patch/612072/. You need to apply both.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 05/05/2016 23:37, Thomas Petazzoni ha scritto:
> Please use LANG=C before posting messages to mailing lists. Not 
> everybody speaks italian :) 

I'm sorry, I thought "error" was enough to understand my problem :)

> The patch I pointed to depends on patch 
> https://patchwork.ozlabs.org/patch/612072/. You need to apply both.

Ok, I should have to guess from the name: "v2,2/2".
Generally speaking, I have to apply all the patches that belong to the 
same group.

Last question, a bit off-topic but to better understand how the 
community works: what is the patch "lifetime"? I mean, all committed 
patches will be inserted into the next buildroot stable release?

Best regards
Marco

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 05/05/2016 14:25, Thomas Petazzoni ha scritto:
>> - bluez4 is recommended with pulseaudio due to simpler configuration of
>> A2DP and HFP
>> - but connman 1.32 doesn't support bluez4 anymore
>> - but QtConnectivity doesn't support bluez5
> I think it does, see https://patchwork.ozlabs.org/patch/612073/.


I've just seen bluez5 requires glibc or musl toolchain.
I tried to rebuild all with glibc (instead of uClibc) but the RPi3 
refuses to boot due to a kernel panic.

It's a known behavior? Otherwise I'm afraid I have to do a "regression" 
with older versions.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kernel-panic.jpg
Type: image/jpeg
Size: 137771 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160507/a8f32b0d/attachment-0001.jpg>

[Buildroot] Which package for bluetooth management?

[Arnout Vandecappelle]

On 05/07/16 09:32, Marco Trapanese wrote:
> Il 05/05/2016 14:25, Thomas Petazzoni ha scritto:
>>> - bluez4 is recommended with pulseaudio due to simpler configuration of
>>> A2DP and HFP
>>> - but connman 1.32 doesn't support bluez4 anymore
>>> - but QtConnectivity doesn't support bluez5
>> I think it does, see https://patchwork.ozlabs.org/patch/612073/.
>
>
> I've just seen bluez5 requires glibc or musl toolchain.
> I tried to rebuild all with glibc (instead of uClibc) but the RPi3 refuses to
> boot due to a kernel panic.

  Please use a serial port for debugging: the screenshot isn't really readable, 
and the interesting part has probably scrolled off-screen.

  However, it's extremely unlikely that changing uClibc to glibc would cause a 
kernel panic, because the kernel isn't using libc. So you have probably 
inadvertedly changed something else as well.

  Regards,
  Arnout

>
> It's a known behavior? Otherwise I'm afraid I have to do a "regression" with
> older versions.
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Which package for bluetooth management?

[Thomas Petazzoni]

Hello,

On Sun, 8 May 2016 01:41:37 +0200, Arnout Vandecappelle wrote:

> > I've just seen bluez5 requires glibc or musl toolchain.
> > I tried to rebuild all with glibc (instead of uClibc) but the RPi3 refuses to
> > boot due to a kernel panic.  
> 
>   Please use a serial port for debugging: the screenshot isn't really readable, 
> and the interesting part has probably scrolled off-screen.
> 
>   However, it's extremely unlikely that changing uClibc to glibc would cause a 
> kernel panic, because the kernel isn't using libc. So you have probably 
> inadvertedly changed something else as well.

If you look at the kernel panic from the screenshot (I was able to read
it), it says that init was killed, i.e that the kernel couldn't run it
init. So uClibc vs. glibc could definitely make a difference here.

Marco: could you upload online the tarball image of your root
filesystem, so that we can have a look?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Which package for bluetooth management?

[Marco Trapanese]

Il 08/05/2016 01:41, Arnout Vandecappelle ha scritto:
> I've just seen bluez5 requires glibc or musl toolchain.
>> I tried to rebuild all with glibc (instead of uClibc) but the RPi3 
>> refuses to
>> boot due to a kernel panic.


In the meanwhile I did something weird... but it seems to work.
I used uClibc adding in the config file the following:

UCLIBC_HAS_REGEX=y
UCLIBC_HAS_WORDEXP=y
UCLIBC_HAS_FOPEN_CLOSEEXEC_MODE=y

then I removed the dependency of bluez5_utils from glibc and tried to 
set the latest version: 5.39.

Well... I don't know if it might explode in few minutes but it compiles 
fine and bluez5 is (almost) working.
I have to fix some things like the path of bluetoothd 
(/usr/libexec/bluetooth/ instead of /usr/sbin) and errors on dbus 
(org.bluez.Error.Failed)

But the most important questions is: it's obvious that if I was able to 
enable wordexp in uClibc and you didn't enable it - there is a good 
reason, which I don't know. Perhaps is it not safe?

Best regards
Marco