Look into chromium recipe

Branch master has been renamed to buster. Also setting protocol to https as GitHub is migrating away from unencrypted git protocol Signed-off-by: Devendra Tewari <devendra.tewari@...> ---

How do I get a -native recipe to use clang-native? I have this in my recipe, and target variant builds with clang: RUNTIME = "llvm" TOOLCHAIN = "clang" PREFERRED_PROVIDER:libgcc = "compiler-rt" All

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alexandre, Armin, Daiane, Jon, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: - Richard

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

hi sir, i am working on yocto ,i created one core-image-base inside that image i want to set logo on u-boot and kernel side ,i added psplash also in local.conf (IMAGE_FEATURES = "psplash") . but

Hi Khem, meta-rockchip does not have a honister branch for now because it is still working with master branch from OE-Core. This patch does not break this behaviour. Do I add a "known issues" to the

I could define a python function and use it like this: SRC_URI:append:rk3399 = "${@rk3399_fix_mac(d)}" Would that work better for you? Cheers, Quentin

v5.14.14 is already fixed. The only release currently is 3.4 and I hit that issue, hence the patch. I assume not everybody is updating to 3.4.1 when it's out, I've seen people running behind dot

Current yocto build is based on zeus… We have one board running Yocto Embedded linux that is sharing a drive partition via NFS. Another board is mounting the NFS share and has a few processes that

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

meta-rockchip does not have honister branch for now. So it expects master to keep working with honister for now. kernel upgrades are already committed into honister branch on meta-yocto-bsps so fix

Hi Stephen Thanks for the report! Sorry, I couldn't attend the meeting. Could I update this on https://wiki.yoctoproject.org/wiki/Releases? Cheers Michael. -- Michael Opdenacker, Bootlin Embedded

If you could explain what's *really* bothering you, I could try to find a proper explanation or agree with you but it's a bit too vague to me right now. Anyway, I'll do some guesses in the next

I am not yet convinced why should we have such version specific patch

<quentin.schulz@...> wrote: once dot release is out then thats whats maintained not the original release since they are incremental. the anon python to apply a patch. Can you explain

<quentin.schulz@...> wrote: Patching piece below looks quite a bit. lets just fix v5.14.14 and dont worry about 3.4

Thanks Martin, I added an extra step to sync up the ca-certificates within my docker container that I use to build dunfell. This seems to have resolved the issue that I encountered.

Are you working with Yocto builds? Do you need to understand what licenses you have? Do you need to understand what changed between two builds/releases/versions? I know the pain. License manifest will

From Linux kernel v5.14 to v5.14.11 (both included), the Ethernet MAC controller found on RK3399 is not working. A fix is available in v5.14.12 and later (available also in v5.15) which is provided