From: Tom Rini <trini@konsulko.com>
To: "Chee, Tien Fong" <tienfong.chee@altera.com>
Cc: Sune Brian <briansune@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH v4] Altera SoCFpga Boot Stall Fix
Date: Fri, 14 Nov 2025 11:35:35 -0600 [thread overview]
Message-ID: <20251114173535.GD6688@bill-the-cat> (raw)
In-Reply-To: <CAN7C2SBU1xozPwfRG_tdcqos4jDZRm-qzXR5MEVTG7jXebp_7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Fri, Nov 14, 2025 at 11:35:21PM +0800, Sune Brian wrote:
> > like Cyclone V, and Arria 10. Our initial assumption was that users
> > would primarily use the Altera official release repo, where we have been
> > gradually migrating platform devices to the driver model stage by stage,
> > including clk driver used in MMC driver.
>
> Tom, with all respect. I don't see those previous patches really improved
> nor introduced a proper build environment for supported SoCFPGA series.
>
> Assumption is not considered as a proper way nor correct way to patch things.
> Simply removing critical code and breaking other SoCFPGA families is completely
> unacceptable.
>
> We are not talking about code improvement nor cleanup.
> What the previous patch actually did is simply remove old generation SoCFPGA
> codes and w/o coherently coexist old and new generations.
Something like this recently happened on the i.MX side of things, and it
was fixed because once the rest of the community found out, it was made
clear breaking / removing older used devices is not allowed.
So, Tien, Altera in general, please do whatever is needed to restore
functionality to older devices that are still quite clearly being used
by both the community and your own customers. If more CI of older
targets is needed, get that going. Breaking older devices to support
newer devices is not appropriate.
>
> Brian
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-14 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 13:34 [PATCH v4] Altera SoCFpga Boot Stall Fix Brian Sune
2025-11-14 10:56 ` Chee, Tien Fong
2025-11-14 11:23 ` Sune Brian
2025-11-14 11:36 ` Chee, Tien Fong
2025-11-14 11:46 ` Sune Brian
2025-11-14 15:35 ` Sune Brian
2025-11-14 17:35 ` Tom Rini [this message]
2025-11-17 7:44 ` Chee, Tien Fong
2025-11-24 15:02 ` Jan Kiszka
2025-11-24 22:25 ` Sune Brian
2025-11-25 3:10 ` Chee, Tien Fong
2025-11-25 6:48 ` Jan Kiszka
2025-11-14 11: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=20251114173535.GD6688@bill-the-cat \
--to=trini@konsulko.com \
--cc=briansune@gmail.com \
--cc=festevam@gmail.com \
--cc=tienfong.chee@altera.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