All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Reizer, Eyal" <eyalr@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 1/4] wl18xx-fw: add recipe for version R8.7_SP3
Date: Mon, 4 Dec 2017 14:51:50 -0500	[thread overview]
Message-ID: <20171204195150.GC15340@edge> (raw)
In-Reply-To: <8665E2433BC68541A24DFFCA87B70F5B364A8553@DFRE01.ent.ti.com>

On Sun, Dec 03, 2017 at 05:34:49AM -0500, Reizer, Eyal wrote:
> Signed-off-by: Eyal Reizer <eyalr@ti.com>
> ---
>  recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb

Thanks! Can we just update from 8.7.1 to 8.7.3 by replacing the recipe, 
instead of adding new one?


> diff --git a/recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb b/recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb
> new file mode 100644
> index 0000000..a52ec89
> --- /dev/null
> +++ b/recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb
> @@ -0,0 +1,26 @@
> +DESCRIPTION = "Firmware files for use with TI wl18xx"
> +LICENSE = "TI-TSPA"
> +LIC_FILES_CHKSUM = "file://LICENCE;md5=4977a0fe767ee17765ae63c435a32a9e"
> +
> +SRC_URI = " \
> +	git://git.ti.com/wilink8-wlan/wl18xx_fw.git;protocol=git;branch=${BRANCH} \
> +	file://0001-Add-Makefile-to-install-firmware-files.patch \
> +"
> +
> +# Tag: R8.7-SP3 (8.7.3)
> +SRCREV = "f659be25473e4bde8dc790bff703ecacde6e21da"
> +BRANCH = "master"
> +
> +S = "${WORKDIR}/git"
> +
> +CLEANBROKEN = "1"
> +
> +do_compile() {
> +    :
> +}
> +
> +do_install() {
> +    oe_runmake 'DEST_DIR=${D}' install
> +}
> +
> +FILES_${PN} = "/lib/firmware/ti-connectivity/*"
> -- 
> 2.7.4
> 


  reply	other threads:[~2017-12-04 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 10:34 [PATCH 1/4] wl18xx-fw: add recipe for version R8.7_SP3 Reizer, Eyal
2017-12-04 19:51 ` Denys Dmytriyenko [this message]
2017-12-04 19:54   ` Reizer, Eyal
2017-12-04 20:14     ` Denys Dmytriyenko

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=20171204195150.GC15340@edge \
    --to=denys@ti.com \
    --cc=eyalr@ti.com \
    --cc=meta-ti@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 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.