[OE-core] [PATCH] runqemu-internal: add NIC to kernel parameters

Fixes [YOCTO #6356] Problem: If QEMU parameters are extended to emulate additional network interfaces, NFS boot does not work. Example: runqemu ... qemuparams=-net nic,model=virtio... -net tap, ... This is solved by extending the kernel parameters by ::eth0:on --- scripts/runqemu-internal | 2 +-

Re: [OE-core] runqemu + dhcp server

more work is needed, in particular around how to enable or disable this feature. Patching the .bb files also leads to a (to me) strange QA error. See the comments in the patches for details. Adrian Freihofer Gschwaderweg 29 8610 Uster 043 497 84 01 [1] http

Re: [OE-core] runqemu + dhcp server

On Friday 07 November 2014 10.12:02 Patrick Ohly wrote: Adrian Freihofer adrian.freihofer@... writes: Personally I would prefer a slightly different implementation. I consider the 192.168.7.2 network interface as development, debugging and testing interface which should just work. Agreed

Re: [OE-core] Why is systemd installed to / (was: [yocto] Export bitbake variables between recipes)

to deploy software updates to many devices. This approach could provide a generic, robust and optimized SW update procedure for embedded systems as well. Regards, Adrian Adrian Freihofer Gschwaderweg 29 8610 Uster 043 497 84 01 [1] http://0pointer.net/blog

Re: [OE-core] runqemu + dhcp server

On Tuesday 17 February 2015 11.34:14 you wrote: On Mon, 2014-11-10 at 22:57 +0100, Adrian Freihofer wrote: I haven't tried NFS rootfs. My hope is that it would still work because the ip parameter and the DHCP server assign the same IP address and thus nothing changes inside

[OE-core] Add archiver folder to SSTATE_DUPWHITELIST

Bitbake fails with an error message such as The recipe bla is trying to install files into a shared area when those files already exist. Conditions: - The archiver class is active - Bitbake is called more than once e.g. to compile two images for different architectures At least for me, the

Re: [OE-core] [master-next][PATCH] wic: Add plugin for single partition disk

Hi Ed, Thank you for the response. See my comments below. On Mon, 2015-04-20 at 21:21 +0300, Ed Bartosh wrote: Hi Adrian, Thank you for the plugin! The implementation looks good to me. See my comments below. On Mon, Apr 20, 2015 at 04:54:23PM +0200, Adrian Freihofer wrote: The wic

[OE-core] [master-next][PATCH] wic: Add plugin for single partition disk

to package based kernel updates on the device. The plugin depends on syslinux-nomtools a user space installer for syslinux on ext filesystems. Thanks to Robert Yang who implemented syslinux-nomtools and supported the implementation of this plugin. Signed-off-by: Adrian Freihofer adrian.freiho

[OE-core] [master-next][PATCHv2] wic: Add plugin for single partition disk

to package based kernel updates on the device. The plugin depends on syslinux-nomtools a user space installer for syslinux on ext filesystems. Thanks to Robert Yang who implemented syslinux-nomtools and supported the implementation of this plugin. Signed-off-by: Adrian Freihofer adrian.freiho

Re: [OE-core] [wic][PATCH] wic: Implement --build-rootfs command line option

Let wic call bitbake seems to be a great idea. One question is open to me. What's the recommended approach to resolve the dependencies between the image, the bootloader and native tools which are additionally required to create the final disk image? Basically the right place to resolve this

[OE-core] [master-next][PATCHv2] wic: Add plugin for single partition disk

at 13:10 +0300, Ed Bartosh wrote: On Mon, Apr 20, 2015 at 10:27:26PM +0200, Adrian Freihofer wrote: Hi Ed, Thank you for the response. See my comments below. On Mon, 2015-04-20 at 21:21 +0300, Ed Bartosh wrote: Hi Adrian, Thank you for the plugin! The implementation looks good

[OE-core] [master-next][PATCHv3] wic: Add plugin for single partition disk

to package based kernel updates on the device. The plugin depends on syslinux-nomtools a user space installer for syslinux on ext filesystems. Thanks to Robert Yang who implemented syslinux-nomtools and supported the implementation of this plugin. Signed-off-by: Adrian Freihofer adrian.freiho

Re: [OE-core] [PATCH] wic: remove intermediate partitions

Is there a reason to write exec_cmd(rm -f %s % rootfs) instead of using python functions such as os.remove(), os.rmdir() or shutil.rmtree()? I know, there are a lot of similar lines in the existing code... On Tuesday 28 April 2015 01.36:42 Alexandre Belloni wrote: Hi, On 28/04/2015 at

Re: [OE-core] [PATCH 1/1] syslinux: add syslinux-nomtools to PACKAGES

rootfs-pcbios-ext +# +# The first line generates a root file system including a syslinux.cfg file +# The --source rootfs-pcbios-ext in the second line triggers the ldlinux.sys +# installation into the image. +# +# AUTHOR +# Adrian Freihofer adrian.freihofer (at] gmail.com +# + +import os +from wic import

[OE-core] [PATCH 0/3] runqemu: support different net modes

-tapdevs, runqemu or a script to run a virtual reference server. This still needs to be implemented by the user. However, with the patch-set the user is enabled to do so without hacking in the poky folder. Adrian Freihofer (3): connman: fix qemu config runqemu: add support for multiple NICs

[OE-core] [PATCH 2/3] runqemu: add support for multiple NICs

, ... Signed-off-by: Adrian Freihofer adrian.freiho...@gmail.com --- scripts/runqemu-internal | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal index bc2a355..ea2badc 100755 --- a/scripts/runqemu-internal +++ b/scripts/runqemu

[OE-core] [PATCH 3/3] runqemu: support different net modes

. E.g. for testing and development of M2M/IoT applications a reference implementation of a cloud server can be connected to the bridge as well. Such a setup allows writing ptests to verify the communication between the target device and the cloud server. Signed-off-by: Adrian Freihofer adrian.freiho

[OE-core] [PATCH 1/3] connman: fix qemu config

If a network interface is configured by kernel boot parameters and the image is booted in qemu, connman takes the IP settings from /proc/cmdline for this NIC. The regex for parsing /proc/cmdline is invalid. Signed-off-by: Adrian Freihofer adrian.freiho...@gmail.com --- meta/recipes-connectivity

Re: [OE-core] [meta-oe][PATCH 0/3] runqemu improve networking

\ > > On Sun, Nov 15, 2015 at 1:01 AM, Aws Ismail <aws.ism...@gmail.com> wrote: > > Thanks Adrian for the patchset. I will test it and get back to you. > > > > Aws\ > > > > On Sat, Nov 14, 2015 at 4:35 PM, Adrian Freihofer > > <adrian.freiho...@gmail.co

[OE-core] [PATCH] libqmi: update to 1.12.6

Building ModemManager fails with previous version of libqmi. --- .../libqmi/{libqmi_1.12.2.bb => libqmi_1.12.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-oe/recipes-connectivity/libqmi/{libqmi_1.12.2.bb => libqmi_1.12.6.bb} (80%) diff --git

[OE-core] [meta-oe][PATCH 3/3] runqemu: support hostonly net mode

work setup specific for a particular use case. This might be a bridged network or what ever required. Signed-off-by: Adrian Freihofer <adrian.freiho...@gmail.com> --- scripts/runqemu | 7 ++- scripts/runqemu-gen-tapdevs | 11 +++ scripts/runqemu-

[OE-core] [meta-oe][PATCH 2/3] runqemu: add support for multiple NICs

t tap, ..." Signed-off-by: Adrian Freihofer <adrian.freiho...@gmail.com> --- scripts/runqemu-internal | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal index 3b0e54c..7b1fdd9 100755 --- a/scripts/runqemu-internal +++ b

[OE-core] [meta-oe][PATCH 1/3] connman: fix qemu config

If a network interface is configured by kernel boot parameters and the image is booted in qemu, connman takes the IP settings from /proc/cmdline for this NIC. The regex for parsing /proc/cmdline is invalid. Signed-off-by: Adrian Freihofer <adrian.freiho...@gmail.com> --- meta/r

[OE-core] [meta-oe][PATCH 0/3] runqemu improve networking

patch connman fails if the virtual device provides more than one NIC. @Aws Ismail: I'm using this since more than one year. Would be great if you could test this and provide feedback. Adrian Freihofer (3): connman: fix qemu config runqemu: add support for multiple NICs

[OE-core] [meta-oe][PATCH] python-pickle: Add rdepend python-db

Signed-off-by: Adrian Freihofer <adrian.freiho...@gmail.com> --- meta/recipes-devtools/python/python-2.7-manifest.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/python/python-2.7-manifest.inc b/meta/recipes-devtools/python/python-2.7-manife

Re: [OE-core] [PATCH V2 2/3] systemd: Upgrade 219 -> 225

Hi Andreas Here is a first patchset ready for pulling... https://github.com/openembedded/meta-openembedded/pull/16 Von: "Khem Raj" An: "Andreas Müller" CC: openembedded-de...@lists.openembedded.org, "Patches and discussions about the

Re: [OE-core] [PATCH] systemd: disable problematic GCC 5.2 optimizations

Hi Jonathan Your patch is fine on beaglebone black. At least it is possible to login. Thank you. Regards, Adrian On Mon, 2015-09-21 at 22:49 +1000, Jonathan Liu wrote: > Hi Adrian, > > On 21/09/2015 10:45 PM, Adrian Freihofer wrote: > > On Beaglebone-black Systemd 215 does not b

Re: [OE-core] [PATCH] systemd: disable problematic GCC 5.2 optimizations

Hi, On Beaglebone-black Systemd 215 does not boot if compiled with -O2. Compiling with -O1 works. Regards, Adrian 2015-09-21 14:31 GMT+02:00 Jonathan Liu : > On 21/09/2015 10:23 PM, Burton, Ross wrote: > > > On 21 September 2015 at 12:23, Jonathan Liu

Re: [OE-core] [PATCH V2 2/3] systemd: Upgrade 219 -> 225

Von: "Martin Jansa" <martin.ja...@gmail.com> An: "Adrian Freihofer" <adrian.freiho...@neratec.com> CC: "Khem Raj" <raj.k...@gmail.com>, "openembedded-devel" <openembedded-de...@lists.openembedded.org>, "Patches and discussi

Re: [OE-core] [meta-oe][PATCH 0/3] runqemu improve networking

the user is planning to use > > the VM for extended use. > > > > > > Tested-by: Aws Ismail <aws.ism...@gmail.com> > > > > > > > > On Tue, Nov 17, 2015 at 7:24 AM, Adrian Freihofer > > <adrian.freiho...@gmail.com> wrote: &g

[OE-core] [PATCH] wic: Fix and update rootfs-pcbios-ext plugin

ugin might be a good choice. +# In general a fat boot partition and a second root partition is +# recommended. +# Example wks file: +# part / --source rootfs-pcbios-ext --ondisk sda --fstype=ext4 --active --label rootfs --align 4096 --size 20 +# bootloader --source rootfs-pcbios-ext --timeout=0 --

[OE-core] [PATCH] wic: Fix and update rootfs-pcbios-ext plugin

ugin might be a good choice. +# In general a fat boot partition and a second root partition is +# recommended. +# Example wks file: +# part / --source rootfs-pcbios-ext --ondisk sda --fstype=ext4 --active --label rootfs --align 4096 --size 20 +# bootloader --source rootfs-pcbios-ext --timeout=0 --

[OE-core] [meta-oe][PATCH rebased] wic: Fix and update rootfs-pcbios-ext plugin

hoice. +# In general a fat boot partition and a second root partition is +# recommended. +# Example wks file: +# part / --source rootfs-pcbios-ext --ondisk sda --fstype=ext4 --active --label rootfs --align 4096 --size 20 +# bootloader --source rootfs-pcbios-ext --timeout=0 --append="root

Re: [OE-core] About scripts/oe-find-native-sysroot

Hi, scripts/runqemu-gen-tapdevs requires native sysroot as a command line parameter. Which folder might be passed to the script now? Regards, Adrian On Wed, 2017-03-01 at 23:53 +, Richard Purdie wrote: > On Wed, 2017-03-01 at 13:58 +0800, Robert Yang wrote: > > Hi RP, > > > > The common

[OE-core] [poky][PATCH 1/2] devtool sdk-update: Support Basic Auth

Support HTTP Basic Auth for plain HTTP downloads as well as for downloads performed by git. If the server returns a 401 error and Basic Auth is supported by the server, the user is asked for credentials. Signed-off-by: Adrian Freihofer --- scripts/lib/devtool/sdk.py | 105

[OE-core] [poky][PATCH 2/2] devtool sdk-update: --updateserver-insecure-tls

policy. * Linux development workstations are not domain members, so they don't get the company's ca.cert enrolled. * The build server has a self signed certificate Signed-off-by: Adrian Freihofer --- scripts/lib/devtool/sdk.py | 31 +-- 1 file changed, 29 insertions

[OE-core] [meta-oe][PATCH] libiio: update and improve recipe

* Update to latest version 0.14. * Make depends on avahi, libusb1 and libxml2 optional by PACKAGECONFIG or DISTRO flags. * Install iiod.service file Signed-off-by: Adrian Freihofer <adrian.freiho...@gmail.com> --- meta-oe/recipes-support/libiio/libiio_git.b

[OE-core] [PATCH] systemd: fix PN-container package splitting

From: Adrian Freihofer - Fix package splitting for services installed with systemd-container. Some files have been installed with systemd package instead of systemd-container package. (*.service, *.socket, *.html...) - Split journal-upload, journal-remote, journal-gatewayd into separate

[OE-core] Is python2 native broken in current eSDK?

Having baked an eSDK. Now I'm facing a problem with devtool and python2 native. The error occurs at least on the thud and on the master branch. Also the host distro seams not relevant. The same happens on Ubuntu 16.04, Ubuntu 18.04 and on Fedora 29 hosts. For example modifying and building

[OE-core] [meta-oe][PATCH v2 0/1] systemd: fix PN-container package splitting

= 'systemd' TEST_SUITES_append = ' systemd' command: bitbake core-image-sato -c testimage Adrian Freihofer (1): systemd: fix PN-container package splitting meta/recipes-core/systemd/systemd_239.bb | 61 1 file changed, 53 insertions(+), 8 deletions(-)

[OE-core] [meta-oe][PATCH v2 1/1] systemd: fix PN-container package splitting

are not strictly related to nspawn containers. Remote logging is now possible without installing all the container stuff. - systemd-container package rrecommends journal-upload, journal- remote, journal-gatewayd packages. Signed-off-by: Adrian Freihofer --- meta/recipes-core/systemd

[OE-core] [PATCH] devtool: fix target-deploy --strip

peError: strip_exbar() missing 1 required positional argument: 'd' Signed-off-by: Adrian Freihofer --- scripts/lib/devtool/deploy.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lib/devtool/deploy.py b/scripts/lib/devtool/deploy.py index 52e261d560..886004b5d0 10

Re: [OE-core] [meta-oe][PATCH 1/3] systemd: remove 2 obsolete useradds

On Mon, 2019-04-15 at 09:40 +0800, ChenQi wrote: > On 04/14/2019 09:24 PM, Adrian Freihofer wrote: > > - Users systemd-journal-remote and systemd-journal-upload are not > > used by > > I guess you mean 'systemd-journal-gateway'? You are right. I will send a V2 if I can convin

[OE-core] [meta-oe][PATCH v2 1/3] systemd: remove 2 obsolete useradds

- Users systemd-journal-gateway and systemd-journal-upload are not used by systemd anymore. Systemd creates dynamic users for services without persistent data. - Fix start of journal-remote Signed-off-by: Adrian Freihofer --- meta/recipes-core/systemd/systemd_241.bb | 6 +- 1 file

[OE-core] [meta-oe][PATCH 2/3] systemd: container remove rrecommend

not be installed automatically. Signed-off-by: Adrian Freihofer --- meta/recipes-core/systemd/systemd_241.bb | 6 -- 1 file changed, 6 deletions(-) diff --git a/meta/recipes-core/systemd/systemd_241.bb b/meta/recipes-core/systemd/systemd_241.bb index 8e493d5b55..688cc0608e 100644 --- a/meta/recipes

[OE-core] [meta-oe][PATCH 3/3] runqemu: support non-bootable wic images

where the bootloader as well as the devicetree is provided by Qemu. Example: QB_DEFAULT_FSTYPE = "wic-nb" QB_KERNEL_ROOT = "/dev/vda1" QB_SYSTEM_NAME = "qemu-system-aarch64" QB_MACHINE = "-machine virt" QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0&q

[OE-core] [meta-oe][PATCH 1/3] systemd: remove 2 obsolete useradds

- Users systemd-journal-remote and systemd-journal-upload are not used by systemd anymore. Systemd creates dynamic users for services without persistent data. - Fix start of journal-remote Signed-off-by: Adrian Freihofer --- meta/recipes-core/systemd/systemd_241.bb | 6 +- 1 file

[OE-core] [meta-oe][PATCH v2 4/4] runqemu: add wic-fs and wic-wm paramters

This is an optional follow up for the previous commit. It allows to define if wic images are handled as vm or as fs type images by command line argument. Signed-off-by: Adrian Freihofer --- scripts/runqemu | 6 ++ 1 file changed, 6 insertions(+) diff --git a/scripts/runqemu b/scripts

[OE-core] [meta-oe][PATCH v2 3/4] runqemu: support non-bootable wic images

this. If QB_MACHINE contains "-machine virt" and the image is of type wic a -kernel parameter is expected. Otherwise wic images are handled as before. Example: QB_DEFAULT_FSTYPE = "wic" QB_KERNEL_ROOT = "/dev/vda1" QB_SYSTEM_NAME = "qemu-system-aarch64" QB_MACHINE

[OE-core] [meta-oe][PATCH v2 1/4] qemurunner: fix undefined variable

While hacking on this I got an Exception. It's better to define variables also in python. Signe:-off-by: Adrian Freihofer --- meta/lib/oeqa/utils/qemurunner.py | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/lib/oeqa/utils/qemurunner.py b/meta/lib/oeqa/utils/qemurunner.py index

[OE-core] [meta-oe][PATCH v2 0/4] runqemu: support non-bootable wic images

) or as a fstype image (kernel in image). If QB_MACHINE contains "-machine virt" runqemu passes a "-kernel" parameter to qemu. Otherwise runqemu treats the wic image as vmtype image as before. The last patch additionally allows the user to enforce one behavior by passing wic-vm or wic-fs

[OE-core] [meta-oe][PATCH v2 2/4] testimage: consider QB_DEFAULT_FSTYPE

testimage.bbclass starts qemu with the first image type found in the IMAGE_FSTYPES list. It's weird: this ['wic', 'tar'] works but this ['tar'. 'wic'] does not. If QB_DEFAULT_FSTYPE is defined, this fstype is booted. Signed-off-by: Adrian Freihofer --- meta/classes/testimage.bbclass | 6

[OE-core] [meta-oe][PATCH v2 0/4] runqemu: support non-bootable wic images

) or as a fstype image (kernel in image). If QB_MACHINE contains "-machine virt" runqemu passes a "-kernel" parameter to qemu. Otherwise runqemu treats the wic image as vmtype image as before. The last patch additionally allows the user to enforce one behavior by passing wic-vm or wic-fs

