All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: yocto-patches@lists.yoctoproject.org,
	Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [yocto-patches] [meta-rockchip][PATCH] u-boot: Update SRCREV for radxa-zero-3
Date: Wed, 11 Dec 2024 15:07:15 -0500	[thread overview]
Message-ID: <20241211200715.GA12655@localhost> (raw)
In-Reply-To: <4e53cd8a-0607-4816-830b-ae2ed81e5875@cherry.de>

On Mon 2024-12-09 @ 04:22:47 PM, Quentin Schulz wrote:
> Hi Oleksii,
> 
> On 12/7/24 5:23 PM, Oleksii Kurochko via lists.yoctoproject.org wrote:
> > [You don't often get email from oleksii.kurochko=gmail.com@lists.yoctoproject.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > 
> > During the fetch stage of u-boot for radxa-zero-3, the following issue occurs:
> >    Unable to find revision 8cdf606e616baa36751f3b4adcfaefc781126c8c in branch
> >    rk3xxx-2024.07 even from upstream
> > 
> > This happens because the hash of the head commit for the rk3xxx-2024.07 branch
> > is different from the one specified in the recipe.
> > This can be verified by running the following command in
> > <yocto>/build/tmp/work/radxa_zero_3e-poky-linux/u-boot/2024.01/git:
> >    $ git rev-list -n 1 rk3xxx-2024.07
> >      2e2ae1fb69a25217640bfe2fb9abaf9f4fbacead
> > 
> > Update the SRCREV to the hash of the current head commit corresponding to
> > the rk3xxx-2024.07 branch.
> > 
> > Fixes: e0b13fe834b5("radxa-zero-3{e|w}: add")
> > Signed-off-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>
> > ---
> >   recipes-bsp/u-boot/u-boot_%.bbappend | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/recipes-bsp/u-boot/u-boot_%.bbappend b/recipes-bsp/u-boot/u-boot_%.bbappend
> > index c939a48..9432e2b 100644
> > --- a/recipes-bsp/u-boot/u-boot_%.bbappend
> > +++ b/recipes-bsp/u-boot/u-boot_%.bbappend
> > @@ -3,8 +3,8 @@ require u-boot-rockchip.inc
> >   FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
> > 
> >   SRC_URI:radxa-zero-3 = "git://github.com/Kwiboo/u-boot-rockchip.git;protocol=https;branch=rk3xxx-2024.07;name=Kwiboo"
> > -SRCREV:radxa-zero-3 = "8cdf606e616baa36751f3b4adcfaefc781126c8c"
> > -SRCREV:radxa-zero-3:rk-u-boot-env = "8cdf606e616baa36751f3b4adcfaefc781126c8c"
> > +SRCREV:radxa-zero-3 = "2e2ae1fb69a25217640bfe2fb9abaf9f4fbacead"
> > +SRCREV:radxa-zero-3:rk-u-boot-env = "2e2ae1fb69a25217640bfe2fb9abaf9f4fbacead"
> > 
> 
> Master poky now has v2024.10 and at a glance it seems the Zero 3E/W is
> supported, so maybe we could simply ditch those overrides for master branch
> in meta-rockchip?

Yes, and it looks like it's time to also ditch the overrides for rk-u-boot-env
as well. When I added that recipe from Jonas, he warned me at that time that
switching to upstream would be a better option, but it worked, so I left it
for the time-being.

> Other release branches should probably get a fix similar to the one in this
> patch though. Or ideally just download the patches from that tree and apply
> them on top of v2024.07 for styhead (we would need a new release branch for
> that though). Scarthgap has v2024.01 so that's a bit too old to apply
> patches destined to 2024.07. But we could maybe point to v2024.07
> upstream+patches instead of pointing to Jonas (Kwiboo)'s personal git repo.
> 
> What do you think? Trevor, an opinion here?
> 
> Cheers,
> Quentin


      parent reply	other threads:[~2024-12-11 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07 16:23 [meta-rockchip][PATCH] u-boot: Update SRCREV for radxa-zero-3 Oleksii Kurochko
2024-12-09 15:22 ` [yocto-patches] " Quentin Schulz
2024-12-10 16:16   ` Oleksii Kurochko
2024-12-10 16:37     ` Quentin Schulz
2024-12-10 19:03       ` Oleksii Kurochko
2024-12-11  9:25         ` Quentin Schulz
2024-12-12  9:21           ` Oleksii Kurochko
2024-12-11 20:07   ` Trevor Woerner [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=20241211200715.GA12655@localhost \
    --to=twoerner@gmail.com \
    --cc=oleksii.kurochko@gmail.com \
    --cc=quentin.schulz@cherry.de \
    --cc=yocto-patches@lists.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.