From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 01/12] kas: Add initial Kconfig support
Date: Tue, 19 Sep 2023 14:04:59 +0200 [thread overview]
Message-ID: <64c75f3c-48ca-4fdb-a722-e120e93119ca@siemens.com> (raw)
In-Reply-To: <20230919115640.18398-2-ubely@ilbers.de>
On 19.09.23 13:56, Uladzimir Bely wrote:
> Create required Kconfig files and appropriate YAML configuration
> fragments for supporting initial build configuragion via
> `kas-container menu`.
>
> Since Isar does not support any possible combination of machines and
> distros, there are particular dependencies between them exist.
>
> User should select the distro first and after that it would be
> possible to choose the board this distro supports.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> .gitignore | 1 +
> Kconfig | 12 +++
> kas/distro/Kconfig | 40 ++++++++
> kas/distro/debian-bookworm.yaml | 4 +
> kas/distro/debian-bullseye.yaml | 4 +
> kas/distro/debian-buster.yaml | 4 +
> kas/distro/debian-sid-ports.yaml | 4 +
> kas/distro/raspios-bullseye.yaml | 4 +
> kas/distro/ubuntu-focal.yaml | 4 +
> kas/distro/ubuntu-jammy.yaml | 4 +
> kas/isar.yaml | 18 ++++
> kas/machine/Kconfig | 127 ++++++++++++++++++++++++++
> kas/machine/bananapi.yaml | 4 +
> kas/machine/container-amd64.yaml | 4 +
> kas/machine/de0-nano-soc.yaml | 4 +
> kas/machine/hikey.yaml | 4 +
> kas/machine/imx6-sabrelite.yaml | 4 +
> kas/machine/nanopi-neo.yaml | 4 +
> kas/machine/phyboard-mira.yaml | 4 +
> kas/machine/qemuamd64-sb.yaml | 4 +
> kas/machine/qemuamd64.yaml | 4 +
> kas/machine/qemuarm.yaml | 4 +
> kas/machine/qemuarm64.yaml | 4 +
> kas/machine/qemui386.yaml | 4 +
> kas/machine/qemumipsel.yaml | 4 +
> kas/machine/qemuriscv64.yaml | 4 +
> kas/machine/rpi-arm-v7.yaml | 4 +
> kas/machine/rpi-arm-v7l.yaml | 4 +
> kas/machine/rpi-arm.yaml | 4 +
> kas/machine/rpi-arm64-v8.yaml | 4 +
> kas/machine/sifive-fu540.yaml | 4 +
> kas/machine/starfive-visionfive2.yaml | 4 +
> kas/machine/stm32mp15x.yaml | 4 +
> kas/machine/virtualbox.yaml | 4 +
> kas/machine/vmware.yaml | 4 +
> 35 files changed, 318 insertions(+)
> create mode 100644 Kconfig
> create mode 100644 kas/distro/Kconfig
> create mode 100644 kas/distro/debian-bookworm.yaml
> create mode 100644 kas/distro/debian-bullseye.yaml
> create mode 100644 kas/distro/debian-buster.yaml
> create mode 100644 kas/distro/debian-sid-ports.yaml
> create mode 100644 kas/distro/raspios-bullseye.yaml
> create mode 100644 kas/distro/ubuntu-focal.yaml
> create mode 100644 kas/distro/ubuntu-jammy.yaml
> create mode 100644 kas/isar.yaml
> create mode 100644 kas/machine/Kconfig
> create mode 100644 kas/machine/bananapi.yaml
> create mode 100644 kas/machine/container-amd64.yaml
> create mode 100644 kas/machine/de0-nano-soc.yaml
> create mode 100644 kas/machine/hikey.yaml
> create mode 100644 kas/machine/imx6-sabrelite.yaml
> create mode 100644 kas/machine/nanopi-neo.yaml
> create mode 100644 kas/machine/phyboard-mira.yaml
> create mode 100644 kas/machine/qemuamd64-sb.yaml
> create mode 100644 kas/machine/qemuamd64.yaml
> create mode 100644 kas/machine/qemuarm.yaml
> create mode 100644 kas/machine/qemuarm64.yaml
> create mode 100644 kas/machine/qemui386.yaml
> create mode 100644 kas/machine/qemumipsel.yaml
> create mode 100644 kas/machine/qemuriscv64.yaml
> create mode 100644 kas/machine/rpi-arm-v7.yaml
> create mode 100644 kas/machine/rpi-arm-v7l.yaml
> create mode 100644 kas/machine/rpi-arm.yaml
> create mode 100644 kas/machine/rpi-arm64-v8.yaml
> create mode 100644 kas/machine/sifive-fu540.yaml
> create mode 100644 kas/machine/starfive-visionfive2.yaml
> create mode 100644 kas/machine/stm32mp15x.yaml
> create mode 100644 kas/machine/virtualbox.yaml
> create mode 100644 kas/machine/vmware.yaml
>
> diff --git a/.gitignore b/.gitignore
> index 2525d41e..c12658eb 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,3 +1,4 @@
> *~
> /*.patch
> __pycache__
> +.config.yaml
.config.yaml* (to catch also .config.yaml.old).
And we should ignore the kas workdir (build).
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2023-09-19 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 11:56 [PATCH v2 00/12] Support building Isar using kas Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 01/12] kas: Add initial Kconfig support Uladzimir Bely
2023-09-19 12:04 ` Jan Kiszka [this message]
2023-09-19 11:56 ` [PATCH v2 02/12] kas: Add a local copy of kas-container script Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 03/12] kas: Add mirror selection Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 04/12] kas: Add packages selection Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 05/12] kas: Add COMPAT_ARCH support Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 06/12] kas: Add cross compilation mode selection support Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 07/12] kas: Add ccache option Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 08/12] kas: Add image type selection Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 09/12] kas: Add IMAGE_FSTYPES selection Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 10/12] kas: Support CACHE_DEB_SRC option in menu Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 11/12] kas: Add options to activate predefined users Uladzimir Bely
2023-09-19 11:56 ` [PATCH v2 12/12] kas: Add kas/README.md Uladzimir Bely
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=64c75f3c-48ca-4fdb-a722-e120e93119ca@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.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