From: Peter Korsgaard <peter@korsgaard.com>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
"brandon.maier@collins.com" <brandon.maier@collins.com>,
"ju.o@free.fr" <ju.o@free.fr>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"romain.naour@smile.fr" <romain.naour@smile.fr>,
"Simek, Michal" <michal.simek@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/bootgen: bump to xilinx_v2025.1
Date: Mon, 02 Jun 2025 14:12:40 +0200 [thread overview]
Message-ID: <87cybmpcjr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <SA1PR12MB56150EFB6580E77979B89CD3F062A@SA1PR12MB5615.namprd12.prod.outlook.com> (Neal Frager's message of "Mon, 2 Jun 2025 11:57:23 +0000")
>>>>> "Frager," == Frager, Neal <neal.frager@amd.com> writes:
> [AMD Official Use Only - AMD Internal Distribution Only]
> Hi Peter,
>> Bump bootgen to xilinx_v2025.1 release.
>> With version 2025.1, bootgen executable is now in the build/bin dir, so
>> the install step is changed accordingly.
>> It could be interesting to add a shortlog of the (fairly limited) amount
>> of changes done:
>> git shortlog --no-merges xilinx_v2024.2..xilinx_v2025.1
>> Shaik Salauddin (4):
>> Latest versal specific changes push to main branch for 2025.1
>> RDI version update to 2025.1
>> Adding placeholder in build directory for bootgen bin generation
>> Fix for sdcard bootup failure in zynmp/zynq
>> bsaihema (2):
>> merged and restructured code for versal_2ve_2vm and spartanus+
>> optional data fix for versal_2ve_2vm
>> Please also document why the LICENSE hash changed, E.G. LICENSE file
>> changed by a conversion from DOS to UNIX newlines by commit 86b862096bcb
>> (merged and restructured code for versal_2ve_2vm and spartanus+), no
>> content change.
> Thomas was too quick for you this time... ;)
> https://gitlab.com/buildroot.org/buildroot/-/commit/4850405d8aa2b4f7aeb84a0db7cd3369a727d214
Ahh, sorry - I missed the change on the next branch.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-06-02 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 16:40 [Buildroot] [PATCH v1 1/1] package/bootgen: bump to xilinx_v2025.1 Neal Frager via buildroot
2025-05-30 19:36 ` Thomas Petazzoni via buildroot
2025-06-02 11:47 ` Peter Korsgaard
2025-06-02 11:57 ` Frager, Neal via buildroot
2025-06-02 12:12 ` Peter Korsgaard [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=87cybmpcjr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=brandon.maier@collins.com \
--cc=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@smile.fr \
--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.