[OE-core] [meta-oe][PATCH v2 2/4] testimage: consider QB_DEFAULT_FSTYPE

testimage.bbclass starts qemu with the first image type found in the IMAGE_FSTYPES list. It's weird: this ['wic', 'tar'] works but this ['tar'. 'wic'] does not. If QB_DEFAULT_FSTYPE is defined, this fstype is booted. Signed-off-by: Adrian Freihofer --- meta/classes/testimage.bbclass | 6

[OE-core] [meta-oe][PATCH v3 3/4] runqemu: support non-bootable wic images

this. If QB_MACHINE contains "-machine virt" and the image is of type wic a -kernel parameter is expected. Otherwise wic images are handled as before. Example: QB_DEFAULT_FSTYPE = "wic" QB_KERNEL_ROOT = "/dev/vda1" QB_SYSTEM_NAME = "qemu-system-aarch64" QB_MACHINE

[OE-core] [meta-oe][PATCH v3 0/4] runqemu: support non-bootable wic images

new e-mail address I resent them. Then this mess appeared on the mailing list. Adrian Freihofer (4): qemurunner: fix undefined variable testimage: consider QB_DEFAULT_FSTYPE runqemu: support non-bootable wic images runqemu: add wic-fs and wic-wm paramters meta/classes/testimage.bbclass|

