From: "Nishanth Menon" <nm@ti.com>
To: Denys Dmytriyenko <denis@denix.org>,
Saurabh Narang <saurabhnarang@ti.com>
Cc: <nikhil.nd@ti.com>, <meta-ti@yoctoproject.org>, <praneeth@ti.com>,
<lokeshvutla@ti.com>, <kishon@ti.com>, <nsekhar@ti.com>,
<hnagalla@ti.com>, <saurabhnarang@ti.com>
Subject: Re: [meta-ti][dunfell PATCH v2] recipes-bsp: wl18xx-fw: update SRCREV to latest
Date: Tue, 16 Mar 2021 13:29:36 -0500 [thread overview]
Message-ID: <20210316182936.r4xmdxps6mz7meyt@parched> (raw)
In-Reply-To: <20210312231143.GE4892@denix.org>
On 18:11-20210312, Denys Dmytriyenko wrote:
> On Wed, Mar 10, 2021 at 11:22:22AM -0600, Nishanth Menon wrote:
> > On 12:11-20210310, Denys Dmytriyenko wrote:
> > > On Wed, Mar 10, 2021 at 09:43:37PM +0530, Nikhil Devshatwar via lists.yoctoproject.org wrote:
> > > > Update the wl18xx firmware recipe to latest version 8.9.0.0.86
> > > >
> > > > Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
> > >
> > > Reviewed-by: Denys Dmytriyenko <denis@denix.org>
> > >
> > >
> > > > ---
> > > >
> > > > Notes:
> > > > Changes from v1:
> > > > * Update the version in the recipe filename
> > > >
> > > > .../wl18xx-fw/{wl18xx-fw_8.7.3.bb => wl18xx-fw_8.9.0.0.86.bb} | 3 +--
> > > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > > > rename recipes-bsp/wl18xx-fw/{wl18xx-fw_8.7.3.bb => wl18xx-fw_8.9.0.0.86.bb} (86%)
> > > >
> > > > diff --git a/recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb b/recipes-bsp/wl18xx-fw/wl18xx-fw_8.9.0.0.86.bb
> > > > similarity index 86%
> > > > rename from recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb
> > > > rename to recipes-bsp/wl18xx-fw/wl18xx-fw_8.9.0.0.86.bb
> > > > index a52ec898..50b6c297 100644
> > > > --- a/recipes-bsp/wl18xx-fw/wl18xx-fw_8.7.3.bb
> > > > +++ b/recipes-bsp/wl18xx-fw/wl18xx-fw_8.9.0.0.86.bb
> > > > @@ -7,8 +7,7 @@ SRC_URI = " \
> > > > file://0001-Add-Makefile-to-install-firmware-files.patch \
> > > > "
> >
> > Just curious, is there a periodic upgrade plan in upstream [1] - last commit is
> > [2] ?
>
> Based on [3], I believe this is a question for Saurabh Narang <saurabhnarang@ti.com>
> And would also like to hear the answer...
Saurabh,
any suggestions?
>
>
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/ti-connectivity/wl18xx-fw-4.bin?id=d5f9eea5a251d43412b07f5295d03e97b89ac4a5
>
> [3] https://git.ti.com/cgit/wilink8-wlan/wl18xx_fw/log/
>
> --
> Regards,
> Denys Dmytriyenko <denis@denix.org>
> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
> Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2021-03-16 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 16:13 [meta-ti][dunfell PATCH v2] recipes-bsp: wl18xx-fw: update SRCREV to latest Nikhil Devshatwar
2021-03-10 17:11 ` Denys Dmytriyenko
2021-03-10 17:22 ` Nishanth Menon
2021-03-12 23:11 ` Denys Dmytriyenko
2021-03-16 18:29 ` Nishanth Menon [this message]
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=20210316182936.r4xmdxps6mz7meyt@parched \
--to=nm@ti.com \
--cc=denis@denix.org \
--cc=hnagalla@ti.com \
--cc=kishon@ti.com \
--cc=lokeshvutla@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=nikhil.nd@ti.com \
--cc=nsekhar@ti.com \
--cc=praneeth@ti.com \
--cc=saurabhnarang@ti.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 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.