public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev <cip-dev@lists.cip-project.org>,
	isar-users <isar-users@googlegroups.com>
Cc: kas-devel <kas-devel@googlegroups.com>
Subject: Re: [isar-cip-core][WIP][PATCH] Add kconfig menu
Date: Tue, 17 Aug 2021 14:16:29 +0200	[thread overview]
Message-ID: <b6eecc00-d4bc-45ff-9418-d0f4e1e6d7d7@siemens.com> (raw)
In-Reply-To: <43993e08-b055-d2f5-012e-8ededd8485e6@siemens.com>

On 17.08.21 10:12, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Use the new kas menu plugin to present available image options to the
> user. This also allows to model their dependencies, specifically as not
> all options are supported on all boards.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Only for preview as the underlying kas feature is not yet merged. Try it 
> out by fetching kas-container from the kas next branch and then run
> 
> KAS_IMAGE_VERSION=next kas-container menu
> 
> This is the first more complex layer modeled via kconfig/kas-menu. I 
> think it nicely demonstrates the potential of this approach.
> 
>  Kconfig | 146 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 146 insertions(+)
>  create mode 100644 Kconfig
> 
> diff --git a/Kconfig b/Kconfig
> new file mode 100644
> index 0000000..72c75bf
> --- /dev/null
> +++ b/Kconfig
> @@ -0,0 +1,146 @@
> +mainmenu "Isar core layer of the Civil Infrastructure Platform project"
> +
> +config KAS_INCLUDE_MAIN
> +	string
> +	default "kas-cip.yml"
> +
> +config KAS_BUILD_SYSTEM
> +	string
> +	default "isar"
> +
> +choice
> +	prompt "Target board"
> +	default TARGET_QEMU_AMD64
> +
> +config TARGET_QEMU_AMD64
> +	bool "QEMU AMD64 (x86-64)"
> +
> +config TARGET_SIMATIC_IPC227E
> +	bool "Siemens SIMATIC IPC227E"
> +
> +config TARGET_QEMU_ARM64
> +	bool "QEMU ARM64 (aarch64)"
> +
> +config TARGET_HIHOPE_RZG2M
> +	bool "HopeRun HiHope-RZ/G2M"
> +
> +config TARGET_QEMU_ARM
> +	bool "QEMU ARM (armhf)"
> +
> +config TARGET_BBB
> +	bool "BeagleBone Black"
> +
> +config TARGET_IWG20D
> +	bool "iWave Systems RainboW-G20D-Qseven"
> +
> +endchoice
> +
> +config KAS_INCLUDE_BOARD
> +	string
> +	default "kas/board/qemu-amd64.yml" if TARGET_QEMU_AMD64
> +	default "kas/board/simatic-ipc227e.yml" if TARGET_SIMATIC_IPC227E
> +	default "kas/board/qemu-arm64.yml" if TARGET_QEMU_ARM64
> +	default "kas/board/hihope-rzg2m.yml" if TARGET_HIHOPE_RZG2M
> +	default "kas/board/qemu-arm.yml" if TARGET_QEMU_ARM
> +	default "kas/board/bbb.yml" if TARGET_BBB
> +	default "kas/board/iwg20m.yml" if TARGET_IWG20D
> +
> +comment "Kernel options"
> +
> +choice
> +	prompt "CIP kernel version"
> +	default KERNEL_4_19
> +
> +config KERNEL_4_4
> +	bool "Kernel 4.4.x-cip"
> +
> +config KERNEL_4_19
> +	bool "Kernel 4.19.x-cip"
> +
> +endchoice
> +
> +config KAS_INCLUDE_KERNEL
> +	string
> +	default "kas/opt/4.4.yml"
> +	depends on KERNEL_4_4
> +
> +config KERNEL_RT
> +	bool "Real-time CIP kernel"
> +
> +config KAS_INCLUDE_KERNEL_RT
> +	string
> +	default "kas/opt/rt.yml"
> +	depends on KERNEL_RT
> +
> +comment "Debian distribution options"
> +
> +choice
> +	prompt "Debian Release"
> +	default DEBIAN_BUSTER
> +
> +config DEBIAN_STRETCH
> +	bool "stretch (9)"
> +
> +config DEBIAN_BUSTER
> +	bool "buster (10)"
> +
> +config DEBIAN_BULLSEYE
> +	bool "bullseye (11)"
> +
> +endchoice
> +
> +config KAS_INCLUDE_DEBIAN
> +	string
> +	default "kas/opt/stretch.yml" if DEBIAN_STRETCH
> +	default "kas/opt/bullseye.yml" if DEBIAN_BULLSEYE
> +
> +comment "Image features"
> +
> +choice
> +	prompt "Image formats"
> +	default IMAGE_FLASH
> +
> +config IMAGE_FLASH
> +	bool "Flashable image"
> +
> +config IMAGE_ARTIFACTS
> +	bool "Separate artifacts for NFS boot"
> +
> +endchoice
> +
> +config KAS_INCLUDE_IMAGE_FORMAT
> +	string
> +	default "kas/opt/targz.yml" if IMAGE_ARTIFACTS && (TARGET_QEMU_AMD64 || TARGET_QEMU_ARM64 || TARGET_QEMU_ARM)
> +	default "kas/opt/wic-targz.yml" if IMAGE_ARTIFACTS && !(TARGET_QEMU_AMD64 || TARGET_QEMU_ARM64 || TARGET_QEMU_ARM)
> +
> +config IMAGE_SECURITY
> +	bool "Security extensions"
> +
> +config KAS_INCLUDE_SECURITY
> +	string
> +	default "kas/opt/security.yml" if IMAGE_SECURITY
> +
> +config IMAGE_TESTING
> +	bool "Test extensions"
> +
> +config KAS_INCLUDE_TESTING
> +	string
> +	default "kas/opt/test.yml" if IMAGE_TESTING
> +
> +if IMAGE_FLASH
> +
> +config IMAGE_SWUPDATE
> +	bool "SWUpdate support for root partition"
> +	depends on TARGET_QEMU_AMD64 || TARGET_SIMATIC_IPC227E
> +
> +config IMAGE_SECURE_BOOT
> +	bool "Secure boot support"
> +	depends on TARGET_QEMU_AMD64
> +
> +config KAS_INCLUDE_SWUPDATE_SECBOOT
> +	string
> +	default "kas/opt/ebg-swu.yml" if IMAGE_SWUPDATE && !IMAGE_SECURE_BOOT
> +	default "kas/opt/ebg-secure-boot-snakeoil.yml" if !IMAGE_SWUPDATE && IMAGE_SECURE_BOOT
> +	default "kas/opt/ebg-snakeoil-swu.yml" if IMAGE_SWUPDATE && IMAGE_SECURE_BOOT
> +
> +endif
> 

Oh, wrong primary list. Was supposed to go to cip-dev, but possibly not
uninteresting for Isar as well.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

      reply	other threads:[~2021-08-17 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  8:12 Jan Kiszka
2021-08-17 12:16 ` Jan Kiszka [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=b6eecc00-d4bc-45ff-9418-d0f4e1e6d7d7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=isar-users@googlegroups.com \
    --cc=kas-devel@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