public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: daniel.bovensiepen@siemens.com, jan.kiszka@siemens.com,
	cedric.hombourger@siemens.com
Subject: Re: [PATCH v2 0/2] add bookworm versions of nanopi-neo
Date: Mon, 25 Sep 2023 08:56:08 +0300	[thread overview]
Message-ID: <c9cd63039f48144976a402231f476f78648641c9.camel@ilbers.de> (raw)
In-Reply-To: <20230921104214.1658110-1-felix.moessbauer@siemens.com>

On Thu, 2023-09-21 at 18:42 +0800, Felix Moessbauer wrote:
> This series adds two bookworm targets for the nanopi-neo board.
> The standard version uses the classical u-boot boot chain and by
> that makes it easy to use device-tree-overlays. The second patch
> adds a version using EFI boot, which makes it possible to add
> patterns like swupdate from CIP-Core. However, we split these to,
> as the support for device-tree overlays highly depends on the EFI
> booloader and support for that is not widely available.
> 
> Changes since v1:
> 
> - add multiconfig entries to local.conf.sample
> 
> Best regards,
> Felix Moessbauer
> 
> Felix Moessbauer (2):
>   add nanopi-neo-bookworm target
>   add EFI boot version of nanopi-neo target
> 
>  meta-isar/conf/local.conf.sample                  |  2 ++
>  meta-isar/conf/machine/nanopi-neo-efi.conf        | 13 +++++++++++++
>  .../conf/multiconfig/nanopi-neo-bookworm.conf     |  5 +++++
>  .../conf/multiconfig/nanopi-neo-efi-bookworm.conf |  5 +++++
>  .../lib/wic/canned-wks/nanopi-neo-efi.wks.in      | 15
> +++++++++++++++
>  testsuite/citest.py                               |  2 ++
>  6 files changed, 42 insertions(+)
>  create mode 100644 meta-isar/conf/machine/nanopi-neo-efi.conf
>  create mode 100644 meta-isar/conf/multiconfig/nanopi-neo-
> bookworm.conf
>  create mode 100644 meta-isar/conf/multiconfig/nanopi-neo-efi-
> bookworm.conf
>  create mode 100644 meta-isar/scripts/lib/wic/canned-wks/nanopi-neo-
> efi.wks.in
> 

Applied to next, thanks.

      parent reply	other threads:[~2023-09-25  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 10:42 Felix Moessbauer
2023-09-21 10:42 ` [PATCH v2 1/2] add nanopi-neo-bookworm target Felix Moessbauer
2023-09-21 10:42 ` [PATCH v2 2/2] add EFI boot version of nanopi-neo target Felix Moessbauer
2023-09-25  5:56 ` Uladzimir Bely [this message]

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=c9cd63039f48144976a402231f476f78648641c9.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=cedric.hombourger@siemens.com \
    --cc=daniel.bovensiepen@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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