From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] [V2] BlueZ 5 experimental packages
Date: Mon, 15 Jul 2013 16:50:23 +0300 [thread overview]
Message-ID: <cover.1373896070.git.cristian.iorga@intel.com> (raw)
This sets of patches adds bluez5 recipes as experimental packages.
BlueZ 5.X is not an upgrade for Bluez 4.x, as such, no upgrade is
provided/possible.
The two versions of the BT stack also conflicts each other.
The following changes since commit 74e403705e25afec656b5e40921771a9c29bdc40:
yocto-kernel: make BBLAYERS parsing more robust (2013-07-13 18:23:39 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/bluez57v2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ciorga/bluez57v2
Cristian Iorga (2):
bluez5: new package for v5.7
bluez4: conflicts with/replaces bluez5
meta/recipes-connectivity/bluez/bluez4_4.101.bb | 3 ++
.../bluez5/bluez5-5.7/bluetooth.conf | 16 +++++++
meta/recipes-connectivity/bluez5/bluez5.inc | 45 ++++++++++++++++++++
meta/recipes-connectivity/bluez5/bluez5_5.7.bb | 37 ++++++++++++++++
4 files changed, 101 insertions(+)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5-5.7/bluetooth.conf
create mode 100644 meta/recipes-connectivity/bluez5/bluez5.inc
create mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.7.bb
--
1.7.10.4
next reply other threads:[~2013-07-15 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 13:50 Cristian Iorga [this message]
2013-07-15 13:50 ` [PATCH 2/2] bluez4: conflicts with/replaces bluez5 Cristian Iorga
2013-07-15 15:24 ` Saul Wold
2013-07-15 16:27 ` Phil Blundell
2013-07-15 17:00 ` Burton, Ross
2013-07-16 14:29 ` Iorga, Cristian
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=cover.1373896070.git.cristian.iorga@intel.com \
--to=cristian.iorga@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.