From: Saul Wold <sgw@linux.intel.com>
To: "Iorga, Cristian" <cristian.iorga@intel.com>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Re: Thoughts about bluez4 and bluez5
Date: Sun, 28 Jul 2013 23:39:44 -0700 [thread overview]
Message-ID: <51F60E30.5030200@linux.intel.com> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB16C0F03E@IRSMSX105.ger.corp.intel.com>
On 07/28/2013 11:34 PM, Iorga, Cristian wrote:
> Back from the past!!
>
> -----Original Message-----
> From: Iorga, Cristian
> Sent: Friday, July 26, 2013 8:51 AM
> To: 'Saul Wold'; 'Patches and discussions about the oe-core layer'; Burton, Ross
> Subject: RE: Thoughts about bluez4 and bluez5
>
> Hi Saul, Ross,
>
> I think that for the time being libasound-module-bluez should be libasound-module-bluez5.
> We will get back to it after 1.5, when all components will be ready for BlueZ 5.
This can not wait until after 1.5, it's a note and needs to be addressed
now. Martin has also reported this issue to you as well.
> On the second issue, can you please go into details? I am not following exactly.
It's possible for new version of ofono or connman to want to use bluez5,
via the PACKAGECONFIG settings, we need to allow that to happen with out
having to embed bluez4 vs bluez5 in the recipe, this can be done with a
virtual/bluez style of declartion you can see examples of this for
virtual/libc and in the meta/conf/distro/include/default-providers.inc file
Sau!
> Regards,
> Cristian
>
> -----Original Message-----
> From: Saul Wold [mailto:sgw@linux.intel.com]
> Sent: Thursday, July 25, 2013 7:24 PM
> To: 'Patches and discussions about the oe-core layer'; Iorga, Cristian; Burton, Ross
> Subject: Thoughts about bluez4 and bluez5
>
>
>
> 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?
>
>
>
next prev parent reply other threads:[~2013-07-29 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 16:23 Thoughts about bluez4 and bluez5 Saul Wold
2013-07-26 5:50 ` Iorga, Cristian
[not found] ` <969F26A8BAB325438E7EB80D3C3134FB16C0F03E@IRSMSX105.ger.corp.intel.com>
2013-07-29 6:39 ` Saul Wold [this message]
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=51F60E30.5030200@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=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.