All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nishanth Menon" <nm@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: <praneeth@ti.com>, Yogesh Siraswar <yogeshs@ti.com>,
	Denys Dmytriyenko <denys@konsulko.com>,
	<meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][dunfell/master][PATCH 1/4] ti-sci-fw: Update imggen to release 08.00.00.001 tag
Date: Tue, 29 Jun 2021 13:48:20 -0500	[thread overview]
Message-ID: <20210629184820.vu7prcgphnj2u2k4@unshaved> (raw)
In-Reply-To: <20210629020604.GZ1528@denix.org>

On 22:06-20210628, Denys Dmytriyenko wrote:
> On Mon, Jun 28, 2021 at 07:28:14PM -0500, praneeth via lists.yoctoproject.org wrote:
> > 
> > 
> > On 6/28/2021 7:26 PM, Yogesh Siraswar wrote:
> > >Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
> > >---
> > >  recipes-bsp/ti-sci-fw/ti-sci-fw.inc | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > >diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw.inc b/recipes-bsp/ti-sci-fw/ti-sci-fw.inc
> > >index 7ec074c8..e6227632 100644
> > >--- a/recipes-bsp/ti-sci-fw/ti-sci-fw.inc
> > >+++ b/recipes-bsp/ti-sci-fw/ti-sci-fw.inc
> > >@@ -7,7 +7,7 @@ PV = "2021.01a"
> > 
> > PV is 2021.05
> 
> This is just image gen, not the actual SYSFW. Should those be updated at the 
> same time to 2021.05?
> 
> 
> > >  SRCREV = "0468c7a78cd26f9190d374e198e37c63c7660ba9"
> > >  BRANCH ?= "ti-linux-firmware"
> > >-SRCREV_imggen = "e411dc16862b5bb2d8befb12496b03d7b01c87b2"
> > >+SRCREV_imggen = "b65ae80847f5a0d1885ed6e4de4d9d635544053c"
> > >  SRCREV_FORMAT = "imggen"
> > >  SRC_URI = " \
> > >


This series of updates has completely broken Upstream am64x support. I
cant figure out (at least personally) how to make it work consistently.

https://git.ti.com/cgit/k3-image-gen/k3-image-gen/commit/?id=e411dc16862b5bb2d8befb12496b03d7b01c87b2
is the offending commit.

Unfortunately we picked that up along with moving the baseline to latest
k3-image-gen - this implies upstream is looking at SPL at older address
while we are building which puts SPL and TF-A conflicting with each
other, resulting in a completely non-bootable system when using
mainline.

I have tried various forms of patching inside meta-ti, but I am not able
to think of a sensible manner to keep mainline functional for am64x.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2021-06-29 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  0:26 [meta-ti][dunfell/master][PATCH 0/4] Release 08.00.00.001 update Yogesh Siraswar
2021-06-29  0:26 ` [meta-ti][dunfell/master][PATCH 1/4] ti-sci-fw: Update imggen to release 08.00.00.001 tag Yogesh Siraswar
2021-06-29  0:28   ` praneeth
2021-06-29  2:06     ` Denys Dmytriyenko
2021-06-29 18:48       ` Nishanth Menon [this message]
2021-06-29  0:26 ` [meta-ti][dunfell/master][PATCH 2/4] u-boot-ti-staging: Update to 08.00.00.001 release tag Yogesh Siraswar
2021-06-29  0:26 ` [meta-ti][dunfell/master][PATCH 3/4] linux-ti-staging-rt: " Yogesh Siraswar
2021-06-29  0:26 ` [meta-ti][dunfell/master][PATCH 4/4] linux-ti-staging: " Yogesh Siraswar
2021-06-29  0:29 ` [meta-ti][dunfell/master][PATCH 0/4] Release 08.00.00.001 update praneeth

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=20210629184820.vu7prcgphnj2u2k4@unshaved \
    --to=nm@ti.com \
    --cc=denis@denix.org \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=praneeth@ti.com \
    --cc=yogeshs@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.