From: "Ilya Sorochan" <k0tran@altlinux.org>
To: "E Shattow" <e@freeshell.de>
Cc: <soc@kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
"Hal Feng" <hal.feng@starfivetech.com>,
"Conor Dooley" <conor@kernel.org>,
"Heinrich Schuchardt" <heinrich.schuchardt@canonical.com>
Subject: Re: [GIT PULL] ~RISC-V~Starfive devicetrees fixes for v7.0-rc6
Date: Mon, 30 Mar 2026 12:24:24 +0300 [thread overview]
Message-ID: <DHG0B03HM9S2.2QXKTJEGPI65B@altlinux.org> (raw)
In-Reply-To: <a77f7c9c-4357-47df-95e1-f6e0f5a7c02f@freeshell.de>
On Sat Mar 28, 2026 at 1:07 PM MSK, E Shattow wrote:
>>> I'm glad you sent a patch, but I still object for the other reasons
>>> mentioned.
>>
>> I'm glad to talk to competent people in this space, however I still hope that
>> the kernel will refrain from breaking this feature until it is really necessary.
>
> I hope you'll continue on to review the BootROM r.e. effort and cite its
> code snippets in patches so adding bootph-pre-ram hints covering the
> eMMC SPL boot method from StarFive Loader, retrospectively describing
> the SD Card SPL boot method from StarFive Loader, and/or secure boot
> crypto accelerator functionality in the starfive crypto driver (what
> does command=8 and command=9 do exactly?) The exact nature of the bug in
> StarFive Loader UART XMODEM incompatibility could use a proper
> description, and SPI Flash configuration parameter analysis, too.
Unfortunately this is beyond my competence. This exact issue was fixed without
any r.e. only using git bisect. And while it might be interesting diving into
learning how things are I'm not sure I will.
next prev parent reply other threads:[~2026-03-30 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 11:13 [GIT PULL] ~RISC-V~Starfive devicetrees fixes for v7.0-rc6 Conor Dooley
2026-03-26 14:36 ` E Shattow
2026-03-26 15:14 ` Conor Dooley
2026-03-26 15:44 ` Heinrich Schuchardt
2026-03-26 19:27 ` Ilya Sorochan
2026-03-27 4:53 ` E Shattow
2026-03-27 8:52 ` Ilya Sorochan
2026-03-28 10:07 ` E Shattow
2026-03-30 9:24 ` Ilya Sorochan [this message]
2026-03-27 8:19 ` Krzysztof Kozlowski
2026-03-27 9:45 ` Conor Dooley
2026-03-27 9:49 ` Krzysztof Kozlowski
2026-03-27 10:50 ` Krzysztof Kozlowski
2026-03-27 12:16 ` Conor Dooley
2026-03-28 4:22 ` E Shattow
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=DHG0B03HM9S2.2QXKTJEGPI65B@altlinux.org \
--to=k0tran@altlinux.org \
--cc=conor@kernel.org \
--cc=e@freeshell.de \
--cc=hal.feng@starfivetech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@kernel.org \
/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