Damned that makes things more complicated :) That could push us along the following lines ? CONSOLE_DEVICES = "/dev/ttyS2 /dev/tty1" CONSOLE_BAUD_ttyS2 = "1500000" CONSOLE_BAUD_tty1 =

Good point, thanks for mentioning it. I suspect it would break things in all sorts of unimaginable ways ;-) For example, SERIAL_CONSOLES (note: plural) can contain more than one baud+device pair so

Signed-off-by: Steve Sakoman <steve@...> --- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py b/config.py index 2565bd7..03ccfba 100644 ---

----- Mail original ----- What about making this change at the poky level, then ?

Applied to meta-rockchip master.

while I appreciate this change, it does have an effect of removing the users away from BSP variables that core metadata layers have, e.g. SERIAL_CONSOLES is a well defined and documented variable and

Instead of having SoC-specific wks files and machine-specific wks files, it turns out all we need is one rockchip-specific wks file; any differences can be specified with variables. Boot tested with

Break out the conf/machine/include/rockchip-defaults.inc into: - conf/machine/include/rockchip-defaults.inc - conf/machine/include/rockchip-32.inc - conf/machine/include/rockchip-64.inc -

Take the console device and baud settings from the MACHINE configurations and reuse them in the wic files. This reduces duplication and eliminates a potential source of mistakes. Signed-off-by:

The console settings (baud and device) are scrambled and spread throughout the MACHINE configurations. Consolidate them and set defaults which are then overridden only as required. Signed-off-by:

Use initscript and service files provided by apparmor. Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-mac/AppArmor/apparmor_3.0.1.bb | 33 +--

Drop backport patches: 0001-apparmor-fix-manpage-order.patch 0001-libapparmor-add-missing-include-for-socklen_t.patch 0002-libapparmor-add-aa_features_new_from_file-to-public-.patch

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.9.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

Yocto Technical Team Minutes, Engineering Sync, for June 22, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made

Hello, We are pleased to announce the first milestone release for Yocto Project 3.4 (yocto-3.4_M1) is now available for download. Download:

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

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: Bug Triage meeting Thursday June 24th at 7:30am PDT

Hi all I move all TMPDIR in another folder The EXTRA_DISTRO_FETAURES += "package_managent" PACKAGE_CLASS := " package_deb " When I build the image the package_manager try to find the debs in the older

Hello, I dug further into yocto classes and I think I found what is going on. All seems to come from the fact that gcc debug-prefix-map and macro-prefix-map options are statically defined in

All, YP M+ or high bugs which moved to a new milestone in WW25 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11385 poky-container: clarify that