From: "Peter A. Bigot" <pab@pabigot.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: viability of bluez5 in next OE development cycle?
Date: Mon, 20 Oct 2014 09:50:13 -0500 [thread overview]
Message-ID: <54452125.1080108@pabigot.com> (raw)
There's this bugzilla entry:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5031
I see a NAKd patch set from about 26 Mar 2014 which tried to add
virtual/bluez. The outcome was that a rework would be done and tested
and resubmitted latter. In the related discussion there was some concern
that dependent packages were still not ready to move even though the
last bluez4 release was in June 2012.
With a little local hacking I can get bluez5 working well enough for my
BTLE needs on beaglebone (mostly s/bluez4/bluez5/g and a PROVIDER for
bluez-hcidump). Does anybody have plans to work this during the early
1.8 development cycle? It looks pretty straightforward, but Idon't use
BT in enough variants and packages to be able to test the full set of
required patches.
Peter
next reply other threads:[~2014-10-20 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 14:50 Peter A. Bigot [this message]
2014-10-20 14:58 ` viability of bluez5 in next OE development cycle? Burton, Ross
2014-10-20 17:01 ` Peter A. Bigot
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=54452125.1080108@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.org \
/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