Still broken :( -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com

Hello, Some more details would be needed (ie. you have systemd?), but this could be a good point to start: https://wiki.archlinux.org/title/Systemd-resolved (ie. see a bit down, like:

Hi, I assume it shouldn't be empty resov. conf. Manually I am updating nameserver always. but when I reboot my machine it's empty. So for this, I want to make permanent my nameserver always. I

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit adds 382 autogenerated machines generated via generate-zephyr-machines.bb. These machines have obviously not all been tested

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit just adds some documentation on how to use the machine generation recipe. Signed-off-by: Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> Some of these recipes ended up overriding the ZEPHYR_MODULES we set elsewhere. As well, zephyr-lvgl tries to apply a patch we already

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> Trying to handwrite all the machine defintions in zephyr would be an enormous task. This commit creates a patch to zephy which abuses

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> fd8bf397792d58280928d23686313a8da810485a should have also applied the dtc.patch to the 2.6.1 kernel. This commits applies it, so both

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> Currently meta-zephyr only checks out a subset of the kernel source. With the addition of being able to generate machine configs

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit removes the need for calling out ZEPHYR_MODULES via MACHINEOVERRIDES. It uses west list to figure out what ZEPHYR_MODULES are

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit restructures meta-zephyr into meta-zephyr-core and meta-zephyr-bsp. It moves machine definitions into meta-zephyr-bsp in

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> We will need west for a few things. First, west knows about all the boards supported, so for automatic machine generation, we will need

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This set of patches relates to what I discussed at https://lists.yoctoproject.org/g/yocto/message/55285. Four major issues (and one

This is a classic problem with software that doesn't consider cross-compilation (and even when building for a similar architecture, like genericx86-64 on an x86 host, you're cross-compiling in

The documentation mentions a relationship between enable_uart and (lower) core frequency on some hardware variants - could there be a side-effect (if yes, maybe gpu_freq/arm_freq could play a factor)

For a reason I can't quite understand, everything stated working when I added ENABLE_UART = "1" Does anyone understand the relation between ENABLE_UART = "1" and RPI_USE_U_BOOT = "1"

I need to include an old open source project named judy for a legacy utility dependency. The recipe I have so far is listed at the end of this email. The build host is 64bit linux, I'm using dunfell

Signed-off-by: Ross Burton <ross.burton@...> --- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py b/config.py index 6da8d58..4c0b83b 100644 ---

Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 4 ++++ scripts/publish-artefacts | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/config.json

The exception for github.com was implemented in bitbake fetcher and backported to various versions, e.g. 1.46 used with dunfell