From: Bin Meng <bin.meng@processmission.com>
To: QEMU <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-arm@nongnu.org
Subject: [PATCH v2 23/32] hw/arm: phytium: Support Phytium E2000 direct Linux boot
Date: Tue, 8 Sep 2026 18:41:32 +0800 [thread overview]
Message-ID: <20260908104159.1621764-24-bin.meng@processmission.com> (raw)
In-Reply-To: <20260908104159.1621764-1-bin.meng@processmission.com>
Allow the Phytium Pi machine to boot a Linux Image directly through
the generic Arm loader. Require the matching SDK phytiumpi_firefly.dtb
whenever -kernel is used.
Signed-off-by: Bin Meng <bin.meng@processmission.com>
---
Changes in v2:
- Pass the SoC-owned primary ARMCPU to the boot loader
hw/arm/phytium_e2000_machine.c | 65 ++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
diff --git a/hw/arm/phytium_e2000_machine.c b/hw/arm/phytium_e2000_machine.c
index 0337795f2d..41bce8a64b 100644
--- a/hw/arm/phytium_e2000_machine.c
+++ b/hw/arm/phytium_e2000_machine.c
@@ -15,6 +15,7 @@
#include "qapi/error.h"
#include "system/address-spaces.h"
#include "system/block-backend-global-state.h"
+#include "system/device_tree.h"
#include "system/kvm.h"
#include "exec/hwaddr.h"
#include "hw/arm/boot.h"
@@ -44,6 +45,7 @@ struct PhytiumE2000MachineClass {
MachineClass parent_class;
const char *machine_name;
+ const char *direct_boot_dtb;
const char *pbr_boot_mode;
};
@@ -105,6 +107,61 @@ static void phytium_e2000_create_ram(PhytiumE2000MachineState *s)
phytium_e2000_memmap[PHYTIUM_E2000_RAM_HIGH].base, &s->ram_high);
}
+static void phytium_e2000_add_memory_node(void *fdt, hwaddr base,
+ uint64_t size)
+{
+ uint32_t acells;
+ uint32_t scells;
+ g_autofree char *name = g_strdup_printf("/memory@%" HWADDR_PRIx, base);
+
+ acells = qemu_fdt_getprop_cell(fdt, "/", "#address-cells",
+ NULL, &error_fatal);
+ scells = qemu_fdt_getprop_cell(fdt, "/", "#size-cells",
+ NULL, &error_fatal);
+
+ qemu_fdt_add_subnode(fdt, name);
+ qemu_fdt_setprop_string(fdt, name, "device_type", "memory");
+ qemu_fdt_setprop_sized_cells(fdt, name, "reg",
+ acells, base, scells, size);
+}
+
+static void phytium_e2000_modify_dtb(const struct arm_boot_info *info,
+ void *fdt)
+{
+ uint64_t low_size =
+ MIN(info->ram_size, phytium_e2000_memmap[PHYTIUM_E2000_RAM].size);
+ uint64_t high_size = info->ram_size - low_size;
+ g_auto(GStrv) memory_nodes = NULL;
+ Error *err = NULL;
+ int i;
+
+ if (!high_size) {
+ return;
+ }
+
+ /*
+ * arm_load_dtb() normally describes RAM as one range beginning at
+ * loader_start. E2000 RAM above 2 GiB is instead mapped at 0x2000000000,
+ * beyond the PCIe aperture. Replace the generic range so Linux never
+ * treats the intervening address-space hole as RAM.
+ */
+ memory_nodes = qemu_fdt_node_unit_path(fdt, "memory", &err);
+ if (err) {
+ error_report_err(err);
+ exit(1);
+ }
+ for (i = 0; memory_nodes[i]; i++) {
+ if (g_str_has_prefix(memory_nodes[i], "/memory")) {
+ qemu_fdt_nop_node(fdt, memory_nodes[i]);
+ }
+ }
+
+ phytium_e2000_add_memory_node(
+ fdt, phytium_e2000_memmap[PHYTIUM_E2000_RAM].base, low_size);
+ phytium_e2000_add_memory_node(
+ fdt, phytium_e2000_memmap[PHYTIUM_E2000_RAM_HIGH].base, high_size);
+}
+
static void phytium_e2000_init(MachineState *ms)
{
PhytiumE2000MachineState *s = PHYTIUM_E2000_MACHINE(ms);
@@ -123,6 +180,12 @@ static void phytium_e2000_init(MachineState *ms)
exit(1);
}
+ if (ms->kernel_filename && !ms->dtb) {
+ error_report("%s: direct Linux boot requires the SDK %s via -dtb",
+ pemc->machine_name, pemc->direct_boot_dtb);
+ exit(1);
+ }
+
if (ms->smp.cpus > PHYTIUM_E2000_NUM_CPUS) {
error_report("%s supports at most %d CPUs", pemc->machine_name,
PHYTIUM_E2000_NUM_CPUS);
@@ -159,6 +222,7 @@ static void phytium_e2000_init(MachineState *ms)
phytium_e2000_memmap[PHYTIUM_E2000_RAM].base;
s->bootinfo.psci_conduit = QEMU_PSCI_CONDUIT_SMC;
s->bootinfo.firmware_loaded = firmware_loaded;
+ s->bootinfo.modify_dtb = phytium_e2000_modify_dtb;
arm_load_kernel(phytium_e2000_soc_cpu(&s->soc, 0), ms, &s->bootinfo);
}
@@ -224,6 +288,7 @@ static void phytium_pi_class_init(ObjectClass *oc, const void *data)
mc->desc = "Phytium Pi board (Phytium E2000Q)";
mc->block_default_type = IF_SD;
pemc->machine_name = "phytium-pi";
+ pemc->direct_boot_dtb = "phytiumpi_firefly.dtb";
pemc->pbr_boot_mode = PHYTIUM_E2000_PBR_BOOT_MODE_SD0;
}
--
2.53.0
next prev parent reply other threads:[~2026-09-08 10:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 10:41 [PATCH v2 00/32] hw/arm: Add Phytium E2000Q SoC and board support Bin Meng
2026-09-08 10:41 ` [PATCH v2 01/32] hw/arm: Add Phytium E2000 SoC and Phytium Pi machine Bin Meng
2026-09-08 10:41 ` [PATCH v2 02/32] hw/arm: phytium: Add Phytium E2000 PCIe host Bin Meng
2026-09-08 10:41 ` [PATCH v2 03/32] hw/sd: Add Synopsys DesignWare MCI controller Bin Meng
2026-09-08 10:41 ` [PATCH v2 04/32] hw/sd: Add Phytium E2000 " Bin Meng
2026-09-08 10:41 ` [PATCH v2 05/32] hw/arm: phytium: Connect Phytium E2000 MCI controllers Bin Meng
2026-09-08 10:41 ` [PATCH v2 06/32] tests/qtest: Add Synopsys DesignWare MCI coverage Bin Meng
2026-09-08 10:41 ` [PATCH v2 07/32] hw/arm: phytium: Connect Phytium E2000 GEM controllers Bin Meng
2026-09-08 10:41 ` [PATCH v2 08/32] hw/misc: Add Phytium E2000 DDR controller Bin Meng
2026-09-08 10:41 ` [PATCH v2 09/32] hw/arm: phytium: Connect the " Bin Meng
2026-09-08 10:41 ` [PATCH v2 10/32] hw/misc: Add Phytium E2000 MHU doorbell Bin Meng
2026-09-08 10:41 ` [PATCH v2 11/32] hw/arm: phytium: Connect the Phytium E2000 MHU Bin Meng
2026-09-08 10:41 ` [PATCH v2 12/32] hw/ssi: Add Phytium E2000 QSPI controller Bin Meng
2026-09-08 10:41 ` [PATCH v2 13/32] hw/arm: phytium: Connect the " Bin Meng
2026-09-08 10:41 ` [PATCH v2 14/32] hw/misc: Add Phytium E2000 PBR model Bin Meng
2026-09-08 10:41 ` [PATCH v2 15/32] hw/arm: phytium: Integrate the Phytium E2000 PBR Bin Meng
2026-09-08 10:41 ` [PATCH v2 16/32] hw/arm: phytium: Add Phytium E2000 control region placeholders Bin Meng
2026-09-08 10:41 ` [PATCH v2 17/32] hw/misc: Support Phytium E2000 SCMI CPU power control Bin Meng
2026-09-08 10:41 ` [PATCH v2 18/32] hw/arm: phytium: Select the Phytium E2000 PBR boot medium Bin Meng
2026-09-08 10:41 ` [PATCH v2 19/32] hw/arm: phytium: Connect the Phytium E2000 I2C controller Bin Meng
2026-09-08 10:41 ` [PATCH v2 20/32] hw/arm: phytium: Add Phytium E2000 xHCI controllers Bin Meng
2026-09-08 10:41 ` [PATCH v2 21/32] hw/misc: Model the Phytium E2000 random generator Bin Meng
2026-09-08 10:41 ` [PATCH v2 22/32] hw/arm: phytium: Connect " Bin Meng
2026-09-08 10:41 ` Bin Meng [this message]
2026-09-08 10:41 ` [PATCH v2 24/32] hw/arm: phytium: Add Phytium E2000Q COMe machine Bin Meng
2026-09-08 10:41 ` [PATCH v2 25/32] hw/block: m25p80: Add GigaDevice GD25Q128 flash Bin Meng
2026-09-08 10:41 ` [PATCH v2 26/32] hw/arm: phytium: Connect the Phytium E2000Q COMe QSPI flash Bin Meng
2026-09-08 10:41 ` [PATCH v2 27/32] hw/arm: phytium: Add Phytium E2000 AHCI controllers Bin Meng
2026-09-08 10:41 ` [PATCH v2 28/32] hw/arm: Add Phytium E2000 Linux SCMI channel Bin Meng
2026-09-08 10:41 ` [PATCH v2 29/32] hw/arm: phytium: Connect the Phytium E2000 SMMUv3 Bin Meng
2026-09-08 10:41 ` [PATCH v2 30/32] docs/system/arm: Document Phytium E2000 machines Bin Meng
2026-09-08 10:41 ` [PATCH v2 31/32] tests/functional/aarch64: Add Phytium Pi boot tests Bin Meng
2026-09-08 10:41 ` [PATCH v2 32/32] MAINTAINERS: Add Phytium E2000Q machines Bin Meng
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=20260908104159.1621764-24-bin.meng@processmission.com \
--to=bin.meng@processmission.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.