Hi all,
Please find the mInutes from the October 15 TrusteFirmware TSC below.
Best regards,
Don Harbin
TrustedFirmware Community Manager
don.harbin(a)linaro.org
Trusted Firmware TSC 15 October - MinutesAttendees
*Abhishek (Arm)Julian Hall (Arm)Gyorgi Szing (Arm)Dan Handley (Arm)KangKang
(FutureWei)Julius Werner (Google)Joakim Bech (Linaro)David Brown
(Linaro)Don Harbin (Linaro)Andrew Butok (NXP)Dave Cocca (Renesas)Michael
Thomas(Renesas)*Actions:
*Abhishek: Send inclusive language email for voteAbhishek: Check to see if
can share Trusted Service Project use casesAbhishek: Gather vote on Trusted
Services Project request through emailDanH: Talk to Matteo / Shebu about
requirements for continued support of s/w stacks on new h/w (in particular
the 8.4 and beyond). Develop a migration plan.*Minutes:
Trusted Services Project request
-
TSC needs to approve. No budgetary impacts
-
JH: Shared overview slides of Trusted Services Project
-
JH: Ready to re-publish the work. A build system is in place. Tests in
place.
-
Need a public repo
-
Need tf.org front page update
-
Need Mail list
-
CI is a TBD
-
DanH: Plan to go to public CI from the start?
-
Gyorgy - an internal CI first would be easier.
-
DanH: Need to be aware of what upstream CI will require ahead of time
-
DC: How are CI requirements related to other ongoing projects
-
Gyorgy - currently no implementation, would need to do that and implement
-
DC: What about ongoing CI?
-
DanH: Should eventually migrate to TF CI
-
AB: Why not develop as part of TF-A Project?
-
Abhishek: Ideally would migrate TF-A services into this at some point.
-
JH: A stand-alone w/ dependencies makes sense
-
DanH: Within Arm, want to integrate the components in multiple
configurations.
-
Abhishek: Would help if clarify TF-A vs TF-M.
-
JB: Do we have use cases defined on how these will be used
-
JH: For crypto services, yes. Device Identity, Audit Logs, building
blocks to secure an IoT device are some examples.
-
JB: People ready to start using?
-
JH: Yes in the edge space
-
JB: Understanding the use cases on problem solving would be helpful
-
JH: Focus has been on Cortex A use cases
-
Abhishek: Will work to close this vote soon.
Inclusive Language
-
Abhishek: Looks like sufficient support.
-
No budget required, so no formal vote required. Want a vote?
-
DC: Vote here is ok.
-
Don: Destination of wording?
-
JW: Propose into coding style guides
-
Abhishek: Could also be a developer wiki page.
-
I.e. Duplicate in each coding guidelines plus a common section on the
wiki.
-
Maintainers would be asked to add these to the Projects Coding
Guidelines.
-
DanH: Proposing having it in one place and pointing to it.
-
Abhishek: Formalize the decision. Then can decide how to deploy.
-
Don: Where is exact wording?
-
Abhishek: Propose an email vote and the email will include the exact
wording in the email. Also that the maintainer for each project is
responsible to integrate into their coding guidelines
Arm V8 → 8.4 transition
-
JB: Member Companies have expressed concerns about Arm V8 and changes
required to 84.. What should we tell people?
-
DanH: Don’t have to change S/W on 8.4.
-
Abhishek: How does Hafnium leverage it?
-
JB: Don’t want to forget this when making changes. All changes may not
be backward compatible.
-
DanH: Take back to Matteo / Shebu a discussion about a migration plan
-
JB: Impacts to OP TEE components important to this.
<end>
Hello,
FYI:
NXP has just started Inclusive Language Project to review sensitive terms and update terminology in alignment with industry changes:
"After researching industry best practices, we've decided to replace the following words and to discontinue using them in documents.
* Master/Slave -> replace with Leader/Follower, Primary/Replica or Primary/Standby
* Blacklist/Whitelist -> replace with Denylist/Allowlist
Additionally,
* we will discontinue using other terms that are gender-related or discriminating in future materials, including technical, marketing and quality documents.
* we are also updating our NXP Style Guide accordingly."
So, according this new declaration, NXP supports the proposed TF Inclusive Language guideline.
Best regards,
Andrej Butok
From: TSC <tsc-bounces(a)lists.trustedfirmware.org<mailto:tsc-bounces@lists.trustedfirmware.org>> On Behalf Of Abhishek Pandit via TSC
Sent: mardi 13 octobre 2020 15:32
To: tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>
Subject: [TF-TSC] TSC Agenda 15 Oct 2020
Hi All,
Any agenda items for this week's meeting?
We have two existing topics which need to be decided by vote. Please do not reply to this email with your vote, there will be a separate email to the voting members.
1. Inclusive language guideline.
This is based on the discussion in the previous TSC meeting and the follow up proposal from Julius.
2. Trusted services project creation.
Arm team has been developing reference trusted services running in Secure EL0 that we plan to upstream in TF.org. This would form a new project to provide trusted services running on A profile devices.
The topic has already been discussed in board and Arm engineering team will provide further details in the TSC meeting.
Thanks
Abhishek
Hi Abhishek, all
I just answered to Julius's email concerning inclusive language
No additional topics from my side
I will be most likely not able to join this TSC meeting.
Regards,
Eric Finco
[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: logo_big5]
Eric FINCO | Tel: +33 (0)2 4402 7154
MDG | Technical Specialist
From: TSC <tsc-bounces(a)lists.trustedfirmware.org> On Behalf Of Abhishek Pandit via TSC
Sent: mardi 13 octobre 2020 15:32
To: tsc(a)lists.trustedfirmware.org
Subject: [TF-TSC] TSC Agenda 15 Oct 2020
Hi All,
Any agenda items for this week's meeting?
We have two existing topics which need to be decided by vote. Please do not reply to this email with your vote, there will be a separate email to the voting members.
1. Inclusive language guideline.
This is based on the discussion in the previous TSC meeting and the follow up proposal from Julius.
2. Trusted services project creation.
Arm team has been developing reference trusted services running in Secure EL0 that we plan to upstream in TF.org. This would form a new project to provide trusted services running on A profile devices.
The topic has already been discussed in board and Arm engineering team will provide further details in the TSC meeting.
Thanks
Abhishek
Hi All,
Any agenda items for this week's meeting?
We have two existing topics which need to be decided by vote. Please do not reply to this email with your vote, there will be a separate email to the voting members.
1. Inclusive language guideline.
This is based on the discussion in the previous TSC meeting and the follow up proposal from Julius.
2. Trusted services project creation.
Arm team has been developing reference trusted services running in Secure EL0 that we plan to upstream in TF.org. This would form a new project to provide trusted services running on A profile devices.
The topic has already been discussed in board and Arm engineering team will provide further details in the TSC meeting.
Thanks
Abhishek
