Hi Trevor, On my side I have a minimal defconfig for our own board, which is very similar to the nanopi-m4, which could be used as a starting point for the latter. One possibility would be using a

From: Yann Dirson <yann@...> We have two board variants, respectively with 2GB and 4GB RAM. Signed-off-by: Yann Dirson <yann@...> --- Changes from v2: - commit message

Hi Randall, You cannot, you need to either not instal init-ifupdown and busybox-udhdpc or modify them to not install this file in your image. Cheers, Quentin

The Yocto Project mailing lists migrated to a new system and email address a while back. Update the README with the up-to-date information. Signed-off-by: Trevor Woerner <twoerner@...> ---

Personally, specifying wic should add wic.bmap implicitly. I can't imagine why anyone would want to generate a wic without the bmap to go with it. But my use-case is probably narrow.

I will be able to test it. once its installed

Hi Yann, Sorry to nitpick… Could you please tighten up the commit message? For example, please set the subject to something like: "NanoPi-M4: add" or perhaps "NanoPi-M4: add machines" then in the

Since we are using threads to read from child, no complex logic is needed for handle timeouts use alarm(2). [YOCTO #14220] Signed-off-by: Aníbal Limón <anibal.limon@...> --- utils.c | 60

In order to handle large output add a thread for read from childs using a pipe and remove non-blocking option. Modify bash unittest to output large data and cover this scenario. [YOCTO

Modify testcase to validate the actual exit status. [YOCTO #14217] Signed-off-by: Aníbal Limón <anibal.limon@...> --- tests/data/fail/ptest/run-ptest | 3 +++ tests/utils.c

Fixes, $ ./ptest-runner -d ./tests/data bash Signed-off-by: Aníbal Limón <anibal.limon@...> --- utils.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git

HI, Building up a customization layer over the top of poke to install 3rd party RPM files at build time. These packages contain some basic global configuration changes for the destination environment.

All, YP M+ or high bugs which moved to a new milestone in WW12 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11449 Allow overriding classes to

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 42 bug owners as of the end of WW12 of who have open medium or higher bugs and enhancements against YP 3.3. There are 28 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Ah, I was referring to the DTB used by the Kernel (which u-boot can switch), not the DTB used by u-boot itself (which AFAIK is compiled into u-boot and cannot be changed). > >> >> >> >> >

Hi Joshua, Wait, it's only the dtb used by u-boot which is different in this case, the kernel uses a single dtb for both variants. Those probably get embedded inside the bootloader, in any case

In case anyone else is affected by this… I tried building inside a Docker container based on Ubuntu 20.04 (and the buildtools removed) and the CVE database was populated properly (and CVE reports

FWIW, I'd rather u-boot could automatcially detect what variant of the board it's running on and do the right thing (usually, just selecting the proper DTB from the FIT image). The only