Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.1.rc2)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.1.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC

Re: [linux-yocto] xlnx-soc: fix bugs in DisplayPort subsystem.

On Fri, Dec 4, 2020 at 3:43 AM wrote: > > From: Quanyang Wang > > Hi Bruce & Michal, > > Would you please help review this patch series? These patch patches are > used to fix DisplayPort issues in mainline v5.10. > These look ok to me (and I'm kind of surprised at how small the overall changes

Re: [linux-yocto][yocto-kernel-cache][yocto-5.4][PATCH] nxp-s32g2xx: add config CONFIG_CMA_SIZE_MBYTES

merged to 5.4 Bruce In message: [linux-yocto][yocto-kernel-cache][yocto-5.4][PATCH] nxp-s32g2xx: add config CONFIG_CMA_SIZE_MBYTES on 08/12/2020 Xulin Sun wrote: > By default the cma memory size is 16M for the system, > Now explicitly increase this size to 128M in order to solve > the

Re: [linux-yocto][linux-yocto v5.4/standard/nxp-s32g2xx][PATCH] can: flexcan: drop repetitive execution can_rx_offload_add_timestamp

merged. Bruce In message: [linux-yocto][linux-yocto v5.4/standard/nxp-s32g2xx][PATCH] can: flexcan: drop repetitive execution can_rx_offload_add_timestamp on 03/12/2020 Xulin Sun wrote: > To fix below call trace: > [ 5748.193968] list_add double add: new=ff886ba61010, >

Re: [linux-yocto] [kernel-meta master 0/2] cn96xx: sync the yocto-5.4 and master branch

In message: [kernel-meta master 0/2] cn96xx: sync the yocto-5.4 and master branch on 02/12/2020 Kevin Hao wrote: > From: Kevin Hao > > Hi, > > Thease two patches are cherry-picked from the yocto-5.4 branch. Merged to master. Bruce > > Kevin Hao (2): > marvell-cn96xx: Enable the BPHY

[yocto] M+ & H bugs with Milestone Movements WW49

All, YP M+ or high bugs which moved to a new milestone in WW49 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 14114 Implement proper sphinx docs publishing randy.macl...@windriver.com

[yocto] Enhancements/Bugs closed WW49!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count st...@sakoman.com 2 richard.pur...@linuxfoundation.org 2 randy.macl...@windriver.com 1 Grand Total 5 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:

[yocto] Current high bug count owners for Yocto Project 3.3

All, Below is the list as of top 48 bug owners as of the end of WW49 of who have open medium or higher bugs and enhancements against YP 3.3. There are 98 possible work days left until the final release candidates for YP 3.3 needs to be released. Who Count richard.pur...@linuxfoundation.org

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 the triage page under the appropriate heading:

[linux-yocto][yocto-kernel-cache][yocto-5.4][PATCH] nxp-s32g2xx: add config CONFIG_CMA_SIZE_MBYTES

By default the cma memory size is 16M for the system, Now explicitly increase this size to 128M in order to solve the insufficient use cases (eg, PFE feature uses 64M). Signed-off-by: Xulin Sun --- bsp/nxp-s32g2xx/nxp-s32g2xx.cfg | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

You have missed few of my comments in v2 ! Regards, Naveen -Original Message- From: Saini, Naveen Kumar Sent: Monday, December 7, 2020 8:06 PM To: 'Wojciech Zmuda' ; yocto@lists.yoctoproject.org Cc: davide.ri...@huawei.com; zbigniew.bo...@huawei.com; jaroslaw.ma...@huawei.com;

[yocto] QA notification for completed autobuilder build (yocto-3.2.1.rc2)

A build flagged for QA (yocto-3.2.1.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2.1.rc2 Build hash information: bitbake: fec2b85689bba1d26ad6f376bc11cc29bb27cbe5 meta-arm: afa281b7a997bf265bfe221d1693a8a5bd4a243d

Re: [yocto] Which package provides full featured passwd, adduser, etc?

I looks like it is provided by just 'shadow' recipe: oe-pkgdata-util list-pkg-files shadow shadow: /etc/default/useradd /etc/limits /etc/login.access /sbin/nologin.shadow /sbin/vigr.shadow /sbin/vipw.shadow /usr/bin/chage /usr/bin/chfn.shadow /usr/bin/chsh.shadow /usr/bin/expiry /usr/bin/faillog

Re: [yocto] #uboot Problem compiling u-boot with bitbake

Hi Randy Thanks again for you help. I upgraded my build system to Ubuntu 16.04, and this resolved the build errors I was having. There were historical reasons for the build drive being installed with 14.04, but that is no longer necessary. Upgrading to 16.04 cured the build problem. Kind

Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.1.rc1)

On Mon, 2020-12-07 at 16:15 +, Pokybuild User wrote: > A build flagged for QA (yocto-3.2.1.rc1) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.2.1.rc1 > > > Build hash information: > > bitbake:

[yocto] Which package provides full featured passwd, adduser, etc?

Hi All, I'd like to replace busybox passwd, adduser (and friends) with full featured equivalents supporting --root option. Probably I overlooked something, but I cannot find right package to include in my rootfs. At my Ubuntu host those are parts of shadow-utils. What is the right package in

[yocto] IoT Long Term support Linux - Opening to the community of Redpesk@SEA the open source "Marine Grade Linux" by IoT.bzh.

Hello, As Marine requirement is very very close of any IoT (very) long term Linux requirement with high level of security and application isolation, I thought that this webinar from the Linux Fundation might be of interest to some of you... The

[yocto] meta-kernel -> meta-linux-mainline

Hi all, Just a quick announcement. The meta-kernel layer has been renamed to meta-linux-mainline to avoid any confusion. The new URL for the layer is https://gitlab.com/openembedded/community/meta-linux-mainline. The old URL (https://gitlab.com/openembedded/community/meta-kernel) will still work

[yocto] QA notification for completed autobuilder build (yocto-3.2.1.rc1)

A build flagged for QA (yocto-3.2.1.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2.1.rc1 Build hash information: bitbake: fec2b85689bba1d26ad6f376bc11cc29bb27cbe5 meta-arm: 03f2d78e456160f8f6f1ffe693a7bd1ad123e5d5

[yocto] [meta-zephyr][PATCH v2 1/5] zephyr-kernel: clone Nordic HAL

From: Wojciech Zmuda HAL for Nordic chipsets is one of Zephyr subprojects. It is downloaded by default by west. Clone the HAL repository so it can be used for building images for boards with Nordic chips. Signed-off-by: Wojciech Zmuda --- classes/zephyr-kernel-src.bbclass

[yocto] [meta-zephyr][PATCH v2 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

From: Wojciech Zmuda Flash boards supported via pyocd: MACHINE=xxx bitbake yyy -c flash_usb The only supported board for now is 96Boards Nitrogen. Modify its config accordingly. Modify helloworld and philosopers samples with adidtional .hex output file deployment, as this format is

[yocto] [meta-zephyr][PATCH v2 2/5] conf: machine: add support for Nordic nRF52832 Cortex-M4 chip

From: Wojciech Zmuda Add include for Cortex-M4 tunes and nRF52832. The nRF config appends 'nordic' to MACHINEOVERRIDES, so the kernel recipe can include Nordic HAL when this override is detected. Signed-off-by: Wojciech Zmuda --- conf/machine/include/nrf52832.inc | 10 ++

[yocto] [meta-zephyr][PATCH v2 3/5] conf: machine: add 96boards Nitrogen support

From: Wojciech Zmuda The board is based on Nordic nRF52832 Cortex-M4 chip. The support depends on Nordic HAL. It has been verified with zephyr-philosophers and zephyr-shell sample applications. Signed-off-by: Wojciech Zmuda --- conf/machine/96b-nitrogen.conf | 7 +++ 1 file changed, 7

[yocto] [meta-zephyr][PATCH v2 0/5] Add 96Boards Nitrogen support

From: Wojciech Zmuda Hello, v1 -> v2: - README.txt: fix bad MACHINE examples: change _ to -, i.e. 96b_nitrogen -> 96b-nitrogen This patch set adds support for the Nitrogen board by 96Boards. The support consists of: - adding configs for Cortex-M4, nRF52832 SoC and Nitrogen board, - adding

Re: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

Thanks for the patches. Please find my comments below. -Original Message- From: yocto@lists.yoctoproject.org On Behalf Of Wojciech Zmuda Sent: Monday, December 7, 2020 4:15 AM To: yocto@lists.yoctoproject.org Cc: davide.ri...@huawei.com; zbigniew.bo...@huawei.com;

[yocto] "cleanest" way to resolve python2/python3 recipe file install conflicts?

was recently presented with the following issue involving a zeus-based (actually, wind river LTS19-based -- effectively much the same) issue. group wants to move many python2 recipes to python3, but there is apparently a need to keep python2, including quite a number of the same recipes that

[yocto] qemu-5.1.0-r0 do_package_write_deb

Build Configuration: BB_VERSION   = "1.49.0" BUILD_SYS    = "x86_64-linux" NATIVELSBSTRING  = "fedora-33" TARGET_SYS   = "x86_64-overc-linux" MACHINE  = "intel-corei7-64" DISTRO   = "overc" DISTRO_VERSION   = "1.0" TUNE_FEATURES    =

[yocto] npm node-gyp python3 compatibility issue

Hi, I'm adding custom npm app using devtool (using poky dunfel) and hittin build issue like: TypeError: write() argument must be str, not bytes while trying to load binding.gyp To me it seems it's this exact problem described here:https://github.com/nodejs/node-gyp/issues/2051 as release of

[yocto] Qftp absent of qt5 and yocto "zeus" #zeus #QT5 #ftp

Hello everyone, I'm working with Qt5 and I would like to use Qftp QT module on my embedded system, but Yocto project "zeus" seems to don't have the recipe Qftp. Do you know if it exists an alternative or if Qt5 is not compatible with Qftp? Thanks for all and best reguards.