[OE-core] [meta-oe][PATCH v3 1/4] qemurunner: fix undefined variable

While hacking on this I got an Exception. It's better to define variables also in python. Signe:-off-by: Adrian Freihofer --- meta/lib/oeqa/utils/qemurunner.py | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/lib/oeqa/utils/qemurunner.py b/meta/lib/oeqa/utils/qemurunner.py index

[OE-core] [meta-oe][PATCH v3 4/4] runqemu: add wic-fs and wic-wm paramters

This is an optional follow up for the previous commit. It allows to define if wic images are handled as vm or as fs type images by command line argument. Signed-off-by: Adrian Freihofer --- scripts/runqemu | 6 ++ 1 file changed, 6 insertions(+) diff --git a/scripts/runqemu b/scripts

[OE-core] [meta-oe][PATCH v3 2/4] testimage: consider QB_DEFAULT_FSTYPE

testimage.bbclass starts qemu with the first image type found in the IMAGE_FSTYPES list. It's weird: this ['wic', 'tar'] works but this ['tar'. 'wic'] does not. If QB_DEFAULT_FSTYPE is defined, this fstype is booted. Signed-off-by: Adrian Freihofer --- meta/classes/testimage.bbclass | 6

[OE-core] [meta-oe][PATCH v4 3/3] runqemu: QB_FSINFO to support fstype wic images

