- 05 Feb, 2023 1 commit
-
-
Jan Kiszka authored
-
- 01 Feb, 2023 2 commits
-
-
Updating to latest Isar will allow us to use Debian bookworm as base distribution. Bookworm ships a recent glibc which will help to enable y2038 testing in the CI environment. This is the first version of Isar with sbuild enabled, so we can't use the tricks around ${BUILDCHROOT_DIR} anymore. xenomai: The scripts/bootstrap call is already part of the upstream debian/rules file, so we do not have to call it again. linux-xenomai: Moving the rules file provided by linux-custom.inc to rules.isar allows us to ship our own rules file and override the necessary steps. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> [Jan: bump Isar a bit further for optimizations, whitespace fixups] Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Adding "rw" to the kernel cmdline for qemu based LAVA tests is a workaround for a current Isar regression. The rootfs entry is currently removed from /etc/fstab so the rootfs stayed in read-only mode. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 04 Jan, 2023 5 commits
-
-
Jan Kiszka authored
This is needed by systemd to initialize the machine ID on first boot. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
PV can be derived from the release tags, so only the latter need to be updated in the future. But make sure that SRCREV and PV remain overwritable consistently. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Document some variables that might be of interest for tuning the CI setup for different gitlab instances/ci runners. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Variables set in the gitlab UI are available as environment variables inside the build container, so no need to re-assign them in the variables block. Especially when DISTRO_APT_PREMIRRORS was not set at gitlab UI level, the variable got "$DISTRO_APT_PREMIRRORS" as value. That broke builds on our internal CI where we do not need/set this variable. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 21 Nov, 2022 1 commit
-
-
Jan Kiszka authored
Analogously to the changes in Xenomai, we need the transition to 6.x and a fix for the sorting rule. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 15 Nov, 2022 1 commit
-
-
Jan Kiszka authored
Can be helpful to work around deb.debian.org glitches, specifically when the distance of a runner to its next mirror is well known. To allow passing this to bitbake, kas has to list this variable explicitly. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 26 Sep, 2022 6 commits
-
-
Jan Kiszka authored
Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
If selected the Xenomai userspace components will be build as 32 bit (=compat) applications. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Adding compat enabled build and tests for the x86 architecture to the CI infrastructure. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Some architectures support running 32-bit legacy applications on 64-bit kernels. Xenomai supports the amd64 architectures so far. When this kas option file is selected the userspace components will be build for the compat architecture instead of the distro architecture. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
This fixes a test failure (x86io smokey test) on kernel 5.15. The necessary dovetail fixes are available since 5.15.32-dovetail2, so updating to the last available version 5.15.57-dovetail1 fixes the test. Signed-off-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Remove the acl settings as the are no longer valid. Signed-off-by:
Quirin Gylstorff <quirin.gylstorff@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 17 Jul, 2022 1 commit
-
-
Jan Kiszka authored
This is currently 5.19-dovetail. Permits to enable and test Xenomai early against newer kernels. Official support will remain focused on LTS kernels, though. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 29 Jun, 2022 3 commits
-
-
Jan Kiszka authored
The development head of Xenomai lost I-pipe support. Therefore, limit those kernels to 3.1 and 3.2 stable branches. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Private deployments may not need or may not even support the hack we carry for AWS hostings. Reported-by:
Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
This brings changes to image types that are almost easy to account for and permit to drop our downstream patch. Also the image file name changed, so adjust test jobs, readme and start-qemu.sh. There was one catch: qemu-machine.inc did not weak-assign IMAGE_FSTYPES, which is now important as opt-ci.yml must be able to overwrite it. The Isar update itself fixes logging issues, thus helps a lot with analyzing failing builds, specifically in CI. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 14 Apr, 2022 2 commits
-
-
Jan Kiszka authored
We've seen DNS issues with the AWS defaults also on the test jobs. Therefore, expand the scope of the hack to all jobs by generalizing .add-proxy-config to .common-config. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Various fixes and better control over sstate. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 12 Jan, 2022 2 commits
-
-
Jan Kiszka authored
The current workaround breaks compat-arch scenarios (32-bit xenomai packages, 64-bit kernel). Instead, we can achieve the needed tuning for cross-usage of xenomai-kernel-source by appending :native to this dependency of linux-xenomai. This is needed for arm or arm64, because dpkg request the target arch package of xenomai-kernel-source otherwise - for unknown reasons. All this is still a bit weird, but that's how dpkg sometimes is. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 10 Jan, 2022 3 commits
-
-
Jan Kiszka authored
Just requires to switch from IMAGE_TYPE to IMAGE_FSTYPES. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Limit to xenomai-next because on this version fully supports it so far. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Add a recipe and kas option for current release and extends the latest recipe to track the new branch. Default kernel becomes 5.15 for xenomai-next, therefore add rules for 3.2 to xenomai-version.inc. The Kconfig menu is updated accordingly. Limit 5.15 support to Xenomai next because not all related issues were resolved in 3.2. BeagleBone with 5.15 requires to refresh the defconfig, adding now needed CONFIG_TI_CPSW_SWITCHDEV, otherwise network remains down. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 07 Jan, 2022 7 commits
-
-
Jan Kiszka authored
Prepare for adding more dovetail kernel version and reformat the lengthy GIT_REPO and GIT_BRANCH inline-python statements. Should also improve readability. is_kernel() does not have to use startswith because we always compare exact version strings. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Open up the building & testing for stable/v3.2.x by moving current 'next' rules over. As the next Xenomai release dropped support for I-pipe kernels, drop anything but 5.10 from the related CI rules for the development head. That also avoids increasing the CI load too much. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Some were undocumented, DEPLOY_DIR_EXTENSION is now history and was actually never an external interface. Reindent the LAVA settings section at this chance. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Was obsoleted by d3a501eb . Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
That's an interface without a real use case. Dropping it makes live easier for users that want to understand the setup. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
This makes the inclusion structure more regular and reduces duplications by re-using the kernel_<version>.yml files for 3.1 and next. The trick is that we pull common variables to additional top-level 'variables:' blocks and only set what differes in the job-specific 'variables:'. BUILD_IDENTIFIER is now used in place of DEPLOY_DIR_EXTENSION, and the former is derived from the XENOMAI_VERSION and KERNEL_VERSION. Only those version variables are set at xenomai_<version>.yml and kernel- specific job level, respectively. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 05 Jan, 2022 1 commit
-
-
Jan Kiszka authored
Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 30 Nov, 2021 3 commits
-
-
Jan Kiszka authored
CI was forgotten by 7c87984c , and the new stable version provides a few minor fixes. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
Allows to use linux-xenomai.inc in downstream layers. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
Jan Kiszka authored
This allows to build the layer against i386 DISTRO_ARCH. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 29 Nov, 2021 1 commit
-
-
Jan Kiszka authored
This allows downstream layers to set KERNEL_DEFCONFIG to own files without triggering warnings like .../recipes-kernel/linux/linux-xenomai_5.4.bb: Unable to get checksum for linux-xenomai SRC_URI entry custom_defconfig: file could not be found Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 17 Nov, 2021 1 commit
-
-
Jan Kiszka authored
With kas 2.6, we can provide a kconfig-like interactive menu to select the desired image configuration. Add such a menu to model the complex dependencies properly and provide an easy way to expore available options. Also update the README accordingly. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-