Attendees
Dan Handley (Arm)
Ashutosh Singh (Arm)
Eric Finco (ST)
Lionel Debieve (ST)
Kangkang (Futurewei)
Julius Werner (Google)
Joakim Bech (Linaro)
Erik Shreve (TI)
David Brown (Linaro)
Bill Fletcher (Linaro Community Projects)
Andrej Butok (NXP)
Dave Cocca (Renesas)
`
Minutes
Website UX
BF: (see slide).
Have set up a specific branch for the website code on GitHub that generates
a preview.
Would like project leads for each project to fill out the schema at the top
of each of the project pages with the key project-specific links to
code/review/documentation etc and a small amount of descriptive text. If
they push that to the new UX branch it will update the preview.
DH: Are approvals needed?
BF: Admins for the website code approve PRs, but this is still just a
preview, not the live site.
Landing CHERI/Morello enabled Hafnium
https://developer.arm.com/architectures/cpu-architecture/a-profile/morellohttps://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html
JB: Have an implementation of Hafnium that pre-dates TF. Consortium asking
if this is something that TF would be interested in. Have asked Robert from
Cambridge Uni if he would be able to give an overview of the project.
EF: Is there a specific usecase or is it just that it’s available?
JB: Nothing to prevent having Morello in any firmware component. This is a
proof of concept - not confirmed that it will become a product. Aim is to
kill big classes of security issues.
JB: Should we say it’s too early or ask Robert to present?
DH: Are others interested? Maybe it’s a bit early?
JB: Can still ask if Robert is available/interested to discuss.with us.
Ownership of project release strategy/execution, especially for OP-TEE
JB: For OP-TEE after transfer to TF, have been asked who is setting the
direction of the project. Still currently mainly Lenaro. Seems wrong that
Linaro Jira instance has details of when we are going to make releases.
Should we create some kind of tracking internally?
EF: Intent in transfer was to encourage other users of OP-TEE to become
more active in the community. Needs minimum infrastructure to show a live
forum. Seems a mandatory step to set this up.
DH: Seems a Product Management/Technology Management question. Could ask
Arm Technology Managers (Matteo/Shebu) to take on more of a role. Shebu is
looking at Arm’s contributions to OP-TEE.
JB: Main contributors are Linaro Members, Arm, non-members. Would be good
if could get these 3 groups closer together.
DH: For other projects intersection of collaborators is more complex. Feels
like we need a TF.org roadmap that coalesces each individual project
contribution.
JB: Would be nice to have some kind of reference implementation with
OP-TEE, TF, Mbed-TLS, Hafnium …
DH: That’s a ‘platform solutions’ problem (different team in Arm). Could
point to work done by the teams involved in that within Arm. Are we looking
for alignment and unified releases. Think projects would want to determine
their own cadence.
JB: Yes. But should be possible to find when the releases are happening
from tf.org.
DH: You were also talking about the resources to make the releases.
JB: We are rotating between Linaro staff to do the releases. Maybe just
showing how/when it will happen on the website project page. also get the
question a couple of times on LTS branches.
DH: Don’t think project teams would be able to manage additional LTS costs.
AS: Same for TF-M. No plan yet for TLS.
DH: Think LTS is something special. Primary customers are product vendors.
JB: Will think some more and come up with a proposal
Standard Hardware Requirements
EF: Minimum hardware requirements. Was discussed back in June. Abhishek
proposed to come back on it when I was available. When we discuss Level 3
isolation, what is the minimum number of descriptors needed. Was a
presentation on this in the Tech Forum. also discussion of different
profiles. Could TF-M specify the minimum requirements for HW to support the
features?
DH: Minimum number of MPU regions - function of the number of secure
services that need to be supported. Does it not follow from that? Does PSA
specify?
EF: Didn’t find it in the PSA document
DH: Probably not explicit but maybe it can be inferred.
EF: PSA doesn’t enforce implementation. Could provide SiPs with what the
profiles mean.
DH: If it’s missing (from PSA) then needs to be defined somewhere.
AS: Partly defined in PSA but doesn’t go to the granularity for e.g.
different profiles. Do see value but separate discussion as to where.
Number of descriptors doesn’t scale with number of regions since can
re-use. Do need to reserve a few for the core code. MPU is one hardware
piece but what about other bus masters?
DH: Seems like a need for some kind of hardware integration guide.
AS: would hope that someone from the user community can come up with a
starting point. Could be a topic for the Technical Forum and some initial
point for what makes sense for each of the profiles.
Groups.io discussion
DH: Considered a better interface than plain old mailman lists.
DB: Zephyr happy with it. Could use it and not realise it has the web
interface.
DH: Conclusion to migrate completely. Take a break or migrate domain
support. $1000/y for non-profits. If TSC think it’s ok then can just push
this to the Board.
BF: Current cost to the project for Linaro to maintain the mailman servers
(plus endless spam work)
DC: Sounds good. In favour.
JB: Agree (vs mailman)
GitHub/GitLab discussion
DH: Started with the reasons that OP-TEE should stay on GitHub (from
Joakim). Think Mbed-TLS would agree. Other projects in Arm looking at how
to upstream. Issue tracking and wiki is currently not used consistently.
Arm looking at GitLab internally. May not be the driving requirement for
TF. Point raised by Julius that GitHub code review is not ideal. Either
hybrid solution or some kind of plug in (to GitHub)
DB: Are projects that do Gerrit review on GitHub.
DH: There is ‘GerritHub’ but also possible plugins.
DB: Also the issue of ‘community’ in that it’s an expectation that embedded
work will happen on GitHub.
EF: Spoke to some of our developers had a very negative view of GitLab (may
be ST specific).
DH: Is self-hosting a requirement?
DB: Don’t have DoS issues
DH: Mbed TLS does use private repositories for security advisories.
DB: Can have private repositories on GitHub
JB: (Demonstrates security advisory/private repositories)
DH: Who owns https://github.com/TrustedFirmware ? (Action BF)
Action BF/DH to look at the hybrid solution
DH: MbedTLS will have to move since under an Arm/Mbed account. Bit worried
about lumping many projects under one organisation due to potential risks.
Like that OP-TEE is in it’s own org account.
--
[image: Linaro] <http://www.linaro.org/>
*Bill Fletcher* | *Field Engineering*
T: +44 7833 498336 <+44+7833+498336>
bill.fletcher(a)linaro.org | Skype: billfletcher2020
Sorry I missed Eric's topics. I've broadened the release topic to include LTS releases.
* Update on website rework (Bill)
* Landing CHERI enabled Hafnium (Joakim). Some background:
https://developer.arm.com/architectures/cpu-architecture/a-profile/morellohttps://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html
* Ownership of project release strategy/execution, including LTS releases (Joakim, at least for OP-TEE part)
* Standard HW requirements for TF-M, e.g. min number of MPU regions for level 3 isolation (Eric)
* Continuation of Groups.io discussion (Dan)
* Continuation of GitHub/GitLab discussion (Dan)
Regards
Dan
From: TSC <tsc-bounces(a)lists.trustedfirmware.org> On Behalf Of Dan Handley via TSC
Sent: 20 August 2020 14:52
To: tsc(a)lists.trustedfirmware.org
Subject: Re: [TF-TSC] Request for TSC agenda topics 2020-08-20
Hi all
Thanks for the additional topics. The current agenda is as follows (my proposed order):
* Update on website rework (Bill)
* Landing CHERI enabled Hafnium (Joakim). Some background:
https://developer.arm.com/architectures/cpu-architecture/a-profile/morellohttps://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html
* Ownership of project release strategy/execution, especially for OP-TEE (Joakim)
* Continuation of Groups.io discussion (Dan)
* Continuation of GitHub/GitLab discussion (Dan)
Regards
Dan.
From: Dan Handley
Sent: 17 August 2020 12:48
To: tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>
Subject: Request for TSC agenda topics 2020-08-20
Hi all
I'll be chairing the TSC meeting this Thursday. Does anyone have any agenda topics for then?
So far I have:
* Continuation of Groups.io discussion
* Continuation of GitHub/GitLab discussion
Regards
Dan.
Hi all
I'll be chairing the TSC meeting this Thursday. Does anyone have any agenda topics for then?
So far I have:
* Continuation of Groups.io discussion
* Continuation of GitHub/GitLab discussion
Regards
Dan.
Hi,
On Wed, 19 Aug 2020 at 13:20, Dan Handley via TSC <
tsc(a)lists.trustedfirmware.org> wrote:
> Hi
>
>
>
> Regarding the CHERI adaptation of Hafnium, I think we'll need to
> understand the purpose, status and plans for this before we can consider
> the technical/legal aspects. Joakim – do you have that info?
>
Unfortunately I don't have that much background information, since there is
an agreement between the various companies that have been working with it
(Linaro is not one of them). So, I'm a bit of a messenger here in an early
stage, trying to start a discussion around it. Due to this I've already
discussed with Robert N. M. Watson (University of Cambridge) and I've
suggested that we could invite him to one of our TSC calls and he could
explain more about it and after that it should be easier to make a decision
whether this is something the TF TSC would consider being worked on or not.
But before inviting people outside the TSC I thought it'd be good to have a
brief discussion within the TSC itself.
Regards,
Joakim
>
>
> Regards
>
>
>
> Dan.
>
>
>
>
>
> *From:* TSC <tsc-bounces(a)lists.trustedfirmware.org> *On Behalf Of *Serban
> Constantinescu via TSC
> *Sent:* 19 August 2020 11:25
> *To:* Joakim Bech <joakim.bech(a)linaro.org>; Andrew Walbran <
> qwandor(a)google.com>
> *Cc:* tsc(a)lists.trustedfirmware.org
> *Subject:* Re: [TF-TSC] Request for TSC agenda topics 2020-08-20
>
>
>
> +Andrew Walbran <qwandor(a)google.com> in case he has any opinions on the
> CHERI proposal below.
>
>
>
> Hi Joakim,
>
>
>
> On Tue, Aug 18, 2020 at 6:01 PM Joakim Bech via TSC <
> tsc(a)lists.trustedfirmware.org> wrote:
>
> Hi,
>
>
>
> If there is enough time, then I would like to discuss OP-TEE release work,
> questions like: Who will make the release? When should it be done? Where
> should it be tracked? Currently, the answer to all of those are more or
> less "Linaro / Linaro decides", but our (Linaro's) impression is that we
> should try to get this transferred to TrustedFirmware in some way. Linaro
> will certainly be involved in that kind of work in the future also, but we
> believe that the directions should come from TrustedFirmware.org instead of
> Linaro. This might even be something to consider for all TF projects? I.e.,
> not only OP-TEE? But again .. if time permits, otherwise we can push it to
> another call.
>
>
>
> A second topic is related to CHERI [1] and Hafnium. People working with
> the CHERI project asked me whether TrustedFirmware would be interested
> in an open-source CHERI adaptation of Hafnium? So I'd like to get the
> opinion from the TSC with regards to that. If the TSC is positive to it,
> then we have a few other things to consider like where it should go,
> separate CHERI branch(es), official tree with compile time flags? How to
> staff the activity? Legal aspects? Etc.
>
>
>
> Leaving aside the legal aspects which Arm and TF should express a view on,
> I suggest we first review the CHERI changes.
>
>
>
> If they don't put in danger any of the product deadlines and do not
> increase the code significantly we could consider incorporating them as
> part of the official tree. However, I believe the changes are based on an
> old Hafnium fork and add a non-trivial amount of new code - if that's the
> case a separate branch is a better option to start with.
>
>
>
> Best,
>
> Serban
>
>
>
>
>
> [1] http://cheri-cpu.org/
>
>
> Regards,
>
> Joakim
>
>
>
>
>
> On Mon, 17 Aug 2020 at 15:55, Bill Fletcher via TSC <
> tsc(a)lists.trustedfirmware.org> wrote:
>
> Hi Dan
>
>
>
> I can give an update on the website rework.
>
>
>
> Regards
>
>
>
> Bill
>
>
>
> On Mon, 17 Aug 2020 at 12:47, Dan Handley via TSC <
> tsc(a)lists.trustedfirmware.org> wrote:
>
> Hi all
>
>
>
> I'll be chairing the TSC meeting this Thursday. Does anyone have any
> agenda topics for then?
>
>
>
> So far I have:
>
>
>
> * Continuation of Groups.io discussion
>
>
>
> * Continuation of GitHub/GitLab discussion
>
>
>
> Regards
>
>
> Dan.
>
>
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
>
>
>
> --
>
>
>
> [image: Linaro] <http://www.linaro.org/>
>
> *Bill Fletcher* | *Field Engineering*
>
> T: +44 7833 498336 <+44+7833+498336>
> bill.fletcher(a)linaro.org | Skype: billfletcher2020
>
>
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
Hi
Regarding the CHERI adaptation of Hafnium, I think we'll need to understand the purpose, status and plans for this before we can consider the technical/legal aspects. Joakim – do you have that info?
Regards
Dan.
From: TSC <tsc-bounces(a)lists.trustedfirmware.org> On Behalf Of Serban Constantinescu via TSC
Sent: 19 August 2020 11:25
To: Joakim Bech <joakim.bech(a)linaro.org>; Andrew Walbran <qwandor(a)google.com>
Cc: tsc(a)lists.trustedfirmware.org
Subject: Re: [TF-TSC] Request for TSC agenda topics 2020-08-20
+Andrew Walbran<mailto:qwandor@google.com> in case he has any opinions on the CHERI proposal below.
Hi Joakim,
On Tue, Aug 18, 2020 at 6:01 PM Joakim Bech via TSC <tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>> wrote:
Hi,
If there is enough time, then I would like to discuss OP-TEE release work, questions like: Who will make the release? When should it be done? Where should it be tracked? Currently, the answer to all of those are more or less "Linaro / Linaro decides", but our (Linaro's) impression is that we should try to get this transferred to TrustedFirmware in some way. Linaro will certainly be involved in that kind of work in the future also, but we believe that the directions should come from TrustedFirmware.org instead of Linaro. This might even be something to consider for all TF projects? I.e., not only OP-TEE? But again .. if time permits, otherwise we can push it to another call.
A second topic is related to CHERI [1] and Hafnium. People working with the CHERI project asked me whether TrustedFirmware would be interested in an open-source CHERI adaptation of Hafnium? So I'd like to get the opinion from the TSC with regards to that. If the TSC is positive to it, then we have a few other things to consider like where it should go, separate CHERI branch(es), official tree with compile time flags? How to staff the activity? Legal aspects? Etc.
Leaving aside the legal aspects which Arm and TF should express a view on, I suggest we first review the CHERI changes.
If they don't put in danger any of the product deadlines and do not increase the code significantly we could consider incorporating them as part of the official tree. However, I believe the changes are based on an old Hafnium fork and add a non-trivial amount of new code - if that's the case a separate branch is a better option to start with.
Best,
Serban
[1] http://cheri-cpu.org/
Regards,
Joakim
On Mon, 17 Aug 2020 at 15:55, Bill Fletcher via TSC <tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>> wrote:
Hi Dan
I can give an update on the website rework.
Regards
Bill
On Mon, 17 Aug 2020 at 12:47, Dan Handley via TSC <tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>> wrote:
Hi all
I'll be chairing the TSC meeting this Thursday. Does anyone have any agenda topics for then?
So far I have:
* Continuation of Groups.io discussion
* Continuation of GitHub/GitLab discussion
Regards
Dan.
--
TSC mailing list
TSC(a)lists.trustedfirmware.org<mailto:TSC@lists.trustedfirmware.org>
https://lists.trustedfirmware.org/mailman/listinfo/tsc
--
[Linaro]<http://www.linaro.org/>
Bill Fletcher | Field Engineering
T: +44 7833 498336<tel:+44+7833+498336>
bill.fletcher(a)linaro.org<mailto:bill.fletcher@linaro.org> | Skype: billfletcher2020
--
TSC mailing list
TSC(a)lists.trustedfirmware.org<mailto:TSC@lists.trustedfirmware.org>
https://lists.trustedfirmware.org/mailman/listinfo/tsc
--
TSC mailing list
TSC(a)lists.trustedfirmware.org<mailto:TSC@lists.trustedfirmware.org>
https://lists.trustedfirmware.org/mailman/listinfo/tsc
+Andrew Walbran <qwandor(a)google.com> in case he has any opinions on the
CHERI proposal below.
Hi Joakim,
On Tue, Aug 18, 2020 at 6:01 PM Joakim Bech via TSC <
tsc(a)lists.trustedfirmware.org> wrote:
> Hi,
>
> If there is enough time, then I would like to discuss OP-TEE release work,
> questions like: Who will make the release? When should it be done? Where
> should it be tracked? Currently, the answer to all of those are more or
> less "Linaro / Linaro decides", but our (Linaro's) impression is that we
> should try to get this transferred to TrustedFirmware in some way. Linaro
> will certainly be involved in that kind of work in the future also, but we
> believe that the directions should come from TrustedFirmware.org instead of
> Linaro. This might even be something to consider for all TF projects? I.e.,
> not only OP-TEE? But again .. if time permits, otherwise we can push it to
> another call.
>
> A second topic is related to CHERI [1] and Hafnium. People working with
> the CHERI project asked me whether TrustedFirmware would be interested
> in an open-source CHERI adaptation of Hafnium? So I'd like to get the
> opinion from the TSC with regards to that. If the TSC is positive to it,
> then we have a few other things to consider like where it should go,
> separate CHERI branch(es), official tree with compile time flags? How to
> staff the activity? Legal aspects? Etc.
>
Leaving aside the legal aspects which Arm and TF should express a view on,
I suggest we first review the CHERI changes.
If they don't put in danger any of the product deadlines and do not
increase the code significantly we could consider incorporating them as
part of the official tree. However, I believe the changes are based on an
old Hafnium fork and add a non-trivial amount of new code - if that's the
case a separate branch is a better option to start with.
Best,
Serban
> [1] http://cheri-cpu.org/
>
> Regards,
> Joakim
>
>
> On Mon, 17 Aug 2020 at 15:55, Bill Fletcher via TSC <
> tsc(a)lists.trustedfirmware.org> wrote:
>
>> Hi Dan
>>
>> I can give an update on the website rework.
>>
>> Regards
>>
>> Bill
>>
>> On Mon, 17 Aug 2020 at 12:47, Dan Handley via TSC <
>> tsc(a)lists.trustedfirmware.org> wrote:
>>
>>> Hi all
>>>
>>>
>>>
>>> I'll be chairing the TSC meeting this Thursday. Does anyone have any
>>> agenda topics for then?
>>>
>>>
>>>
>>> So far I have:
>>>
>>>
>>>
>>> * Continuation of Groups.io discussion
>>>
>>>
>>>
>>> * Continuation of GitHub/GitLab discussion
>>>
>>>
>>>
>>> Regards
>>>
>>>
>>> Dan.
>>>
>>>
>>> --
>>> TSC mailing list
>>> TSC(a)lists.trustedfirmware.org
>>> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>>>
>>
>>
>> --
>>
>> [image: Linaro] <http://www.linaro.org/>
>> *Bill Fletcher* | *Field Engineering*
>> T: +44 7833 498336 <+44+7833+498336>
>> bill.fletcher(a)linaro.org | Skype: billfletcher2020
>>
>> --
>> TSC mailing list
>> TSC(a)lists.trustedfirmware.org
>> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
Hi Dan and all,
I raised a topic for June TSC but looking at Abhishek minutes and as I was not able to join a couple of TSC meetings afterward, I propose to bring it back on the agenda:
-from June TSC minutes:
>Standard HW requirement for TF-M for PSA levels.
LD- Raising the topic based on Eric's email.
AP - As we have limited details possibly better to discuss next time when Eric joins.
May be TF-M tech forum comes up with proposal for TSC to ratify
-I also attached the email exchanged we had on the TSC list before June meeting on this topic
There was also in June a thread in the TF-A mailing list about an LTS version but I do not think the TSC discussed this topic and took a position on it so I propose to put on the agenda.
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 Bill Fletcher via TSC
Sent: lundi 17 août 2020 15:56
To: Dan Handley <Dan.Handley(a)arm.com>
Cc: tsc(a)lists.trustedfirmware.org
Subject: Re: [TF-TSC] Request for TSC agenda topics 2020-08-20
Hi Dan
I can give an update on the website rework.
Regards
Bill
On Mon, 17 Aug 2020 at 12:47, Dan Handley via TSC <tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>> wrote:
Hi all
I'll be chairing the TSC meeting this Thursday. Does anyone have any agenda topics for then?
So far I have:
* Continuation of Groups.io discussion
* Continuation of GitHub/GitLab discussion
Regards
Dan.
--
TSC mailing list
TSC(a)lists.trustedfirmware.org<mailto:TSC@lists.trustedfirmware.org>
https://lists.trustedfirmware.org/mailman/listinfo/tsc
--
[Linaro]<http://www.linaro.org/>
Bill Fletcher | Field Engineering
T: +44 7833 498336<tel:+44+7833+498336>
bill.fletcher(a)linaro.org<mailto:bill.fletcher@linaro.org> | Skype: billfletcher2020
On 8/18/2020 10:01 AM, Joakim Bech via TSC wrote:
> Hi,
>
> If there is enough time, then I would like to discuss OP-TEE release
> work, questions like: Who will make the release? When should it be done?
> Where should it be tracked? Currently, the answer to all of those are
> more or less "Linaro / Linaro decides", but our (Linaro's) impression is
> that we should try to get this transferred to TrustedFirmware in some
> way. Linaro will certainly be involved in that kind of work in the
> future also, but we believe that the directions should come from
> TrustedFirmware.org instead of Linaro. This might even be something to
> consider for all TF projects? I.e., not only OP-TEE? But again .. if
> time permits, otherwise we can push it to another call.
Thanks Joakim for bringing this up. I am interested in this topic.
If the proposal is to move the future direction role to TF.org, Would
like to understand how and if it will impact any decision making of the
OPTEE roadmap.
>
> A second topic is related to CHERI [1] and Hafnium. People working with
> the CHERI project asked me whether TrustedFirmware would be interested
> in an open-source CHERI adaptation of Hafnium? So I'd like to get the
> opinion from the TSC with regards to that. If the TSC is positive to it,
> then we have a few other things to consider like where it should go,
> separate CHERI branch(es), official tree with compile time flags? How to
> staff the activity? Legal aspects? Etc.
>
> [1] http://cheri-cpu.org/
>
> Regards,
> Joakim
>
>
> On Mon, 17 Aug 2020 at 15:55, Bill Fletcher via TSC
> <tsc(a)lists.trustedfirmware.org <mailto:tsc@lists.trustedfirmware.org>>
> wrote:
>
> Hi Dan
>
> I can give an update on the website rework.
>
> Regards
>
> Bill
>
> On Mon, 17 Aug 2020 at 12:47, Dan Handley via TSC
> <tsc(a)lists.trustedfirmware.org
> <mailto:tsc@lists.trustedfirmware.org>> wrote:
>
> Hi all____
>
> __ __
>
> I'll be chairing the TSC meeting this Thursday. Does anyone have
> any agenda topics for then?____
>
> __ __
>
> So far I have:____
>
> __ __
>
> * Continuation of Groups.io discussion____
>
> __ __
>
> * Continuation of GitHub/GitLab discussion____
>
> __ __
>
> Regards____
>
>
> Dan.____
>
> __ __
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org <mailto:TSC@lists.trustedfirmware.org>
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
>
>
> --
>
> Linaro <http://www.linaro.org/>
> *Bill Fletcher* | /Field Engineering/
> T: +44 7833 498336 <tel:+44+7833+498336>
> bill.fletcher(a)linaro.org <mailto:bill.fletcher@linaro.org> | Skype:
> billfletcher2020
>
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org <mailto:TSC@lists.trustedfirmware.org>
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
>
Hi,
If there is enough time, then I would like to discuss OP-TEE release work,
questions like: Who will make the release? When should it be done? Where
should it be tracked? Currently, the answer to all of those are more or
less "Linaro / Linaro decides", but our (Linaro's) impression is that we
should try to get this transferred to TrustedFirmware in some way. Linaro
will certainly be involved in that kind of work in the future also, but we
believe that the directions should come from TrustedFirmware.org instead of
Linaro. This might even be something to consider for all TF projects? I.e.,
not only OP-TEE? But again .. if time permits, otherwise we can push it to
another call.
A second topic is related to CHERI [1] and Hafnium. People working with the
CHERI project asked me whether TrustedFirmware would be interested in an
open-source CHERI adaptation of Hafnium? So I'd like to get the opinion
from the TSC with regards to that. If the TSC is positive to it, then we
have a few other things to consider like where it should go, separate CHERI
branch(es), official tree with compile time flags? How to staff the
activity? Legal aspects? Etc.
[1] http://cheri-cpu.org/
Regards,
Joakim
On Mon, 17 Aug 2020 at 15:55, Bill Fletcher via TSC <
tsc(a)lists.trustedfirmware.org> wrote:
> Hi Dan
>
> I can give an update on the website rework.
>
> Regards
>
> Bill
>
> On Mon, 17 Aug 2020 at 12:47, Dan Handley via TSC <
> tsc(a)lists.trustedfirmware.org> wrote:
>
>> Hi all
>>
>>
>>
>> I'll be chairing the TSC meeting this Thursday. Does anyone have any
>> agenda topics for then?
>>
>>
>>
>> So far I have:
>>
>>
>>
>> * Continuation of Groups.io discussion
>>
>>
>>
>> * Continuation of GitHub/GitLab discussion
>>
>>
>>
>> Regards
>>
>>
>> Dan.
>>
>>
>> --
>> TSC mailing list
>> TSC(a)lists.trustedfirmware.org
>> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>>
>
>
> --
>
> [image: Linaro] <http://www.linaro.org/>
> *Bill Fletcher* | *Field Engineering*
> T: +44 7833 498336 <+44+7833+498336>
> bill.fletcher(a)linaro.org | Skype: billfletcher2020
>
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
