From: Saul Wold <sgw@linux.intel.com>
To: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>,
"Iorga, Cristian" <cristian.iorga@intel.com>,
"Burton, Ross" <ross.burton@intel.com>
Subject: Thoughts about bluez4 and bluez5
Date: Thu, 25 Jul 2013 09:23:49 -0700 [thread overview]
Message-ID: <51F15115.3040008@linux.intel.com> (raw)
Cristi, Ross:
There is currently a PREFERRED_PROVIDER issue with bluez4 and bluez5 and
I am beginning to think we need to distinguish the
libasound-module-bluez with libasound-module-bluez5.
I am also seeing some areas where we might need a virtual/bluez to allow
recipes to enable features in places like connman and ofono
Thoughts?
--
Sau!
Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System
next reply other threads:[~2013-07-25 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 16:23 Saul Wold [this message]
2013-07-26 5:50 ` Thoughts about bluez4 and bluez5 Iorga, Cristian
[not found] ` <969F26A8BAB325438E7EB80D3C3134FB16C0F03E@IRSMSX105.ger.corp.intel.com>
2013-07-29 6:39 ` Saul Wold
2013-07-29 6:41 ` 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=51F15115.3040008@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cristian.iorga@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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