ystem-aarch64" QB_MACHINE = "-machine virt" ... [YOCTO #13336] Signed-off-by: Adrian Freihofer --- scripts/runqemu | 49 - 1 file changed, 44 insertions(+), 5 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index af9

[OE-core] [meta-oe][PATCH v4 2/3] testimage: consider QB_DEFAULT_FSTYPE

testimage.bbclass starts qemu with the first image type found in the IMAGE_FSTYPES list. It's weird: this ['wic', 'tar'] works but this ['tar'. 'wic'] does not. If QB_DEFAULT_FSTYPE is defined, this fstype is booted. Signed-off-by: Adrian Freihofer --- meta/classes/testimage.bbclass | 6

[OE-core] [meta-oe][PATCH v4 1/3] qemurunner: fix undefined variable

While hacking on this I got an Exception. It's better to define variables also in python. Signe:-off-by: Adrian Freihofer --- meta/lib/oeqa/utils/qemurunner.py | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/lib/oeqa/utils/qemurunner.py b/meta/lib/oeqa/utils/qemurunner.py index

[OE-core] [meta-oe][PATCH v4 0/3] runqemu: support non-bootable wic images

Compared to V3 this is a new implementation, as suggested by Richard. Thanks for the hint, it makes perfect sense. Adrian Freihofer (3): qemurunner: fix undefined variable testimage: consider QB_DEFAULT_FSTYPE runqemu: QB_FSINFO to support fstype wic images meta/classes/testimage.bbclass

[OE-core] [meta-oe][PATCH] yocto-bsp: runqemu runs beaglebone-yocto

eSDK would be required to support development in Qemu as well as on real hardware. Signed-off-by: Adrian Freihofer --- meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 20 +++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yoc

[OE-core] [PATCH v3] runqemu: support multiple NICs

ot process for a very long time. This change solves the timeout problem. Tested with: oe-selftest --run-tests runqemu Signed-off-by: Adrian Freihofer --- scripts/runqemu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/runqemu b/scripts/runqemu index dd0aa4b28f..

Re: [OE-core] [PATCH 0/2] Extensible SDK improvements

On Sat, 2020-03-07 at 12:40 +, Richard Purdie wrote: > On Sat, 2020-03-07 at 12:54 +0100, Adrian Freihofer wrote: > > Hi Richard, > > > > We have found two already supported ways to copy variables from the > > bitbake environment local.conf to the eSDK local.

Re: [OE-core] [PATCH 0/2] Extensible SDK improvements

Hi Richard, We have found two already supported ways to copy variables from the bitbake environment local.conf to the eSDK local.conf If a variable is defined in the local.conf bitbake environment, SDK_LOCAL_CONF_WHITELIST and SDK_LOCAL_CONF_BLACKLIST can be used to add it to the local.conf eSDK

