From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Conor Dooley <mail@conchuod.ie>
Cc: Emil Renner Berthing <kernel@esmil.dk>,
linux-riscv@lists.infradead.org,
Ilya Sorochan <k0tran@altlinux.org>,
devicetree@vger.kernel.org, Conor Dooley <conor@kernel.org>,
E Shattow <e@freeshell.de>
Subject: Re: [PATCH] riscv: dts: starfive: jh7110-common: fix jh7110 SoC boot from SD-card.
Date: Wed, 29 Jul 2026 13:21:14 +0200 [thread overview]
Message-ID: <bb94e760-c7c3-43be-a221-5a45f8ec2db2@canonical.com> (raw)
In-Reply-To: <a32646aa-446a-4f95-9293-40001aeedae5@freeshell.de>
On 7/29/26 11:39, E Shattow wrote:
>
>
> On 7/28/26 11:02, Conor Dooley wrote:
>> From: Conor Dooley <mail@conchuod.ie>
>>
>> On Fri, 06 Mar 2026 20:19:39 +0300, Ilya Sorochan wrote:
>>> Add bootph-pre-ram to mmc1_pins clk-pins.
>>>
>>> U-Boot pruned their overrides recently in favor of Linux which broke booting
>>> from sd-card for me and Heinrich Schuchardt [1]. Pruning commit:
>>> 27f617019dd070cb61f2 ("riscv: dts: starfive: prune redundant jh7110-common overrides")
>>>
>>> [1] https://lore.kernel.org/all/ffdfc550-559b-4c59-9873-3f040fc3bb0e@canonical.com/
>>>
>>> [...]
>>
>> Right, I am going to try this again. I don't think there's actually a
>> valid technical argument against it, since it just affects the stage at
>> which configuration is applied rather than configuration itself.
>> If the configuration is wrong, and more devices don't use this configuration
>> than do, people need to move the node to where they think should be. That
>> shall be done separately.
>>
>> I don't want to hear about the politics about whether or not Starfive want
>> to support it or reverse engineering of binaries etc. All that I care about
>> is discussion of the hardware itself and which boards need this and which do
>> not.
>>
>> Applied to riscv-dt-fixes, thanks!
>>
>> [1/1] riscv: dts: starfive: jh7110-common: fix jh7110 SoC boot from SD-card.
>> https://git.kernel.org/conor/c/42c57c049054
>>
>> Thanks,
>> Conor.
>
> Second NAK to this being applied, again, do not apply as-is.
>
> As you're not interested in the technical discussion, then you won't
> have one.
>
> -E
As E does not offer any reason for their NAK, I guess it can be safely
ignored as invalid.
Best regards
Heinrich
prev parent reply other threads:[~2026-07-29 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 17:19 [PATCH] riscv: dts: starfive: jh7110-common: fix jh7110 SoC boot from SD-card Ilya Sorochan
2026-03-09 17:12 ` Conor Dooley
2026-07-28 18:02 ` Conor Dooley
2026-07-29 9:39 ` E Shattow
2026-07-29 10:59 ` Conor Dooley
2026-07-29 11:21 ` Heinrich Schuchardt [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=bb94e760-c7c3-43be-a221-5a45f8ec2db2@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=e@freeshell.de \
--cc=k0tran@altlinux.org \
--cc=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.org \
--cc=mail@conchuod.ie \
/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