Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: wei.tee.ng@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] recipes-connectivity: Add iw configuration for enabling Marvell 8897 WiFi feature
Date: Mon, 27 Jul 2015 15:07:45 +0100	[thread overview]
Message-ID: <1438006065.821.259.camel@linuxfoundation.org> (raw)
In-Reply-To: <1436418620-16592-3-git-send-email-wei.tee.ng@intel.com>

On Thu, 2015-07-09 at 13:10 +0800, wei.tee.ng@intel.com wrote:
> From: Ng Shui Lei <shui.lei.ng@intel.com>
> 
> iw features was created in the recipes-connectivity layer to
> enable Marvell 8897 module in AP mode and STA mode. iw is a
> new nl80211 based CLI configuration utility for wireless devices.
> 
> Signed-off-by: Ng Shui Lei <shui.lei.ng@intel.com>
> Signed-off-by: Ng Wei Tee <wei.tee.ng@intel.com>
> ---
>  ....sh-don-t-use-git-describe-for-versioning.patch |   40 ++++++++++++++++++++
>  meta/recipes-connectivity/iw/iw_3.8.bb             |   27 +++++++++++++
>  2 files changed, 67 insertions(+)
>  create mode 100644 meta/recipes-connectivity/iw/iw-3.8/0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch
>  create mode 100644 meta/recipes-connectivity/iw/iw_3.8.bb

1. How is this patch specific to the Marvell 8897 chip?
2. Did this recipe come from another layer? If so, saying where it came 
   from would be good.
3. Why do we want iw in OE-Core. I can see a case for it but you do need
   to explain that here in the commit message.
4. There are some cleanliness tweaks needed (see below).

> diff --git a/meta/recipes-connectivity/iw/iw-3.8/0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch b/meta/recipes-connectivity/iw/iw-3.8/0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch
> new file mode 100644
> index 0000000..f4a7ee7
> --- /dev/null
> +++ b/meta/recipes-connectivity/iw/iw-3.8/0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch
> @@ -0,0 +1,40 @@
> +From: Koen Kooi <koen@dominion.thruhere.net>
> +Date: Tue, 29 Nov 2011 17:03:27 +0100
> +Subject: [PATCH] iw: version.sh: don't use git describe for versioning
> +
> +It will detect top-level git repositories like the Angstrom setup-scripts and break.
> +
> +Upstream-status: Unknown

"Pending" perhaps? or "Inappropriate" looking at what the patch does.

> +Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> +---
> + version.sh | 16 +---------------
> + 1 file changed, 1 insertion(+), 15 deletions(-)
> +
> +diff --git a/version.sh b/version.sh
> +index db02f0d..336ce2b 100755
> +--- a/version.sh
> ++++ b/version.sh
> +@@ -3,21 +3,7 @@
> + VERSION="3.8"
> + OUT="$1"
> +
> +-if head=`git rev-parse --verify HEAD 2>/dev/null`; then
> +-	git update-index --refresh --unmerged > /dev/null
> +-	descr=$(git describe)
> +-
> +-	# on git builds check that the version number above
> +-	# is correct...
> +-	[ "${descr%%-*}" = "v$VERSION" ] || exit 2
> +-
> +-	v="${descr#v}"
> +-	if git diff-index --name-only HEAD | read dummy ; then
> +-		v="$v"-dirty
> +-	fi
> +-else
> +-	v="$VERSION"
> +-fi
> ++v="$VERSION"
> +
> + echo '#include "iw.h"' > "$OUT"
> + echo "const char iw_version[] = \"$v\";" >> "$OUT"
> diff --git a/meta/recipes-connectivity/iw/iw_3.8.bb b/meta/recipes-connectivity/iw/iw_3.8.bb
> new file mode 100644
> index 0000000..29dbcd0
> --- /dev/null
> +++ b/meta/recipes-connectivity/iw/iw_3.8.bb
> @@ -0,0 +1,27 @@
> +# Copyright (C) 2013 Digi International.
> +
> +SUMMARY = "nl80211 based CLI configuration utility for wireless devices"
> +DESCRIPTION = "iw is a new nl80211 based CLI configuration utility for \
> +wireless devices. It supports almost all new drivers that have been added \
> +to the kernel recently. "
> +HOMEPAGE = "http://linuxwireless.org/en/users/Documentation/iw"
> +SECTION = "base"
> +LICENSE = "BSD"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=878618a5c4af25e9b93ef0be1a93f774"
> +
> +DEPENDS = "libnl pkgconfig"
> +
> +PR = "${DISTRO}.r0"

DISTRO in PR sounds plain wrong.

> +
> +SRC_URI = "http://www.kernel.org/pub/software/network/iw/iw-${PV}.tar.bz2 \
> +           file://0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch \
> +          "
> +
> +SRC_URI[md5sum] = "618ad1106a196fb1c3d827de96da437c"
> +SRC_URI[sha256sum] = "3dae92ca5989cbc21155941fa01907a5536da3c5f6898642440c61484fc7e0f9"
> +
> +EXTRA_OEMAKE = ""
> +
> +do_install() {
> +	oe_runmake DESTDIR=${D} install
> +}
> -- 
> 1.7.9.5
> 




  reply	other threads:[~2015-07-27 14:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  5:10 [PATCH 0/2] [master][dizzy] Enable Marvel 8897 Wifi feature wei.tee.ng
2015-07-09  5:10 ` [PATCH 1/2] recipes-connectivity: Add hostapd configuration for enabling Marvell 8897 WiFi feature wei.tee.ng
2015-07-27 14:03   ` Richard Purdie
2015-07-09  5:10 ` [PATCH 2/2] recipes-connectivity: Add iw " wei.tee.ng
2015-07-27 14:07   ` Richard Purdie [this message]
2015-07-21  1:32 ` [PATCH 0/2] [master][dizzy] Enable Marvel 8897 Wifi feature Ng, Wei Tee
2015-07-27  5:21 ` Ng, Wei Tee
2015-07-27 16:41 ` Otavio Salvador
2015-07-27 18:15   ` Hugo Vasconcelos Saldanha
2015-07-27 18:28     ` Otavio Salvador
2015-07-27 18:45       ` Burton, Ross
2015-07-28  9:24         ` Ng, Wei Tee
2015-07-27 18:47       ` Hugo Vasconcelos Saldanha

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=1438006065.821.259.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wei.tee.ng@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