[OE-core] [PATCH] runqemu-extract-sdk: fix install debugfs on rootfs

At least with my current setup and acc. the manual, the images are named like image-dbg.rootfs.tar.bz2. The filter has two bugs: - expects something like -dbg.tar - tar without compression suffix is not allowed Signed-off-by: Adrian Freihofer --- scripts/runqemu-extract-sdk | 2 +- 1 file

[OE-core] [PATCH] ref-manual: IMAGE_FEATURE, add allow-root-login

- Add documentation of allow-root-login - Correct the documentation of allow-empty-password Signed-off-by: Adrian Freihofer --- documentation/ref-manual/ref-features.xml | 17 ++--- documentation/ref-manual/ref-variables.xml | 8 2 files changed, 14 insertions(+), 11

[OE-core] [PATCH v4 0/1] runqemu: support multiple NICs

to QB_NETWORK_DEVICE, the corresponding kernel parameters need to be configured accordingly. Adrian Freihofer (1): runqemu: support multiple NICs meta/classes/qemuboot.bbclass | 14 ++ scripts/runqemu | 16 2 files changed, 26 insertions(+), 4 deletions

[OE-core] [PATCH v4 1/1] runqemu: support multiple NICs

From: Adrian Freihofer Emulating more than one network interface with runqemu is a bit tricky, but possible. For example, the following leads to an emulated device with eth0 and eth1: QB_NETWORK_DEVICE_prepend = " \ -device virtio-net-device,mac=52:54:00:12:

Re: [OE-core] [PATCH 0/2] Extensible SDK improvements

Hi Richard, We are going to handle that in our own layer. That's fine. Thank you for the timely clarification anyway. Regards, Adrian On Sat, 2020-03-07 at 16:20 +, Richard Purdie wrote: > On Sat, 2020-03-07 at 15:55 +0100, Adrian Freihofer wrote: > > On Sat, 2020-03-07 at 12

Re: [OE-core] [PATCH] bitbake: gitsm: download submodules

> > > > > > The unpack function failed because the submodules were not > > > > > downloaded. > > > > > Calling download before unpack for each submodule solves this > > > > > issue. > > > > > > > > > > Sign

[OE-core] [meta-oe][PATCH 2/2] oe-publish-sdk: add --keep-orig option

Support publishing the sdk-update as well as the sdk installer in one go. Signed-off-by: Adrian Freihofer --- scripts/oe-publish-sdk | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/scripts/oe-publish-sdk b/scripts/oe-publish-sdk index 19a5d69864..deb8ae1807 100755

