Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
	"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
	"brandon.maier@collins.com" <brandon.maier@collins.com>,
	"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>,
	"Simek, Michal" <michal.simek@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: bump to xilinx-v2024.1
Date: Thu, 6 Jun 2024 18:15:19 +0200	[thread overview]
Message-ID: <ZmHgl--jzVhjn1fA@landeda> (raw)
In-Reply-To: <CH2PR12MB5004A214F904E1B9AB3BC9EDF0FA2@CH2PR12MB5004.namprd12.prod.outlook.com>

Neal, All,

On 2024-06-06 16:02 +0000, Frager, Neal spake thusly:
> > But the filename is unversioned, which means that we can't differentiate
> > between pmufw.elf from yesterday, the one from today, and the one from
> > tomorrow.
[--SNIP--]
> By the way, is this still allowed?  Perhaps we could use it to skip the hash
> check when the u-boot.mk downloads a pre-built pmufw.elf/bin?
> 
> BR_NO_CHECK_HASH_FOR += $(UBOOT_ZYNQMP_PMUFW)

When FORCE_CHECK_HASHES=y, BR_NO_CHECK_HASH_FOR is not actioned, see
package/pkg-download@115.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-06-06 16:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 11:52 [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: bump to xilinx-v2024.1 Neal Frager via buildroot
2024-06-03 11:52 ` [Buildroot] [PATCH v1 2/3] configs/zynqmp_zcu104_defconfig: " Neal Frager via buildroot
2024-06-03 16:19   ` Luca Ceresoli via buildroot
2024-06-03 11:52 ` [Buildroot] [PATCH v1 3/3] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2024-06-03 16:19   ` Luca Ceresoli via buildroot
2024-06-03 16:19 ` [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: " Luca Ceresoli via buildroot
2024-06-03 17:32   ` Frager, Neal via buildroot
2024-06-06 13:59   ` Frager, Neal via buildroot
2024-06-06 15:25 ` Yann E. MORIN
2024-06-06 15:56   ` Frager, Neal via buildroot
2024-06-06 16:02     ` Frager, Neal via buildroot
2024-06-06 16:15       ` Yann E. MORIN [this message]
2024-06-06 18:09   ` Arnout Vandecappelle via buildroot
2024-06-06 18:34     ` [Buildroot] [External] " Maier, Brandon L Collins via buildroot
2024-06-07  6:34       ` Frager, Neal via buildroot
2024-06-11 15:08   ` [Buildroot] " Luca Ceresoli via buildroot
2024-06-11 18:06     ` Frager, Neal via buildroot

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=ZmHgl--jzVhjn1fA@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@buildroot.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox