Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Which package for bluetooth management?
Date: Sat, 7 May 2016 09:32:46 +0200	[thread overview]
Message-ID: <572D9A1E.20609@gmail.com> (raw)
In-Reply-To: <20160505142533.67f8e473@free-electrons.com>

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>

  parent reply	other threads:[~2016-05-07  7:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 20:55 [Buildroot] Which package for bluetooth management? Marco Trapanese
2016-05-04 22:40 ` Arnout Vandecappelle
2016-05-05  6:41   ` Marco Trapanese
2016-05-05  7:54     ` Marco Trapanese
2016-05-05 12:25       ` Thomas Petazzoni
2016-05-05 12:29         ` Marco Trapanese
2016-05-05 21:29         ` Marco Trapanese
2016-05-05 21:37           ` Thomas Petazzoni
2016-05-05 21:47             ` Marco Trapanese
2016-05-07  7:32         ` Marco Trapanese [this message]
2016-05-07 23:41           ` Arnout Vandecappelle
2016-05-08  5:52             ` Thomas Petazzoni
2016-05-08  9:09             ` Marco Trapanese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=572D9A1E.20609@gmail.com \
    --to=marcotrapanese@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox