From: Tom Rini <trini@konsulko.com>
To: Sune Brian <briansune@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v1] Cyclone V Board handsoff script
Date: Fri, 31 Oct 2025 09:54:27 -0600 [thread overview]
Message-ID: <20251031155427.GC6688@bill-the-cat> (raw)
In-Reply-To: <CAN7C2SDcEC+A5-rmCKMYD=vEYDFdOAfMp1G=T5SuQcXYOHDuJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On Fri, Oct 31, 2025 at 05:31:25AM +0800, Sune Brian wrote:
> > No, this is a build script that is a must and also required on every
> > clean build.
>
> Let me elaborate a bit more.
> According to the current U-Boot folder:
> board/altera/cyclone5-socdk/qts
> board/altera/arria5-socdk
> board/altera/arria10-socdk
>
> All these board folder files are not sure and high change to be stall.
> As the deconfig boards are not only official Altera board.
> As such [1] is a prerequisite to build U-Boot.
>
> So unless there are handoff changes until the EOL of 2030.
> These scripts are highly required on U-Boot, unless U-Boot
> plan to remove Altera SoCFPGA from the ARM support list.
>
> Brian
>
> [1] https://www.rocketboards.org/foswiki/Documentation/BuildingBootloaderCycloneVAndArria10#Prerequisites
That's interesting. But that also does mean that someone needs to work
better with upstream about integration here as no, that's not where that
kind of tooling should live. At bare minimum it should be in
tools/something/ and have it's own requirements.txt file too for
whatever python modules it requires.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-31 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 0:33 [PATCH v1] Cyclone V Board handsoff script Brian Sune
2025-10-30 18:09 ` Tom Rini
2025-10-30 21:21 ` Sune Brian
2025-10-30 21:31 ` Sune Brian
2025-10-31 15:54 ` Tom Rini [this message]
2025-10-31 17:30 ` Sune Brian
2025-10-31 17:46 ` Tom Rini
2025-10-31 18:03 ` Sune Brian
2025-10-31 17:35 ` Sune Brian
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=20251031155427.GC6688@bill-the-cat \
--to=trini@konsulko.com \
--cc=briansune@gmail.com \
--cc=u-boot@lists.denx.de \
/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.