Hi Tom, Thanks for the review.
Yes, the B650D4U currently uses the existing evb_ast2600 target as a build variant. I will move the B650D4U maintainer entry from the top-level MAINTAINERS file to board/aspeed/evb_ast2600/MAINTAINERS in the next revision. The board device tree has also been submitted to the Linux kernel as: [PATCH v3 2/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC It has not been accepted yet. I am currently addressing review feedback concerning the RGMII delay configuration, SPI flash layout, and node ordering, together with hardware validation on the board. I will keep the next U-Boot revision aligned with the corrected Linux device tree and retain only U-Boot-specific properties in the U-Boot-specific DTS include. Thanks, Prasanth On Tue, Jul 21, 2026 at 1:00 AM Tom Rini <[email protected]> wrote: > > On Sun, Jul 19, 2026 at 05:47:52PM +0530, Prasanth Kumar Padarthi wrote: > > > Add U-Boot support for the AST2600 BMC on the ASRock Rack B650D4U. > > > > Describe the 512 MiB DRAM, UART5 console, watchdog, 64 MiB SPI > > NOR, RTL8211F-connected MAC0 and RMII/NCSI-connected MAC2. > > > > Use the existing AST2600 EVB target infrastructure and a > > board-specific defconfig. > > > > Signed-off-by: Prasanth Kumar Padarthi <[email protected]> > > --- > > MAINTAINERS | 6 ++ > > arch/arm/dts/ast2600-b650d4u.dts | 74 ++++++++++++++++++++ > > configs/b650d4u_defconfig | 115 +++++++++++++++++++++++++++++++ > > 3 files changed, 195 insertions(+) > > create mode 100644 arch/arm/dts/ast2600-b650d4u.dts > > create mode 100644 configs/b650d4u_defconfig > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index d4b527560aa..52aefd17217 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -213,6 +213,12 @@ F: drivers/reset/reset-ast2500.c > > F: drivers/watchdog/ast_wdt.c > > N: aspeed > > > > +ASROCK RACK B650D4U BMC > > +M: Prasanth Kumar Padarthi <[email protected]> > > +S: Maintained > > +F: arch/arm/dts/ast2600-b650d4u.dts > > +F: configs/b650d4u_defconfig > > This should be in board/aspeed/evb_ast2600/MAINTAINERS since it's just a > build variant. And is the device tree itself being submitted upstream to > the linux kernel? Thanks! > > -- > Tom
