|
[meta-security] [PATCH 1/5] ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty
From: Ming Liu <liu.ming50@...>
'ima' does not have to be in native DISTRO_FEATURES, unset it to avoid
sanity check, this fixes a following error:
Signed-off-by: Ming Liu
From: Ming Liu <liu.ming50@...>
'ima' does not have to be in native DISTRO_FEATURES, unset it to avoid
sanity check, this fixes a following error:
Signed-off-by: Ming Liu
|
By
Ming Liu <liu.ming50@...>
·
#52365
·
|
|
[meta-security] [PATCH 0/5] Some fixes for IMA/EVM
From: Ming Liu <liu.ming50@...>
Ming Liu (5):
ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty
initramfs-framework-ima: fix a wrong path
meta: refactor IMA/EVM sign rootfs
From: Ming Liu <liu.ming50@...>
Ming Liu (5):
ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty
initramfs-framework-ima: fix a wrong path
meta: refactor IMA/EVM sign rootfs
|
By
Ming Liu <liu.ming50@...>
·
#52364
·
|
|
Re: Timing a recipe
As others have said, please look at the buildstats class and the data
it saves into TMPDIR/buildstats. It should do what you want and we have
tools like pybootchart which can show it
As others have said, please look at the buildstats class and the data
it saves into TMPDIR/buildstats. It should do what you want and we have
tools like pybootchart which can show it
|
By
Richard Purdie
·
#52363
·
|
|
Re: #av1 #armv6 #raspberrypi #neon
#av1
#armv6
#raspberrypi
#neon
So, what is your MACHINE variable set to?
Maybe knowing that, somebody can help.
Zee
So, what is your MACHINE variable set to?
Maybe knowing that, somebody can help.
Zee
|
By
Zoran
·
#52362
·
|
|
Re: Timing a recipe
As said, buildstats is *exactly* what you want. There's a forked
pybootchart in oe-core that can visualise the data too.
Ross
As said, buildstats is *exactly* what you want. There's a forked
pybootchart in oe-core that can visualise the data too.
Ross
|
By
Ross Burton <ross@...>
·
#52361
·
|
|
#av1 #armv6 #raspberrypi #neon
#av1
#armv6
#raspberrypi
#neon
Hello folks,
I have an issue integrating av1 in yocto. I get the compile error "compiling simd-neon.h requires -mfpu=neon or equivalent". The problem is that i use armv6 (raspberrypi zero w) so i
Hello folks,
I have an issue integrating av1 in yocto. I get the compile error "compiling simd-neon.h requires -mfpu=neon or equivalent". The problem is that i use armv6 (raspberrypi zero w) so i
|
By
safouane maaloul
·
#52360
·
|
|
Re: Regarding Mender integration
Hi,
Please see my comments in-line.
...
This looks like the patch you/mender try/tries to apply does not work with your u-boot version.[0]
[0]
Hi,
Please see my comments in-line.
...
This looks like the patch you/mender try/tries to apply does not work with your u-boot version.[0]
[0]
|
By
Robert Berger
·
#52359
·
|
|
Re: Keep .bbappend for older Yocto version
Yes in some layers they do work across releases but
That does have some restrictions and maintenance costs eg if you are patching a recipe via a bbappend then use more liberal bbappend names using %
Yes in some layers they do work across releases but
That does have some restrictions and maintenance costs eg if you are patching a recipe via a bbappend then use more liberal bbappend names using %
|
By
Khem Raj
·
#52358
·
|
|
Re: Keep .bbappend for older Yocto version
Thank you for the answer :-). Yes, that works, and it seems like it is commonly used already. But because there is a way to define which versions are supported in the machine configuration, I thought
Thank you for the answer :-). Yes, that works, and it seems like it is commonly used already. But because there is a way to define which versions are supported in the machine configuration, I thought
|
By
Jonas Vautherin
·
#52357
·
|
|
Re: Keep .bbappend for older Yocto version
perhaps you should create a new branch for this layer which will be
compatible with gatesgarth, you can seed it with dunfell branch
and then make needed changes
<jonas.vautherin@...> wrote:
perhaps you should create a new branch for this layer which will be
compatible with gatesgarth, you can seed it with dunfell branch
and then make needed changes
<jonas.vautherin@...> wrote:
|
By
Khem Raj
·
#52356
·
|
|
Re: Yocto Technical Team Minutes, Engineering Sync, for Feb 16 2021
You're welcome :-)
I take notes every week, but had stopped sending emails to the list at the end
of each meeting. A couple people mentioned privately that they appreciate the
notes being formatted
You're welcome :-)
I take notes every week, but had stopped sending emails to the list at the end
of each meeting. A couple people mentioned privately that they appreciate the
notes being formatted
|
By
Trevor Woerner
·
#52355
·
|
|
Keep .bbappend for older Yocto version
Good evening,
I am using Yocto Gatesgarth, and I was just updating a layer that was written for Dunfell. In the `conf/layer.conf`, I can simply add "gatesgarth" to `LAYERSERIES_COMPAT_pocketbeagle`,
Good evening,
I am using Yocto Gatesgarth, and I was just updating a layer that was written for Dunfell. In the `conf/layer.conf`, I can simply add "gatesgarth" to `LAYERSERIES_COMPAT_pocketbeagle`,
|
By
Jonas Vautherin
·
#52354
·
|
|
Re: Yocto Technical Team Minutes, Engineering Sync, for Feb 16 2021
Trevor,
Thanks for taking and sending the minutes.
-armin
Trevor,
Thanks for taking and sending the minutes.
-armin
|
By
Armin Kuster
·
#52353
·
|
|
Re: Timing a recipe
you could also look into using buildstats bbclass
https://wiki.yoctoproject.org/wiki/TipsAndTricks/InvestigatingBuildTime
>
>
you could also look into using buildstats bbclass
https://wiki.yoctoproject.org/wiki/TipsAndTricks/InvestigatingBuildTime
>
>
|
By
Khem Raj
·
#52352
·
|
|
Re: Timing a recipe
"time bitbake recipe" is perfect for manual things. But I wanted to also measure the recipe times when building the entire image. I ended up creating a bbappend with new pre/post tasks for the main
"time bitbake recipe" is perfect for manual things. But I wanted to also measure the recipe times when building the entire image. I ended up creating a bbappend with new pre/post tasks for the main
|
By
Rusty Howell
·
#52351
·
|
|
Yocto Technical Team Minutes, Engineering Sync, for Feb 16 2021
Yocto Technical Team Minutes, Engineering Sync, for Feb 16 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made to
Yocto Technical Team Minutes, Engineering Sync, for Feb 16 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made to
|
By
Trevor Woerner
·
#52350
·
|
|
Re: Regarding Mender integration
hello everyone,
I have an issue while integrating the mender in yocto.
getting error while adding INHERIT +=" mender-full" in the local.conf file .Can anyone pls help me out in solving this issue.
hello everyone,
I have an issue while integrating the mender in yocto.
getting error while adding INHERIT +=" mender-full" in the local.conf file .Can anyone pls help me out in solving this issue.
|
By
U RAVI KUMAR <uppadaravi2511@...>
·
#52349
·
|
|
QA notification for completed autobuilder build (yocto-3.2.2.rc1)
A build flagged for QA (yocto-3.2.2.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.2.2.rc1
Build hash information:
bitbake:
A build flagged for QA (yocto-3.2.2.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.2.2.rc1
Build hash information:
bitbake:
|
By
Pokybuild User <pokybuild@...>
·
#52348
·
|
|
Yocto Project Status WW07`21
Current Dev Position: YP 3.3 M3 development
Next Deadline: 1st March 2021 YP 3.3 M3 build
Next Team Meetings:
Bug Triage meeting Thursday Feb. 18th at 7:30am PDT
Current Dev Position: YP 3.3 M3 development
Next Deadline: 1st March 2021 YP 3.3 M3 build
Next Team Meetings:
Bug Triage meeting Thursday Feb. 18th at 7:30am PDT
|
By
Stephen Jolley
·
#52347
·
|
|
[meta-zephyr][PATCH V2 15/15] README.txt: Fix small typo in email subject prefix
From: Andrei Gherzan <andrei.gherzan@...>
Signed-off-by: Andrei Gherzan <andrei.gherzan@...>
---
README.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Andrei Gherzan <andrei.gherzan@...>
Signed-off-by: Andrei Gherzan <andrei.gherzan@...>
---
README.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
|
By
Andrei Gherzan
·
#52346
·
|