From: Christopher Larson <kergoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCHv2 0/5] Add 'iw' recipe and include in packagegroup-base
Date: Fri, 28 Aug 2015 13:22:54 -0700 [thread overview]
Message-ID: <cover.1440793291.git.chris_larson@mentor.com> (raw)
From: Christopher Larson <chris_larson@mentor.com>
iw uses cfg80211/nl80211, which is the way of the future. wireless-tools uses
WEXT, which uses ioctl, which is in deep maintenance mode. See
http://wireless.kernel.org/en/developers/Documentation/Wireless-Extensions.
Also https://wireless.wiki.kernel.org/en/users/Documentation/iw indicates "The
old tool iwconfing, which uses Wireless Extensions interface, is deprecated
and it's strongly recommended to switch to iw and nl80211."
See also the mailing list thread '[OE-core] iw in place of wireless-tools'.
v2 changes: add Upstream-Status to patch, remove duplicate
VIRTUAL-RUNTIME_wireless-tools definition.
The following changes since commit f07045fcae859c902434062d1725f1348f42d1dd:
oeqa/oetest.py: add better package search for hasPackage() (2015-08-26 08:26:37 +0100)
are available in the git repository at:
git://github.com/kergoth/openembedded-core add-iw
https://github.com/kergoth/openembedded-core/tree/add-iw
Christopher Larson (5):
iw: add recipe from meta-networking
iw: inherit pkgconfig
iw: obey our target path variables
iw: support and enable separate build dir
packagegroup-base: pull in iw as well as wireless-tools
meta/conf/distro/include/default-providers.inc | 1 +
....sh-don-t-use-git-describe-for-versioning.patch | 43 ++++++++++++++++
.../iw/iw/separate-objdir.patch | 57 ++++++++++++++++++++++
meta/recipes-connectivity/iw/iw_4.1.bb | 33 +++++++++++++
.../packagegroups/packagegroup-base.bb | 2 +-
5 files changed, 135 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-connectivity/iw/iw/0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch
create mode 100644 meta/recipes-connectivity/iw/iw/separate-objdir.patch
create mode 100644 meta/recipes-connectivity/iw/iw_4.1.bb
--
2.2.1
next reply other threads:[~2015-08-28 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 20:22 Christopher Larson [this message]
2015-08-28 20:22 ` [PATCHv2 1/5] iw: add recipe from meta-networking Christopher Larson
2015-08-28 20:23 ` [PATCHv2 2/5] iw: inherit pkgconfig Christopher Larson
2015-08-28 20:23 ` [PATCHv2 3/5] iw: obey our target path variables Christopher Larson
2015-08-28 20:23 ` [PATCHv2 4/5] iw: support and enable separate build dir Christopher Larson
2015-08-28 20:23 ` [PATCHv2 5/5] packagegroup-base: pull in iw as well as wireless-tools Christopher Larson
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.1440793291.git.chris_larson@mentor.com \
--to=kergoth@gmail.com \
--cc=chris_larson@mentor.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