[OE-core] [meta-oe][PATCH 1/2] oe-publish-sdk: fix layers init via ssh

Escaping does not work in my use case. It must be escaped for python, ssh and shell as well as for different versions of echo. Let's try it a little less elegant, but hopefully more reliable. Signed-off-by: Adrian Freihofer --- scripts/oe-publish-sdk | 2 +- 1 file changed, 1 insertion(+), 1

[OE-core] [meta-oe][PATCH] util-linux: Set license for pylibmount sub package

Signed-off-by: Adrian Freihofer --- meta/recipes-core/util-linux/util-linux_2.36.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/util-linux/util-linux_2.36.bb b/meta/recipes-core/util-linux/util-linux_2.36.bb index 2fac9793a2..7476e60784 100644

[OE-core] [meta-gplv2][PATCH 1/1] util-linux: remove GPLv3 and pylibmount

python bindings are GPLv3+. Signed-off-by: Adrian Freihofer --- recipes-core/util-linux/util-linux_%.bbappend | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 recipes-core/util-linux/util-linux_%.bbappend diff --git a/recipes-core/util-linux/util-linux_%.bbappend b

[OE-core] [meta-gplv2][PATCH 0/1] util-linux without python

It's not completely tested because we do not use meta-gplv2 layer. But I guess it will solve the Problem of this build pipeline: https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/2371 Adrian Freihofer (1): util-linux: remove GPLv3 and pylibmount recipes-core/util-linux/util

[OE-core] dunfell update reproducible_build.bbclass

Hi Steve We are on Dunfell LTS branch and have a small problem with reproducible builds. The problem is already solved for gatesgarth. So it would help us if the following three patches were picked to dunfell. They apply straight forward and update the reproducible_build.bbclass to paritiy with

Re: [OE-core][dunfell 02/18] ptest-runner: Fix license as it contains 'or later' clause

Hi Steve There is a nasty problem with ptest-runner 2.3.2: It prints an internal warning for each test case, which got fixed by commit: d3e9e5ebf36d1d1d7ee4bc38a64f6ec9e8fc819b "Backport patch to fix inappropriate ioctl error" You might want to consider updating ptest-runner to the latest

Re: [OE-core] [PATCH 1/3] meta-skeleton: add a ptest example

On Thu, 2021-06-03 at 22:00 +0200, Alexander Kanavin wrote: > On Thu, 3 Jun 2021 at 21:53, Adrian Freihofer < > adrian.freiho...@gmail.com> wrote: > > On Thu, 2021-06-03 at 19:46 +0200, Alexander Kanavin wrote: > > > Rather than construct an artificial example, is the

Re: [OE-core] [PATCH] overlayfs.bbclass: generate overlayfs mount units

Hi Vyacheslav It would be very nice to have such a feature in Yocto. If I remember correctly I tried to do that once with an overlay on /etc. However, that did not work with systemd. Did you ever try to add /etc as a mount point? On Thu, 2021-06-03 at 16:21 +0200, Vyacheslav Yurkov wrote: >

[OE-core] [PATCH 1/3] meta-skeleton: add a ptest example

--- .../ptest-example/files/run-ptest | 26 +++ .../ptest-example/ptest-example_0.1.bb| 16 2 files changed, 42 insertions(+) create mode 100644 meta-skeleton/recipes-skeleton/ptest-example/files/run-ptest create mode 100644

[OE-core] [PATCH 2/3] testimage: support additional reports for ptests

This adds a new optional feature to the ptest run-time test. Most unit test frameworks such as googletest generate JUnit like XML reports which can be processed e.g. by GitLab CI or Jenkins. Example: A run-ptest script executes a googletest based unit test: /usr/bin/my-unittest

[OE-core] [PATCH 3/3] runtime_test.py: add new testimage ptest test case

Product: oe-core + Author: Adrian Freihofer +""" +report_subdir = "" + +features = 'DISTRO_FEATURES_append = " ptest"\n' +features += 'IMAGE_CLASSES += "testimage"\n' +features += 'IMAGE_

[OE-core] [PATCH v2 3/3] runtime_test.py: add new testimage ptest test case

Product: oe-core + Author: Adrian Freihofer +""" +report_subdir = "" + +features = 'DISTRO_FEATURES_append = " ptest"\n' +features += 'IMAGE_CLASSES += "testimage"\n' +features += '

[OE-core] [PATCH v2 2/3] testimage: support additional reports for ptests

This adds a new optional feature to the ptest run-time test. Most unit test frameworks such as googletest generate JUnit like XML reports which can be processed e.g. by GitLab CI or Jenkins. Example: A run-ptest script executes a googletest based unit test: /usr/bin/my-unittest

