> -Original Message-
> From: yocto@lists.yoctoproject.org On
> Behalf Of Bruce Ashfield via lists.yoctoproject.org
> Sent: 12 May 2021 16:25
> To: Yann Dirson
> Cc: Yocto discussion list
> Subject: Re: [yocto] Understanding kernel patching in linux-yocto
>
> On Wed, May 12, 2021 at
> -Original Message-
> From: Richard Purdie
> Sent: 02 March 2021 21:50
> To: Diego Santa Cruz ;
> st...@sakoman.com
> Cc: rustyhow...@gmail.com; Yocto (yocto@lists.yoctoproject.org)
>
> Subject: Re: [yocto] Reducing the perl footprint on my image
>
[...]
> > So I locally extended the
> -Original Message-
> From: yocto@lists.yoctoproject.org On
> Behalf Of Steve Sakoman via lists.yoctoproject.org
> Sent: 02 March 2021 21:06
> To: Steve Sakoman
> Cc: rustyhow...@gmail.com; Yocto (yocto@lists.yoctoproject.org)
>
> Subject: Re: [yocto] Reducing the perl footprint on my
From: Jonas Vautherin
Sent: 31 January 2021 22:23
To: Aaron Cohen
Cc: Diego Santa Cruz ; Paul Barker
; Yocto-mailing-list
Subject: Re: [yocto] Writing a BSP from downstream kernel sources
Thanks Aaron!
That seems to remove the log2 warnings, but it seems like they were not related
to those
From: yocto@lists.yoctoproject.org On Behalf Of
Jonas Vautherin via lists.yoctoproject.org
Sent: 24 January 2021 14:30
To: Jonas Vautherin
Cc: Paul Barker ; Yocto-mailing-list
Subject: Re: [yocto] Writing a BSP from downstream kernel sources
Just to close this: it seems like the
Hi there,
From: yocto@lists.yoctoproject.org On Behalf Of
vijayrakeshmunganda via lists.yoctoproject.org
Sent: 27 November 2020 09:47
To: yocto@lists.yoctoproject.org
Subject: [yocto] Yocto AWS MQTT: ssl.SSLCertVerificationError: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed:
> -Original Message-
> From: yocto@lists.yoctoproject.org On
> Behalf Of Damien LEFEVRE via lists.yoctoproject.org
> Sent: 26 May 2020 11:02
> To: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] gpg: can't connect to the agent: File name too long
>
> I think my problem is that the
> -Original Message-
> From: yocto@lists.yoctoproject.org On Behalf
> Of Armpit via Lists.Yoctoproject.Org
> Sent: 06 December 2019 18:38
> To: yocto@lists.yoctoproject.org
> Cc: yocto@lists.yoctoproject.org
> Subject: [yocto] [meta-security][PATCH] meta-security: add layer index
>
From: Philip Tricca
These have changed upstream.
Signed-off-by: Philip Tricca
Signed-off-by: Diego Santa Cruz
---
meta-tpm/recipes-tpm2/tpm2-abrmd/files/tpm2-abrmd.default | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This ports patches from the meta-measured layer that fix tpm2-abrmd
not starting up.
The first patch is necessary on kernels 4.12 and later.
The second patch is necessary after the update to 2.3.0.
Philip Tricca (1):
tpm2-abrmd: Port command line options to new version.
Trevor Woerner (1):
From: Trevor Woerner
Newer kernels, in addition to the traditional /dev/tpmX device nodes, are now
also creating /dev/tpmrmX device nodes. This causes this script to get
confused and abort, meaning tpm2-abrmd does not get started during boot.
Fix for
Dear all,
I got the feedback below by private email (was meant to be sent to the m-l), so
I think I’ll go with meta-tmp2 from meta-secure-core for now.
But I may switch to meta-tpm from meta-security in the future as it seems to
have more tpm2 related recipes (I’m on thud for now and the
Hello,
I need to use a TPM2 software stack for my project (tpm2-tools, tpm2-abrmd,
tpm2-tss, etc.), where I am already using Yocto, meta-intel, meta-oe,
meta-networking, etc.
I see there are at least the following three layers that carry the necessary
TPM2 bits, with varying recipe versions.
13 matches
Mail list logo
