public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Bryan Hinton <bryan@bryanhinton.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] configs: Add rock5b_plus-rk3588_defconfig
Date: Tue, 4 Nov 2025 12:29:43 -0600	[thread overview]
Message-ID: <20251104182943.GF6688@bill-the-cat> (raw)
In-Reply-To: <20251104182523.2142120-2-bryan@bryanhinton.com>

[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]

On Tue, Nov 04, 2025 at 12:25:11PM -0600, Bryan Hinton wrote:
> Add initial defconfig for the Radxa ROCK 5B+ (RK3588), tested on board
> revision 1.2 with 32 GB LPDDR5. This mirrors the existing ROCK 5B baseline
> and uses the DTS from U-Boot’s vendored Linux snapshot
> (rockchip/rk3588-rock-5b-plus).
> 
> Build and test details:
>   - U-Boot build: 2026.01-rc1-00232-g0673831a738b-dirty (Nov 04 2025 - 21:18:07 -0600)
>   - Toolchain: aarch64-linux-gnu-gcc (GCC) 15.1.0
>   - DDR TPL: rkbin/bin/rk35/rk3588_ddr_lp4_2112MHz_lp5_2400MHz_v1.19.bin
>   - BL31: rkbin/bin/rk35/rk3588_bl31_v1.51.elf
>   - Boot medium: microSD card (U-Boot image written via dd)
>   - SoC: RK3588 (8× Cortex-A76/A55)
>   - DRAM: 32 GiB LPDDR5 detected
>   - eMMC socket present but module not soldered (controller still detected)
>   - Verified: SPL → U-Boot prompt
>   - `mmc list` shows SD + eMMC controllers
>   - USB EHCI/XHCI enumeration works (`usb tree`)
>   - Control FDT present (`fdt addr ${fdtcontroladdr}; fdt print / model`)
>   - Default environment: `fdtfile=rockchip/rk3588-rock-5b-plus.dtb`
> 
> This configuration reuses the ROCK 5B base defconfig with minimal adjustments
> and builds from the upstream DTS snapshot. Follow-up patches will enable
> NVMe, Ethernet, and saveenv support.
> 
> Signed-off-by: Bryan Hinton <bryan@bryanhinton.com>
> ---
>  configs/rock5b_plus-rk3588_defconfig | 118 +++++++++++++++++++++++++++
>  1 file changed, 118 insertions(+)
>  create mode 100644 configs/rock5b_plus-rk3588_defconfig

A thing we don't talk about enough is that defconfig files can use
"#include". So how much is different here from
configs/rock5b-rk3588_defconfig and could we instead do something like
configs/rpi_4_acpi_defconfig does to just augment an existing defconfig?
Next, this needs to update a MAINTAINERS file at the same time in order
for CI to pass.

[snip]
> +# Minimal first version; follow-ups can add NVMe, Ethernet, saveenv
> +# CONFIG_CMD_SAVEENV is not set
> +# CONFIG_NVME is not set

Please don't include that, and make sure this is the output from a "make
savedefconfig" so that we don't have noise in the file later when it's
resynced automatically. Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-04 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 18:25 [PATCH 0/2] Add Radxa ROCK 5B+ defconfig Bryan Hinton
2025-11-04 18:25 ` [PATCH 1/2] configs: Add rock5b_plus-rk3588_defconfig Bryan Hinton
2025-11-04 18:29   ` Tom Rini [this message]
2025-11-04 18:25 ` [PATCH 2/2] MAINTAINERS: Add entry for Radxa ROCK 5B+ Bryan Hinton
2025-11-04 19:04 ` [PATCH 0/2] Add Radxa ROCK 5B+ defconfig Jonas Karlman
2025-11-04 19:43   ` Bryan Hinton
2025-11-04 19:58     ` Jonas Karlman
2025-11-04 21:23       ` Bryan Hinton

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=20251104182943.GF6688@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bryan@bryanhinton.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