From: Emekcan Aras <Emekcan.Aras@arm.com>
To: Jon Mason <jdmason@kudzu.us>, Ross Burton <Ross.Burton@arm.com>
Cc: "meta-arm@lists.yoctoproject.org" <meta-arm@lists.yoctoproject.org>
Subject: Re: [PATCH 2/5] arm/optee: support optee 3.19
Date: Wed, 11 Jan 2023 09:22:25 +0000 [thread overview]
Message-ID: <DBBPR08MB4838A51C624195B5FCEDD03A8EFC9@DBBPR08MB4838.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <Y72UYV/BG39wEykn@kudzu.us>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
________________________________
From: Jon Mason <jdmason@kudzu.us>
Sent: Tuesday, January 10, 2023 4:37 PM
To: Ross Burton <Ross.Burton@arm.com>
Cc: Emekcan Aras <Emekcan.Aras@arm.com>; meta-arm@lists.yoctoproject.org <meta-arm@lists.yoctoproject.org>
Subject: Re: [PATCH 2/5] arm/optee: support optee 3.19
On Thu, Jan 05, 2023 at 03:30:14PM +0000, Ross Burton wrote:
> > +++ b/meta-arm/recipes-security/optee/optee-os-3_19.inc
> > @@ -0,0 +1,82 @@
> > +SUMMARY = "OP-TEE Trusted OS"
> > +DESCRIPTION = "Open Portable Trusted Execution Environment - Trusted side of the TEE"
> > +HOMEPAGE = "https://www.op-tee.org/"
> > +
> > +LICENSE = "BSD-2-Clause"
> > +LIC_FILES_CHKSUM = "[file://LICENSE;md5=c1f21c4f72f372ef38a5a4aee55ec173]file://LICENSE;md5=c1f21c4f72f372ef38a5a4aee55ec173"
> > +
> > +inherit deploy python3native
> > +require optee.inc
>
> …
>
> This file is 99% identical to optee-os.inc apart from FILEEXTRAPATHS, so put that assignment in the .bb and include the common optee-os.inc.
>
> Whilst I’m there…
>
> > +do_compile:prepend() {
> > + PLAT_LIBGCC_PATH=$(${CC} -print-libgcc-file-name)
> > +}
>
> This doesn’t appear to do anything, can you remove it in a separate commit.
>
> > +# note: "textrel" is not triggered on all archs
> > +INSANE_SKIP:${PN} = "textrel"
> > +# Build paths are currently embedded
> > +INSANE_SKIP:${PN} += "buildpaths"
>
> Can you experiment and remove these to see if they’re still valid?
>
> Ross
>
Looks like I missed this and pulled it in without being commented on.
Emekcan, can you address this in a follow-on patch?
Thanks,
Jon
Yeah sure, I had the patch, just need to rebase it
Thanks
Emek
[-- Attachment #2: Type: text/html, Size: 3521 bytes --]
next prev parent reply other threads:[~2023-01-11 9:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 14:39 [PATCH 0/5] Add optee-os 3.19 recipe emekcan.aras
2022-12-21 14:39 ` [PATCH 1/5] arm/optee: Move optee-3.18 patches emekcan.aras
2022-12-21 14:39 ` [PATCH 2/5] arm/optee: support optee 3.19 emekcan.aras
2023-01-05 15:30 ` Ross Burton
2023-01-10 16:37 ` Jon Mason
2023-01-11 9:22 ` Emekcan Aras [this message]
2023-01-12 17:58 ` [meta-arm] " Denys Dmytriyenko
2023-01-12 18:15 ` Ross Burton
2023-01-13 9:52 ` Emekcan Aras
2023-01-13 10:38 ` Ross Burton
2022-12-21 14:39 ` [PATCH 3/5] arm-bsp/optee-os: Adds 3.19 bbappend emekcan.aras
2022-12-21 14:39 ` [PATCH 4/5] arm-bsp/optee-os: N1SDP support for optee-os 3.19 emekcan.aras
2022-12-21 14:39 ` [PATCH 5/5] arm/qemuarm-secureboot: pin optee-os version emekcan.aras
2022-12-21 15:37 ` [meta-arm] " Sumit Garg
2022-12-21 15:59 ` Emekcan Aras
2022-12-22 6:48 ` Sumit Garg
2022-12-22 8:42 ` Emekcan Aras
2022-12-23 5:47 ` Sumit Garg
2023-01-05 15:31 ` Ross Burton
2023-01-09 16:23 ` [PATCH 0/5] Add optee-os 3.19 recipe Jon Mason
2023-01-10 18:27 ` Jon Mason
2023-01-13 18:05 ` Jon Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DBBPR08MB4838A51C624195B5FCEDD03A8EFC9@DBBPR08MB4838.eurprd08.prod.outlook.com \
--to=emekcan.aras@arm.com \
--cc=Ross.Burton@arm.com \
--cc=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).