From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/2] add nanopi-neo-bookworm target
Date: Wed, 20 Sep 2023 11:42:26 +0300 [thread overview]
Message-ID: <f0b6861d63d1e7c1b26bd8119e80d8c9bd7c7c84.camel@ilbers.de> (raw)
In-Reply-To: <20230914074226.3018960-2-felix.moessbauer@siemens.com>
On Thu, 2023-09-14 at 07:42 +0000, 'Felix Moessbauer' via isar-users
wrote:
> This target is based on the classical u-boot boot chain to
> allow easy use of device tree overlays.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta-isar/conf/multiconfig/nanopi-neo-bookworm.conf | 5 +++++
> testsuite/citest.py | 1 +
> 2 files changed, 6 insertions(+)
> create mode 100644 meta-isar/conf/multiconfig/nanopi-neo-
> bookworm.conf
>
> diff --git a/meta-isar/conf/multiconfig/nanopi-neo-bookworm.conf
> b/meta-isar/conf/multiconfig/nanopi-neo-bookworm.conf
> new file mode 100644
> index 00000000..e11bf37e
> --- /dev/null
> +++ b/meta-isar/conf/multiconfig/nanopi-neo-bookworm.conf
> @@ -0,0 +1,5 @@
> +# This software is a part of ISAR.
> +# Copyright (C) 2023 Siemens AG
> +
> +MACHINE ?= "nanopi-neo"
> +DISTRO ?= "debian-bookworm"
> diff --git a/testsuite/citest.py b/testsuite/citest.py
> index 48b10286..73dddaf3 100755
> --- a/testsuite/citest.py
> +++ b/testsuite/citest.py
> @@ -197,6 +197,7 @@ class NoCrossTest(CIBaseTest):
> 'mc:virtualbox-bullseye:isar-image-base',
> 'mc:bananapi-bullseye:isar-image-base',
> 'mc:nanopi-neo-bullseye:isar-image-base',
> + 'mc:nanopi-neo-bookworm:isar-image-base',
> 'mc:stm32mp15x-bullseye:isar-image-base',
> 'mc:qemuamd64-focal:isar-image-ci',
> 'mc:qemuamd64-bookworm:isar-image-ci',
> --
> 2.34.1
>
New multiconfig records should also be added to local.conf.sample,
otherwise CI fails with:
"ERROR: Multiconfig dependency mc:nanopi-neo-efi-bookworm:isar-image-
base depends on nonexistent multiconfig configuration named nanopi-neo-
efi-bookworm"
By the way, we now have different "local.conf.sample" files in both
"meta-isar" and "meta-test" layers and should think about possibility
of reusing the code in them...

next prev parent reply other threads:[~2023-09-20 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 7:42 [PATCH 0/2] add bookworm versions of nanopi-neo Felix Moessbauer
2023-09-14 7:42 ` [PATCH 1/2] add nanopi-neo-bookworm target Felix Moessbauer
2023-09-20 8:42 ` Uladzimir Bely [this message]
2023-09-14 7:42 ` [PATCH 2/2] add EFI boot version of nanopi-neo target Felix Moessbauer
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=f0b6861d63d1e7c1b26bd8119e80d8c9bd7c7c84.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
/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