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@...> 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 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@...> This set of patches relates to what I discussed at https://lists.yoctoproject.org/g/yocto/message/55285. Four major issues (and one

Peter, Ross Thanks for your replies. This all makes perfect sense then. Thanks again Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com

Hi, No they are not mandatory for all fetchers. They are only used for content downloaded from non-local archives.

<michael.opdenacker@...> wrote: Checksums are for files that are fetched via http:// and friends, not local files. Ross

Greetings, I reused a simple "hello" recipe and added a non-matching checksum to it: ... SRC_URI = "file://helloworld.c" SRC_URI[md5sum] = "34f0efd76b4f18888888888833cdd129" ... The rest of the

Hi Tomasz, Thanks for your response. Yes, but the Zeus build image uses the same device tree that could run WiFi connection without any issues, I am comparing the same source and configuration

Hi JH, Are you using custom Linux kernel / custom device tree? Maybe there is some issue there? Kind regards, Tomasz Żyjewski Embedded Systems Engineer GPG: 5C495EA3EBEECA59 https://3mdeb.com |

Signed-off-by: Anuj Mittal <anuj.mittal@...> --- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py b/config.py index 4c0b83b..0f99557 100644 ---

Hi Rudolf, Thanks for your response and comments. Not that bad, the WiFi interfaces was fine, but it could not get dhcp response and IP address so an automatic private IP address 169.254

perhaps gdb-cross-${TARGET_ARCH} would be more generic.

Thanks for the feedback. Done on https://www.yoctoproject.org/community/mailing-lists/ I added lore.kernel.org links when applicable, and also added the openembedded-devel mailing list which was

Just a short hint if you didn’t discover it yourself, there is a (very) old BSP available from PHYTEC [1]. The downloads don’t seem to work, but they’re available on a probably forgotten FTP

Current Dev Position: YP 3.5 M2 Next Deadline: 17th Jan. 2022 YP 3.5 M2 build Next Team Meetings: Bug Triage meeting Thursday Jan. 20th 7:30 am PDT