From: Stefan Schmidt <stefan@datenfreihafen.org>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 1/2] wpa-supplicant: change dbus interface
Date: Mon, 14 Feb 2011 08:31:13 +0100 [thread overview]
Message-ID: <20110214073113.GA14931@excalibur.local> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A33285081@shsmsx501.ccr.corp.intel.com>
Hello.
On Mon, 2011-02-14 at 08:55, Xu, Dongxiao wrote:
>
> Stefan Schmidt wrote:
> > Hello.
> >
> > On Fri, 2011-02-11 at 17:11, Dongxiao Xu wrote:
> >> From: Dongxiao Xu <dongxiao.xu@intel.com>
> >>
> >> # Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
> >> #CONFIG_DRIVER_BSD=y @@ -404,4 +405,4 @@ CONFIG_PEERKEY=y #LIBS_c +=
> >> -lbfd -liberty -lz CONFIG_TLS = gnutls CONFIG_GNUTLS_EXTRA=y
> >> -CONFIG_CTRL_IFACE_DBUS=y
> >> +CONFIG_CTRL_IFACE_DBUS_NEW=y
> >
> > Any reason not enable both dbus interfaces? They can happily life
> > next to each other. Thats how I did it in OE.
>
> It is OK for me to enable both options. I will change it in my next pull request.
Thanks.
> >> diff --git
> >> a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-0.7.inc
> >> b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-0.7.inc
> >> index 7865b8f..cd62d8f 100644
> >> --- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-0.7.inc
> >> +++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-0.7.inc
> >> @@ -6,7 +6,7 @@ LICENSE = "GPLv2 | BSD"
> >> LIC_FILES_CHKSUM =
> >>
> >>
> >> "file://../COPYING;md5=c54ce9345727175ff66d17b67ff51f58 \
> >> file://../README;md5=54cfc88015d3ce83f7156e63c6bb1738 \
> >> file://wpa_supplicant.c;beginline=1;endline=17;md5=acdc5a4b0d6345f21f136eace747260e"
> >> -DEPENDS = "gnutls dbus" +DEPENDS = "gnutls dbus libnl"
> >
> > Hmm, does poky onl yhave libnl2 recipes or both libnl and libnl2?
> >
> > If the later you should depend on libnl2 instead. I'm trying to get
> > rid of these libnl mess in OE and getting all packges over to libnl2.
> > Would be great if we could share resources here. The iw package for
> > example can also be switched easily.
>
> Currently, Poky only has libnl2, and recipe name is libnl_2.0.bb, thus I added "libnl" as the wpa_supplicant's DEPENDS.
That explains it. So libnl is fine in your case. In OE we have it named
libnl2_2.0.bb to not clash with the libnl recipes.
> Something intersting that, though APIs are incompatible between libnl and libnl2, we didn't see build issues
> except this wpa_supplicant case when upgrading libnl from 1.1 to 2.0.
I would expect that Poky does not have any recipes included that only support
the old libnl version. See the list below.
> Could you list some OE packages which need libnl 1.1 as examples? We can check if we have included them in our current Poky build.
bmon
ibrdtn
lowpan-tools
networkmanager
networkmanager-openvpn
That are the ones that come in mind quickly. The first three are not in Poky
(at least as afar as I know). For the networkmanager part I would be interested
how you got it working with libnl2.
regards
Stefan Schmidt
next prev parent reply other threads:[~2011-02-14 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 9:11 [PATCH 0/2][PULL] Fix Bug 603 Dongxiao Xu
2011-02-11 9:11 ` [PATCH 1/2] wpa-supplicant: change dbus interface Dongxiao Xu
2011-02-11 10:07 ` Stefan Schmidt
2011-02-14 0:55 ` Xu, Dongxiao
2011-02-14 7:31 ` Stefan Schmidt [this message]
2011-02-14 7:34 ` Xu, Dongxiao
2011-02-14 8:07 ` Stefan Schmidt
2011-02-11 9:11 ` [PATCH 2/2] dbus: change owner and mode for dbus-daemon-launch-helper in postinst Dongxiao Xu
-- strict thread matches above, loose matches on Subject: below --
2011-02-14 7:49 [PATCH v2 0/2][PULL] Fix Bug 603 Dongxiao Xu
2011-02-14 7:49 ` [PATCH 1/2] wpa-supplicant: change dbus interface Dongxiao Xu
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=20110214073113.GA14931@excalibur.local \
--to=stefan@datenfreihafen.org \
--cc=dongxiao.xu@intel.com \
--cc=poky@yoctoproject.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