All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yogesh Siraswar" <yogeshs@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
	Denys Dmytriyenko <denys@konsulko.com>,
	Praneeth Bajjuri <praneeth@ti.com>, Nishant Menon <nm@ti.com>,
	<meta-ti@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] [meta-ti][dunfell/master][PATCH] ti-rtos-firmware: update the source to ti-linux-firmware
Date: Fri, 16 Jul 2021 05:02:14 -0500	[thread overview]
Message-ID: <8c0c9e88-8b05-6506-5cec-f6b895635237@ti.com> (raw)
In-Reply-To: <1e859761-1cf6-25ca-47ca-5ac3e9353c6b@ti.com>



On 7/16/2021 3:04 AM, Vignesh Raghavendra wrote:
> 
> 
> On 7/16/21 2:03 AM, Yogesh Siraswar via lists.yoctoproject.org wrote:
>> This is temporary change to pick the 08.00.00.026 firmware from
>> ti-linux-firmware repos:
> 
> ti-eth is @ 08.00.00.029 -> how is that taken care of?
> 

The SRCREV for the ti-sci-fw.inc will be updated to head after tagging. 
Need to fix the PV to override from the ti-sci-fw. Will submit new patch 
revision.

TODO: Will need to split ti-eth and ti-ipc recipes so that they can have 
different versions. But that will be targeted for next release as part 
of over-all clean-up.


>> 1) Using the ti-sci-fw to pick the latest firmware and support AUTOREV
> 
> I thought we did not do AUTOREV on master branch in order for builds to
> be reproducible?
> 

AUTOREV will be only for bleeding brand. Regular build will use the 
SRCREV in ti-sci-fw.inc. This way you do not keep updating this recipe 
as long as you can use the HEAD ti-linux-firmware branch. You can always 
override in-case you want a specific version.

>> 2) Kept the destination folder name same to avoid wide-spead changes to
>> other recipes. Since that will be changed as part of over-all clean-up
>>
>> TODO:
>> 1) Re-structure rtos firmware repo and update all dependent firmware recipes.
>> 2) Fix the destination folder name to match src folder
>>
>> Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
> 
> Regards
> Vignesh
> 

      reply	other threads:[~2021-07-16 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 20:33 [meta-ti][dunfell/master][PATCH] ti-rtos-firmware: update the source to ti-linux-firmware Yogesh Siraswar
2021-07-16  8:04 ` [EXTERNAL] " Vignesh Raghavendra
2021-07-16 10:02   ` Yogesh Siraswar [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=8c0c9e88-8b05-6506-5cec-f6b895635237@ti.com \
    --to=yogeshs@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=nm@ti.com \
    --cc=praneeth@ti.com \
    --cc=vigneshr@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.