From: Tan Siewert <tan@siewert.io>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ARM: dts: aspeed: add asrock x470d4u bmc
Date: Fri, 24 Oct 2025 22:23:45 +0200 [thread overview]
Message-ID: <5f596af8-950c-41aa-a7df-3a62339392ce@siewert.io> (raw)
In-Reply-To: <c6ee0814-1d36-45b5-8598-2a30efeee5a5@hatter.bewilderbeest.net>
On 20.10.25 11:40, Zev Weiss wrote:
> On Sat, Oct 11, 2025 at 04:21:20AM PDT, Tan Siewert wrote:
>> The ASRock Rack X470D4U X470D4U is a single-socket X470-based microATX
>> motherboard for Ryzen processors with an AST2500 BMC and either 32MB or
>> 64MB SPI flash.
>>
>> This mainboard exists in three known "flavors" which only differ in the
>> used host NIC, the BMC SPI size and some parts that may be un-populated.
>>
>> To keep the complexity low with the BMC SPI, use the 32MB layout
>> regardless of the used SPI or mainboard flavor.
*snip*
> Hmm -- I can see the simplicity argument, but it seems a bit of a shame
> to let the other 32MB go to waste on boards with 64MB chips (especially
> given how tight a fit OpenBMC is getting in 32MB these days).
Agreed.
> Could we maybe have an aspeed-bmc-asrock-x470d4u-64.dts alongside this
> one that #includes it and then drops in the 64M layout over the default
> 32? You could then arrange for a flag in the OpenBMC bitbake recipes to
> opt in to using that dts if you want to.
I implemented this idea in one of my first drafts [1], but there were
questions on the OpenBMC Discord if the additional 32MB of space are
really needed, given that the 64MB SPI is only available on an ODM
variant by default.
[1] https://gerrit.openbmc.org/c/openbmc/openbmc/+/82262/4
Cheers,
Tan
>
>
> Zev
>
prev parent reply other threads:[~2025-10-24 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 11:21 [PATCH v2 0/2] ARM: dts: aspeed: ASRock Rack X470D4U BMC support Tan Siewert
2025-10-11 11:21 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add ASRock X470D4U BMC Tan Siewert
2025-10-12 3:03 ` Krzysztof Kozlowski
2025-10-11 11:21 ` [PATCH v2 2/2] ARM: dts: aspeed: add asrock x470d4u bmc Tan Siewert
2025-10-17 5:42 ` Andrew Jeffery
2025-10-17 19:49 ` Tan Siewert
2025-10-20 9:40 ` Zev Weiss
2025-10-24 20:23 ` Tan Siewert [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=5f596af8-950c-41aa-a7df-3a62339392ce@siewert.io \
--to=tan@siewert.io \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zev@bewilderbeest.net \
/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;
as well as URLs for NNTP newsgroup(s).