From: Ming Liu <liu.ming50@...> Introduce IMA_FORCE to allow the IMA policy be applied forcely even 'no_ima' boot parameter is available. This ensures the end users have a way to disable

Tested with rock-pi-4b and applied to master. Thanks!

can you post detailed log

Hi Guys, I am trying to build core-image-base using gatesgarth sources to generate esdk. But i am facing issue with opensbi_0.8.bb:do_fetch failed with exit code 'setscene whitelist'.

From: Yann Dirson <yann@...> TF-A runs between two u-boot stages which both uses 1500000 baud, it just makes no sense to use the same UART at a different rate. Here is a sample session

Well, in fact no , we shouldn't, is a short answer ;) Here is the long answer.. For bitbake and YP, we currently publish: master, master-next and 'stable' branches (e.g. 1.46, 1.48, 1.50 for bitbake

To close the loop, it turned out to be the case that CPU performance on VM has deteriorated which stress-ng showed. The VM has been rebuilt and everything seems to be holding fine now. Thanks for your

Build Sphinx docs for all versions newer than yocto-3.1.5 inclusive. Integrate suggestions from Quentin Schulz and Nicolas Dechesne. Signed-off-by: Michael Halstead

Registration is now open for the upcoming Yocto Project Summit!! details: https://www.yoctoproject.org/yocto-project-virtual-summit-2021/ CfP:

Yocto Technical Team Minutes, Engineering Sync, for April 6, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto

https://wiki.yoctoproject.org/wiki/Best_Known_Methods_(BKMs)_for_Package_Updating#Patch_Upstreaming

On 4/6/21 6:47 PM, Yann Dirson wrote: Very good. TF-A should work "out of the box" in meta-rockchip, so I think changing it's baudrate to 1500000 makes sense at this point (at least

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

No the vivado module sets up key variables, the lib path, and the include paths for building Xilinx low level drivers built into bootapp/kernel... I need to be able to include these components in

This patch fixes the issue: WARNING: libest-3.2.0-r0 do_fetch: Failed to fetch URL git://github.com/cisco/libest, attempting MIRRORS if available ERROR: libest-3.2.0-r0 do_fetch: Fetcher failure:

Hi all. I'd like to use dpkg-scanpackages inside my recipe The recipe copies some deb package into my folder ${D}/myfolder Then I'd like to apply dpkg-scanpackages to ${D}/myfolder I miss last

These are historical reasons. It started as 600, 1200, then quickly jumped to 9600 (4x), stayed some time there, and then transitioned via 19600 to final 115200. But I also see baud rates of

Interesting... For years (a few decades) everybody has used 115200 as the standard setup for UART, as global definition. Why suddenly somebody changed the UART baud rate to be non-standard? From the

<zoran.stojsavljevic@...> a écrit : Sure it is awkward when all tools have come to default to 115200, but then is the situation so different form when we transitionned from, say, 9600

hey! Thanks for starting this! sort -V is even better since it does "natural sort of (version) numbers within text", let's get ready for 3.10 ;) And using -V, how about something along these