[OE-core] [PATCH v2 0/3] testimage: additional reports for ptests

Changes from v1 to v2 of these patches: - Remove artificial ptest example - Update the existing service skeleton - add support for systemd - make it a ptest example Adrian Freihofer (3): meta-skeleton: update service example testimage: support additional reports for ptests

[OE-core] [PATCH v2 1/3] meta-skeleton: update service example

- Support systemd as well - Add a simple ptest --- .../service/service/run-ptest | 45 +++ .../service/service/skeleton.service | 9 .../recipes-skeleton/service/service_0.1.bb | 32 ++--- 3 files changed, 81 insertions(+), 5 deletions(-)

Re: [OE-core] [PATCH 1/3] meta-skeleton: add a ptest example

r example? Regards, Adrian > > Alex > > On Thu, 3 Jun 2021 at 19:22, Adrian Freihofer < > adrian.freiho...@gmail.com> wrote: > > --- > >  .../ptest-example/files/run-ptest             | 26 > > +++ > >  .../ptest-example/ptest-example_0.1

[OE-core] [PATCH] runqemu: support uImage kernel

u-boot's uImage kernel format is not supported by Qemu. Extract the kernel from the uImage to a temporary directory. Signed-off-by: Adrian Freihofer --- scripts/runqemu | 24 ++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts

Re: [OE-core] [PATCH] runqemu: support uImage kernel

Hi Bruce, Thank you for asking the right questions. This patch should be ignored. On Fri, 2021-04-16 at 14:06 -0400, Bruce Ashfield wrote: > On Fri, Apr 16, 2021 at 12:43 PM Adrian Freihofer > wrote: > > u-boot's uImage kernel format is not supported by Qemu. Extract the >

[OE-core] [PATCH] runqemu: support rootfs mounted ro

Optionally allow to set QB_KERNEL_ROOT to e.g. "/dev/vda ro" to mount the rootfs reay-only in Qemu. Signed-off-by: Adrian Freihofer --- meta/classes/qemuboot.bbclass | 2 ++ scripts/runqemu | 8 +++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/me

[OE-core] [PATCH] qemuboot.bbclass: do_write_qemuboot_conf after wic

-by: Adrian Freihofer --- meta/classes/qemuboot.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass index 7a5afe0c1d..12c5501a99 100644 --- a/meta/classes/qemuboot.bbclass +++ b/meta/classes/qemuboot.bbclass

[OE-core] [dunfell][PATCH] boost-native: fix build on recent host distros

deals with a build warning, it seems safe to apply it always not just for native builds. Signed-off-by: Adrian Freihofer --- meta/recipes-support/boost/boost_1.72.0.bb| 1 + ...-elide-a-warning-that-caused-Solaris.patch | 26 +++ 2 files changed, 27 insertions(+) create mode

Re: [OE-core] [dunfell][PATCH] boost-native: fix build on recent host distros

n Sun, Apr 3, 2022 at 5:14 PM Adrian Freihofer > wrote: > > The same build error as reported with Solaris occurred on a Fedora > > 35 > > machine. The problem is already fixed upstream. > > Related PR: > >  https://github.com/boostorg/thread/pull/297 > > Re

[OE-core][PATCH v5 00/14] devtool ide plugin

rtunately there was no feedback on my RFC at https://lists.openembedded.org/g/openembedded-core/message/183819 so far. - Support for more build-tools and programming languages as well as more IDEs should be possible. To prove the extendability 2 of both are already supported. Adrian Freihofer

[OE-core][PATCH v5 01/14] vscode: add minimal configuration

can have different settings depending on the details of the sources that come with the recipe. The new devtool ide plugin will generate settings to match this. Signed-off-by: Adrian Freihofer --- .gitignore| 2 ++ .vscode/settings.json | 32 2 files

[OE-core][PATCH v5 03/14] cmake.bbclass: cleanup spaces and tabs

Signed-off-by: Adrian Freihofer --- meta/classes-recipe/cmake.bbclass | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/classes-recipe/cmake.bbclass b/meta/classes-recipe/cmake.bbclass index 69d566d3154..41748b08207 100644 --- a/meta/classes-recipe/cmake.bbclass

[OE-core][PATCH v5 02/14] cmake.bbclass: refactor cmake args

Make the details of the cmake configure arguments available to d.getVar(). This allows to share them with devtool via tinfoil. Signed-off-by: Adrian Freihofer --- meta/classes-recipe/cmake.bbclass | 43 +-- 1 file changed, 24 insertions(+), 19 deletions(-) diff

  1   2   3   4   >