public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 0/4] Add DE0-Nano-SoC reference board
Date: Tue, 18 Nov 2025 07:09:00 +0100	[thread overview]
Message-ID: <cover.1763446144.git.jan.kiszka@siemens.com> (raw)

We have this target in kernel testing but we were lacking the rather
simple integration into isar-cip-core for image testing. Thanks to its
support to load also the firmware from SD card, it would have been easy
to get our EFI-based boot enabled - if upstream U-Boot didn't regress.
All addressed towards upstream and packaged with this series.

Jan

Jan Kiszka (4):
  u-boot: Add recipe for DE0-Nano-SoC
  Add DE0-Nano-SoC machine
  kas: Hook up DE0-Nano-SoC board
  ci: Add DE0-Nano-SoC board

 .gitlab-ci.yml                                |   7 +
 Kconfig                                       |   8 +-
 conf/machine/de0-nano-soc.conf                |  19 ++
 kas/board/de0-nano-soc.yml                    |  15 ++
 ...-mach-socfpga-Fix-non-Agilex-targets.patch |  97 ++++++++
 ...sector-value-passed-to-mmc_load_imag.patch |  39 +++
 ...for-SYS_MMCSD_RAW_MODE_U_BOOT_USE_PA.patch |  90 +++++++
 ...cfpga-Adjust-a-raw-sectors-for-MMC-l.patch |  44 ++++
 ...onfigs-socfpga-Fix-de0_nano_soc-boot.patch |  31 +++
 ...6-configs-socfpga-Permit-EFI-booting.patch | 229 ++++++++++++++++++
 recipes-bsp/u-boot/u-boot-common-2025.07.inc  |   6 +
 .../u-boot/u-boot-de0-nano-soc_2025.07.bb     |  26 ++
 .../plugins/source/de0-nano-soc-firmware.py   |  31 +++
 wic/de0-nano-soc-efibootguard.wks.in          |  20 ++
 wic/de0-nano-soc.wks                          |  14 ++
 15 files changed, 675 insertions(+), 1 deletion(-)
 create mode 100644 conf/machine/de0-nano-soc.conf
 create mode 100644 kas/board/de0-nano-soc.yml
 create mode 100644 recipes-bsp/u-boot/files/0001-arch-arm-mach-socfpga-Fix-non-Agilex-targets.patch
 create mode 100644 recipes-bsp/u-boot/files/0002-spl-mmc-Respect-sector-value-passed-to-mmc_load_imag.patch
 create mode 100644 recipes-bsp/u-boot/files/0003-spl-mmc-Account-for-SYS_MMCSD_RAW_MODE_U_BOOT_USE_PA.patch
 create mode 100644 recipes-bsp/u-boot/files/0004-arch-arm-mach-socfpga-Adjust-a-raw-sectors-for-MMC-l.patch
 create mode 100644 recipes-bsp/u-boot/files/0005-configs-socfpga-Fix-de0_nano_soc-boot.patch
 create mode 100644 recipes-bsp/u-boot/files/0006-configs-socfpga-Permit-EFI-booting.patch
 create mode 100644 recipes-bsp/u-boot/u-boot-de0-nano-soc_2025.07.bb
 create mode 100644 scripts/lib/wic/plugins/source/de0-nano-soc-firmware.py
 create mode 100644 wic/de0-nano-soc-efibootguard.wks.in
 create mode 100644 wic/de0-nano-soc.wks

-- 
2.51.0



             reply	other threads:[~2025-11-18  6:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  6:09 Jan Kiszka [this message]
2025-11-18  6:09 ` [isar-cip-core][PATCH 1/4] u-boot: Add recipe for DE0-Nano-SoC Jan Kiszka
2025-11-18  6:09 ` [isar-cip-core][PATCH 2/4] Add DE0-Nano-SoC machine Jan Kiszka
2025-11-18  6:09 ` [isar-cip-core][PATCH 3/4] kas: Hook up DE0-Nano-SoC board Jan Kiszka
2025-11-18  6:09 ` [isar-cip-core][PATCH 4/4] ci: Add " Jan Kiszka

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=cover.1763446144.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox