From: "Chee, Tien Fong" <tienfong.chee@altera.com>
To: Sune Brian <briansune@gmail.com>
Cc: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: Re: [PATCH v7] Add optimized Makefile support for SoCFPGA handoff
Date: Fri, 21 Nov 2025 18:12:03 +0800 [thread overview]
Message-ID: <a2305233-a086-4178-a1ab-e44225577eb2@altera.com> (raw)
In-Reply-To: <CAN7C2SAOM5pVqJfQZYAZRVqBXO0aR2z6vgpndYawznSOhEqhnQ@mail.gmail.com>
Hi Brian,
On 20/11/2025 11:31 pm, Sune Brian wrote:
> [CAUTION: This email is from outside your organization. Unless you trust the sender, do not click on links or open attachments as it may be a fraudulent email attempting to steal your information and/or compromise your computer.]
>
>> Thanks for the clarification.
>>
>> Understood on the removal of Arria 10 from this flow, since its handoff mechanism is different and not based on the .hiof format.
>>
>> Noted on your point about keeping the tooling consistent. We can keep this in mind during future clean-ups.
>>
>> All good from my side. Thanks for the update.
>>
>> Tien Fong
> Hi T.F.
>
> Can try to convert to python script but don't have actual A10
> on hand. So may be a test folder with generated outputs
> to diff the new script for sanity check.
I don’t have any Arria 10 handoff samples or generated QTS output on my
side either, so I’m unable to supply a test folder for diff-checking.
If there is any reference handoff or sample output provided in the
future, we can help review or sanity-check, but for now it’s fine to
leave the A10 part as-is.
Thanks,
Tien Fong
prev parent reply other threads:[~2025-11-21 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 22:30 [PATCH v7] Add optimized Makefile support for SoCFPGA handoff Brian Sune
2025-11-18 14:05 ` Sune Brian
2025-11-19 10:54 ` Chee, Tien Fong
2025-11-19 11:13 ` Sune Brian
2025-11-19 13:08 ` Sune Brian
2025-11-20 9:17 ` Chee, Tien Fong
2025-11-20 15:31 ` Sune Brian
2025-11-21 10:12 ` Chee, Tien Fong [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=a2305233-a086-4178-a1ab-e44225577eb2@altera.com \
--to=tienfong.chee@altera.com \
--cc=briansune@gmail.com \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox