When kernel builds with -Werror=designated-init, there will be an
error as below, include the field names in the struct when init it
to fix the error.
drivers/misc/axxia-ncr.c:202:9: error: positional initialization of field in
'struct' declared with 'designated_init' attribute
On Wed, Nov 01, 2023 at 11:04:36PM -0400, Jon Mason wrote:
> Signed-off-by: Jon Mason
Here is the CI for this series
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/1058077201
As you can see from the branch history, these 2 patches were applied
on top of the zephyr version update series.
Retested the zephyr kernel tests to verify which ones are now building
and which ones are now passing CI on qemu machines. They are organized
as follows:
* Any test that fails to be configured is added to a list in
zephyr-kernel-test.inc
* Any test that fails to compile for all machines is
Signed-off-by: Jon Mason
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 2ecf132a6ff5..c94274cdbc2b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@
-image: ghcr.io/siemens/kas/kas:3.2.3
+image:
Signed-off-by: Jon Mason
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 2ecf132a6ff5..c94274cdbc2b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@
-image: ghcr.io/siemens/kas/kas:3.2.3
+image:
On Wed, Nov 01, 2023 at 05:58:07PM +0800, Naveen Saini wrote:
> https://github.com/zephyrproject-rtos/zephyr/releases/tag/v3.5.0
I tested this series and you can see the results at
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/1057638542
There are new issues for intel-x86-64 and
Add the generic Yocto Project tools SECURITY.md as a first step.
Signed-off-by: Tim Orling
---
SECURITY.md | 24
1 file changed, 24 insertions(+)
create mode 100644 SECURITY.md
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 000..7d2ce1f
---
On Wed, 1 Nov 2023 at 16:45, wrote:
> I think these differences between SDK and bitbake environment are no
> longer required and they have been problematic. I would try to make the
> bitbake environment usable like the eSDK environment was without trying
> to replicate all the details of the eSDK
On Wed, 2023-11-01 at 16:19 +0100, Alexander Kanavin via
lists.openembedded.org wrote:
> On Wed, 1 Nov 2023 at 15:18, wrote:
> > We are currently experimenting with replacing the eSDK installer
> > with
> > the bitbake build environment for our users. Part of this
> > transformation is, of
Add two variables IMA_FILE_SIGNATURES_FILE and EVM_FILE_SIGNATURES_FILE
for filenames where the ima_evm_sign_rootfs script can write the names
of files and their IMA or EVM signatures into. Both variables are
optional. The content of the file with IMA signatures may look like
this:
Some CDN stats are now published at https://www.jsdelivr.com/oss-cdn/yocto.
Let me know if you notice anything that needs to be changed.
On Wed, Oct 18, 2023 at 10:33 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Wed, 2023-10-18 at 14:02 +0200, Alexander Kanavin wrote:
> >
Hi Richard, hi Alex
On Mon, 2023-10-30 at 14:07 +, Richard Purdie wrote:
> On Mon, 2023-10-30 at 14:50 +0100, Alexander Kanavin wrote:
> > On Thu, 14 Sept 2023 at 14:56, Richard Purdie
> > wrote:
> > > There are design elements to this work. We need to work out how
> > > we can
> > > make
On Wed, 1 Nov 2023 at 15:18, wrote:
> We are currently experimenting with replacing the eSDK installer with
> the bitbake build environment for our users. Part of this
> transformation is, of course, the shared sstate-cache, for which this
> discussion seems quite relevant. The workflow we are
Hi Alex, hi Richard
The discussion looks really interesting. I would like to contribute
some comments from the point of view of a rather naive user and try to
understand the workflows for which these improvements would be
beneficial also on a bigger picture.
On Thu, 2023-09-14 at 20:51 +0200,
I have specifically tested this on 5.15 on Kirkstone which is what we use at
work. However, I would expect the same behavior on almost any kernel AFAICT the
meaning of CONFIG_DEVMEM and CONFIG_STRICT_DEVMEM has been consistent since
Linux 4.5 and is the same through current upstream.
-Andy
On
I am trying to build an image for beagleplay using kirkstone branch. I am stuck
at issues when using arm-poky-linux-gnueabi, both compile OK when using
arm-poky-eabi.
Are these known issues, or am I missing something?
For libgcc I notice:
| configure: error: cannot compute suffix of object
We run AUH from the autobuilder and we don't need the cron script any more,
we'd point people at the scripts there instead.
Signed-off-by: Richard Purdie
---
weeklyjob.sh | 30 --
1 file changed, 30 deletions(-)
delete mode 100755 weeklyjob.sh
diff --git
We don't need the ability to change this per layer, drop the option
and simplify the code.
Signed-off-by: Richard Purdie
---
upgrade-helper.py | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/upgrade-helper.py b/upgrade-helper.py
index 3be6d68..869dc3f 100755
---
Without it, auto-upgrade-helper skip most of the recipes because they do
not have a specific maintainer.
Signed-off-by: Yoann Congal
---
config.json | 30 ++
1 file changed, 30 insertions(+)
diff --git a/config.json b/config.json
index 6143969..ddf015f 100644
---
https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.16.3
Signed-off-by: Naveen Saini
---
.../zephyr-sdk/{zephyr-sdk_0.16.1.bb => zephyr-sdk_0.16.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-zephyr-core/recipes-devtools/zephyr-sdk/{zephyr-sdk_0.16.1.bb =>
v3.5.0 is available, now drop support for old version.
Signed-off-by: Naveen Saini
---
...ry-generation-issue-in-cross-compila.patch | 93 --
.../zephyr-kernel/zephyr-kernel-src-3.4.0.inc | 286 --
2 files changed, 379 deletions(-)
delete mode 100644
https://github.com/zephyrproject-rtos/zephyr/releases/tag/v3.5.0
Signed-off-by: Naveen Saini
---
...ry-generation-issue-in-cross-compila.patch | 80 ++
.../zephyr-kernel/zephyr-kernel-src-3.5.0.inc | 270 ++
.../zephyr-kernel/zephyr-kernel-src.inc | 2 +-
3 files
Le 01/11/2023 à 01:05, Yoann Congal a écrit :
> v2->v3:
> * Split single patch in a series. Previous version was:
> [auh][PATCH v2] upgrade-helper.py: Add layer command line option
I've just noticed that the "v3" tag is missing from the mail subject. Sorry
about that :(
> * Removed short
On Wed, Nov 1, 2023 at 6:43 AM Ravi Kumar wrote:
>
> Hi team ,
> Most of the IOT lines have been deployed on Yocto now the new
> trend/requirement is security .
> On yocto we see that we moved away making every one as root and every
> resource on the device tree accessible .
> Where it
24 matches
Mail list logo
