All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jamie Gibbons via buildroot <buildroot@buildroot.org>
Cc: Valentina Fernandez Alanis
	<Valentina.FernandezAlanis@microchip.com>,
	Jamie Gibbons <jamie.gibbons@microchip.com>,
	Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
Subject: Re: [Buildroot] [PATCH 1/1] fix: board/beagleboard/beaglev_fire: update uboot hash
Date: Thu, 8 Aug 2024 00:11:48 +0200	[thread overview]
Message-ID: <20240808001148.06b90125@windsurf> (raw)
In-Reply-To: <20240807143605.1440039-1-jamie.gibbons@microchip.com>

Hello Jamie,

On Wed, 7 Aug 2024 15:36:05 +0100
Jamie Gibbons via buildroot <buildroot@buildroot.org> wrote:

> The U-Boot hash is incorrect and breaks the BeagleV Fire build. Update
> the U-Boot hash.
> 
> Fixes:8ce97fd550d6("configs/beaglev_fire: bump Linux and U-Boot")
> 
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
> Tested-by: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>

Thanks, but there is something more wrong... which probably explains
the hash issue:

BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,linux4microchip,u-boot-mchp,u-boot-2023.07-mchp)/linux4microchip+fpga-2024.06.tar.gz"

So we are retrieving U-Boot 2023.07-mchp, and storing it into a tarball
called linux4microchip+fpga-2024.06.tar.gz, meh. Seems like I didn't
review carefully enough that version bump.

Could you check this, and send a patch that really bumps U-Boot (and
fixes the hash) ?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-08-07 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 14:36 [Buildroot] [PATCH 1/1] fix: board/beagleboard/beaglev_fire: update uboot hash Jamie Gibbons via buildroot
2024-08-07 22:11 ` Thomas Petazzoni via buildroot [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=20240808001148.06b90125@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Valentina.FernandezAlanis@microchip.com \
    --cc=jamie.gibbons@microchip.com \
    --cc=prajna.rajendrakumar@microchip.com \
    --cc=thomas.petazzoni@bootlin.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.