From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Alexander Smirnov <asmirnov@ilbers.de>,
Maksim Osipov <mosipov@ilbers.de>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Fwd: [jh-images][PATCH 00/24] Cross-build support, Intel NUC target, target selection menu
Date: Thu, 16 Aug 2018 19:49:36 +0200 [thread overview]
Message-ID: <aafe765c-00fc-8fc8-7e9f-3883860a4e38@siemens.com> (raw)
In-Reply-To: <cover.1534441391.git.jan.kiszka@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
FYI. jailhouse-images is now probably the largest public user of Isar: 3
architectures, 4 target images (2 virtual, 2 physical), and counting.
Thanks to the new cross-build support, things are working really
smoothly and pretty fast now.
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
[-- Attachment #2: [jh-images][PATCH 00/24] Cross-build support, Intel NUC target, target selection menu.eml --]
[-- Type: message/rfc822, Size: 13576 bytes --]
From: Jan Kiszka <jan.kiszka@siemens.com>
To: jailhouse-dev@googlegroups.com
Subject: [jh-images][PATCH 00/24] Cross-build support, Intel NUC target, target selection menu
Date: Thu, 16 Aug 2018 19:42:47 +0200
Message-ID: <cover.1534441391.git.jan.kiszka@siemens.com>
This flushes next of the jailhouse-images repo. Probably the most
important change is incorporation of the cross-build support that
upstream Isar just gained. It allows to build all (by now) 4 targets on
a quad-core i7 workstation in about 1:15h.
Futhermore, this adds support for a new target, the Intel NUC6CAY. That
is an affordable dual-core / 4-threads Atom-based mini PC. It lacks a
UART interface, though, so you need to use the EFI framebuffer or
"jailhouse console" intensively. The target is only working when using
--latest Jailhouse.
Finally, we now have a simple target image selection menu when invoking
build-images.sh. Further polishing has been done to initialize
/etc/os-release, polish the motd output, print which Jailhouse revision
is built in --latest mode, we gitlab-ci rules now, and more.
Jan
Jan Kiszka (24):
jailhouse: Print git hash when building -latest
build-images: Add image selection menu
build-images: Add --all parameter
jailhouse: Run depmod in postinst step
non-root-initramfs: Remove dependency on build-essential
linux-jailhouse: Update to 4.14.62
start-qemu: Pick latest kernel and initrd files
jailhouse: Add dh-python as build dependency
customizations: Polish motd output
Use machine-specific image names
Use machine-specific customizations package name
linux-jailhouse: Prepare for generic x86-64 defconfig
jailhouse: Prepare for generic x86-64 config
customizations: Consolidate Ethernet configurations
linux-jailhouse: Add NUC6CAY support to x86-64 config
jailhouse: Add NUC6CAY support
customizations: Add NUC6CAY support
Hook up Intel NUC6CAY support
ci: Add gitlab-ci support
Update Isar version
demo-image: Set image version and description
jailhouse: Prepare for cross-compiling the package
non-root-initramfs: Prepare for cross-compiling the package
Enable cross-compilation for all images
.gitlab-ci.yml | 19 +
build-images.sh | 51 +
conf/layer.conf | 2 +
.../multiconfig/nuc6cay-jailhouse.conf | 9 +-
images.list | 4 +
kas.yml | 6 +-
recipes-core/customizations/customizations.bb | 8 +-
.../customizations/files/.bash_history-nuc6cay | 13 +
.../files/.bash_history-orangepi-zero | 9 +-
.../customizations/files/.bash_history-qemuamd64 | 4 +-
.../customizations/files/.bash_history-qemuarm64 | 6 +-
.../customizations/files/20-jailhouse-motd | 6 +-
recipes-core/customizations/files/e1000e | 3 -
recipes-core/customizations/files/ethernet | 12 +
recipes-core/customizations/files/ivshmem-net | 6 +
recipes-core/customizations/files/postinst-common | 8 +
recipes-core/customizations/files/postinst-nuc6cay | 1 +
recipes-core/customizations/files/virtio-net | 3 -
recipes-core/images/demo-image.bb | 7 +-
.../non-root-initramfs/files/debian/control | 2 +-
recipes-jailhouse/jailhouse/files/debian/control | 2 +-
recipes-jailhouse/jailhouse/files/debian/postinst | 3 +-
recipes-jailhouse/jailhouse/files/debian/rules | 12 +
.../jailhouse/files/linux-nuc6cay-demo.c | 94 ++
recipes-jailhouse/jailhouse/files/nuc6cay.c | 1234 ++++++++++++++++++++
.../files/{qemuamd64_config.h => x86-64_config.h} | 0
recipes-jailhouse/jailhouse/jailhouse.inc | 11 +-
recipes-jailhouse/jailhouse/jailhouse_latest.bb | 11 +
recipes-kernel/linux/files/orangepi-zero_defconfig | 2 +-
recipes-kernel/linux/files/qemuarm64_defconfig | 3 +-
.../{qemuamd64_defconfig => x86-64_defconfig} | 236 +++-
recipes-kernel/linux/linux-jailhouse.bb | 17 +-
scripts/lib/wic/canned-wks/nuc6cay.wks | 5 +
start-qemu.sh | 11 +-
34 files changed, 1749 insertions(+), 71 deletions(-)
create mode 100644 .gitlab-ci.yml
copy recipes-jailhouse/jailhouse/jailhouse_latest.bb => conf/multiconfig/nuc6cay-jailhouse.conf (56%)
create mode 100644 images.list
create mode 100644 recipes-core/customizations/files/.bash_history-nuc6cay
delete mode 100644 recipes-core/customizations/files/e1000e
create mode 100644 recipes-core/customizations/files/ethernet
create mode 100644 recipes-core/customizations/files/postinst-nuc6cay
delete mode 100644 recipes-core/customizations/files/virtio-net
create mode 100644 recipes-jailhouse/jailhouse/files/linux-nuc6cay-demo.c
create mode 100644 recipes-jailhouse/jailhouse/files/nuc6cay.c
rename recipes-jailhouse/jailhouse/files/{qemuamd64_config.h => x86-64_config.h} (100%)
rename recipes-kernel/linux/files/{qemuamd64_defconfig => x86-64_defconfig} (94%)
create mode 100644 scripts/lib/wic/canned-wks/nuc6cay.wks
--
2.16.4
parent reply other threads:[~2018-08-16 17:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <cover.1534441391.git.jan.kiszka@siemens.com>]
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=aafe765c-00fc-8fc8-7e9f-3883860a4e38@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=mosipov@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