All,
Do we have any suggested topics for Monday April 4?
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Everyone in the to: list,
Are you all free today at 3PM UTC (11 AM US East)?
Oliver,
See the DTE home page for a description of the meeting, the Zoom link
and a google ics file.
However I just added you to the invite going forward. Just delete after
we are done if you do not want to continue.
The meeting is tied to UK time so right now appears 1 hour later than
normal as US has done DST and the UK will not until next week.
Thanks,
Bill
On 3/7/22 11:00 AM, Olivier Masse wrote:
> Hi Bill,
>
> Could you send us some pointers to join your call ?
>
> Sorry for this late request.
>
> Olivier
>
> On mar., 2022-02-22 at 15:00 -0500, Bill Mills wrote:
>> Caution: EXT Email
>>
>> Oliver,
>>
>> On 2/22/22 7:36 AM, Olivier Masse wrote:
>>> Hi All,
>>>
>>> Could we postpone to the next call ?
>>>
>>
>> Yes we can discuss on March 7.
>>
>> However I think you need to define what you want to discuss.
>>
>> First of, there is nothing in your suggested DTS that tells Linux (or
>> other OS) that it should not map the memory area. It looks to me as
>> you should include the "no-map" property in your node.
>>
>> How will the Linux video/graphics drivers refer to this node? I
>> presume
>> by phandle, right?
>>
>> Are you setting any suggested naming convention for the node name
>> (after
>> you fix the node name to include @address)?
>>
>> You are defining a compatible string in the node. The current
>> suggestion is not in the spec. It could be "optee,sdp" if you get
>> optee
>> stakeholders to agree. What should be the definition of "optee,sdp".
>> I presume it means secure data path but that could mean a ton of
>> things.
>> Will sdp always mean DRM protected media playback or could it include
>> more?
>>
>> Thanks,
>> Bill
>>
>>> BR / Olivier
>>>
>>> On mar., 2022-02-15 at 13:46 -0600, Rob Herring wrote:
>>>> Caution: EXT Email
>>>>
>>>> On Fri, Feb 11, 2022 at 8:21 AM Bill Mills <bill.mills(a)linaro.org
>>>>>
>>>> wrote:
>>>>>
>>>>> Rob,
>>>>>
>>>>> Can you confirm for the DT call on Feb 21?
>>>>
>>>> I'm on holiday on the 21st.
>>>>
>>>>>
>>>>> Oliver,
>>>>>
>>>>> On 2/11/22 4:54 AM, Olivier Masse wrote:
>>>>>> Hi Bill,
>>>>>>
>>>>>> NXP had a discussion with Linaro about this optee os issue:
>>>>>>
>>>
>>>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
>>>>>>
>>>>>> Which is implemented by this first draft here:
>>>>>>
>>>
>>>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
>>>>>>
>>>>>> Could we be part of the next Device Tree call to discuss
>>>>>> about
>>>>>> adding
>>>>>> a reserved memory in optee os embedded DT ?
>>>>>>
>>>>>
>>>>> Thanks for bringing it up.
>>>>> I have skimmed the PR threads and the discussion seems to be:
>>>>> 1) OP-TEE internal issues
>>>>> 2) DT standards questions and issues
>>>>>
>>>>> For the DT call we need to focus on #2 above.
>>>>> We will definitely need Rob for this discussion so we need to
>>>>> do it
>>>>> when
>>>>> he can join. (If we don't resolve the question in this email
>>>>> thread
>>>>> before then.)
>>>>>
>>>>> Context for all:
>>>>>
>>>>> SDP here is related to DRM protected playback of media streams.
>>>>>
>>>>> Jens comment in PR:
>>>>> > So far we have managed to avoid defining our own bindings
>>>>> in OP-
>>>>> TEE,
>>>>> > instead we've been able to reuse already established
>>>>> bindings.
>>>>> With
>>>>> > this you're proposing something new. I'm not sure of the
>>>>> best
>>>>> way of
>>>>> > doing such a thing. Are we sure there is nothing to reuse?
>>>>> > If not: How should it be reviewed? Who should review it?
>>>>>
>>>>> DTS in PR:
>>>>> /*
>>>>> * Copyright (c) 2021, NXP. All rights reserved.
>>>>> *
>>>>> * SPDX-License-Identifier: BSD-3-Clause
>>>>> */
>>>>>
>>>>> /dts-v1/;
>>>>>
>>>>> / {
>>>>> #address-cells = <1>;
>>>>> #size-cells = <0>;
>>>>>
>>>>> reserved-memory {
>>>>> #address-cells = <1>;
>>>>> #size-cells = <1>;
>>>>>
>>>>> sdp_mem {
>>>>> compatible = "optee-sdp";
>>>>> reg = <0x3E800000 0x00400000>;
>>>>> };
>>>>> };
>>>>> };
>>>>>
>>>>> However it was modified after that.
>>>>>
>>>>> Oliver: please reply to this thread (on list please) with the
>>>>> final
>>>>> DTS
>>>>> you are proposing. fix DT conventions and what are you doing
>>>>> with
>>>>> the
>>>>> no-map property if anything.
>>>>>
>>>>> Is the memory above meant to be visible to NS world AND S
>>>>> world? Or is
>>>>> just for secure world.
>>>>>
>>>>> Thanks,
>>>>> Bill
>>>>>
>>>>>> Best regards,
>>>>>> Olivier Masse
>>>>>
>>>>> --
>>>>> Bill Mills
>>>>> Principal Technical Consultant, Linaro
>>>>> +1-240-643-0836
>>>>> TZ: US Eastern
>>>>> Work Schedule: Tues/Wed/Thur
>>>>> _______________________________________________
>>>>> boot-architecture mailing list --
>>>>> boot-architecture(a)lists.linaro.org
>>>>> To unsubscribe send an email to
>>>>> boot-architecture-leave(a)lists.linaro.org
>>
>> --
>> Bill Mills
>> Principal Technical Consultant, Linaro
>> +1-240-643-0836
>> TZ: US Eastern
>> Work Schedule: Tues/Wed/Thur
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Hi all,
Normally this isn't the right place for job postings, but in this case it is directly relevant to EBBR and Arm's SystemReady program. Arm is looking to backfill my position with someone who can be responsible for the SystemReady IR program long term direction. If an of you are interested, or can think of someone who would be a good candidate, then please pass this link on to them.
Thanks,
g.
https://experienced-arm.icims.com/jobs/5461/director---technical-lead/job?m…
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi everyone,
It has been many weeks since the last EBBR biweekly, so even though I don’t have much of an agenda, I will hold the call today in a little under an hour. If we don’t have enough to fill an hour then it can just be a short call.
Dial in details are below
Agenda:
- EBBR maintainership
- Restricting console on secure boot
- other business
—-
Join Zoom Meeting
Date: 14 Mar 2022
Time: 15:00 GMT
https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09
Meeting ID: 920 8136 5511<tel:8136%205511> Password: 490324
One tap mobile+14086380968<tel:+14086380968>,,92081365511#,,#,490324# US (San Jose) +16465189805<tel:+16465189805>,,92081365511#,,#,490324# US (New York)
—-
Grant Likely
Senior Technical Director, Arm
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
All,
We will have the Devicetree call today.
As normal it is at 15 UTC / 10 AM US Eastern.
(One hour from when I send this.)
Today we have several topics:
* a specific reserved memory use for OP-TEE
* a general discussion of memory and the spec.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Hi all,
I’m cancelling this weeks EBBR biweekly as I wasn’t able to send out a reminder and agenda last week. Next meeting is 14th March 2022.
As always, email me if you have a topic for the agenda.
g.
—-
Grant Likely
Senior Technical Director, Arm
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Oliver,
On 2/22/22 7:36 AM, Olivier Masse wrote:
> Hi All,
>
> Could we postpone to the next call ?
>
Yes we can discuss on March 7.
However I think you need to define what you want to discuss.
First of, there is nothing in your suggested DTS that tells Linux (or
other OS) that it should not map the memory area. It looks to me as
you should include the "no-map" property in your node.
How will the Linux video/graphics drivers refer to this node? I presume
by phandle, right?
Are you setting any suggested naming convention for the node name (after
you fix the node name to include @address)?
You are defining a compatible string in the node. The current
suggestion is not in the spec. It could be "optee,sdp" if you get optee
stakeholders to agree. What should be the definition of "optee,sdp".
I presume it means secure data path but that could mean a ton of things.
Will sdp always mean DRM protected media playback or could it include more?
Thanks,
Bill
> BR / Olivier
>
> On mar., 2022-02-15 at 13:46 -0600, Rob Herring wrote:
>> Caution: EXT Email
>>
>> On Fri, Feb 11, 2022 at 8:21 AM Bill Mills <bill.mills(a)linaro.org>
>> wrote:
>>>
>>> Rob,
>>>
>>> Can you confirm for the DT call on Feb 21?
>>
>> I'm on holiday on the 21st.
>>
>>>
>>> Oliver,
>>>
>>> On 2/11/22 4:54 AM, Olivier Masse wrote:
>>>> Hi Bill,
>>>>
>>>> NXP had a discussion with Linaro about this optee os issue:
>>>>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
>>>>
>>>> Which is implemented by this first draft here:
>>>>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…
>>>>
>>>> Could we be part of the next Device Tree call to discuss about
>>>> adding
>>>> a reserved memory in optee os embedded DT ?
>>>>
>>>
>>> Thanks for bringing it up.
>>> I have skimmed the PR threads and the discussion seems to be:
>>> 1) OP-TEE internal issues
>>> 2) DT standards questions and issues
>>>
>>> For the DT call we need to focus on #2 above.
>>> We will definitely need Rob for this discussion so we need to do it
>>> when
>>> he can join. (If we don't resolve the question in this email
>>> thread
>>> before then.)
>>>
>>> Context for all:
>>>
>>> SDP here is related to DRM protected playback of media streams.
>>>
>>> Jens comment in PR:
>>> > So far we have managed to avoid defining our own bindings in OP-
>>> TEE,
>>> > instead we've been able to reuse already established bindings.
>>> With
>>> > this you're proposing something new. I'm not sure of the best
>>> way of
>>> > doing such a thing. Are we sure there is nothing to reuse?
>>> > If not: How should it be reviewed? Who should review it?
>>>
>>> DTS in PR:
>>> /*
>>> * Copyright (c) 2021, NXP. All rights reserved.
>>> *
>>> * SPDX-License-Identifier: BSD-3-Clause
>>> */
>>>
>>> /dts-v1/;
>>>
>>> / {
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>>
>>> reserved-memory {
>>> #address-cells = <1>;
>>> #size-cells = <1>;
>>>
>>> sdp_mem {
>>> compatible = "optee-sdp";
>>> reg = <0x3E800000 0x00400000>;
>>> };
>>> };
>>> };
>>>
>>> However it was modified after that.
>>>
>>> Oliver: please reply to this thread (on list please) with the final
>>> DTS
>>> you are proposing. fix DT conventions and what are you doing with
>>> the
>>> no-map property if anything.
>>>
>>> Is the memory above meant to be visible to NS world AND S
>>> world? Or is
>>> just for secure world.
>>>
>>> Thanks,
>>> Bill
>>>
>>>> Best regards,
>>>> Olivier Masse
>>>
>>> --
>>> Bill Mills
>>> Principal Technical Consultant, Linaro
>>> +1-240-643-0836
>>> TZ: US Eastern
>>> Work Schedule: Tues/Wed/Thur
>>> _______________________________________________
>>> boot-architecture mailing list --
>>> boot-architecture(a)lists.linaro.org
>>> To unsubscribe send an email to
>>> boot-architecture-leave(a)lists.linaro.org
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
All,
There will be no DT meeting tomorrow Monday Feb 21.
It is a holiday in the US and others have declined as well.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Rob,
Can you confirm for the DT call on Feb 21?
Oliver,
On 2/11/22 4:54 AM, Olivier Masse wrote:
> Hi Bill,
>
> NXP had a discussion with Linaro about this optee os issue:
> https://github.com/OP-TEE/optee_os/issues/5133
>
> Which is implemented by this first draft here:
> https://github.com/OP-TEE/optee_os/pull/5149
>
> Could we be part of the next Device Tree call to discuss about adding
> a reserved memory in optee os embedded DT ?
>
Thanks for bringing it up.
I have skimmed the PR threads and the discussion seems to be:
1) OP-TEE internal issues
2) DT standards questions and issues
For the DT call we need to focus on #2 above.
We will definitely need Rob for this discussion so we need to do it when
he can join. (If we don't resolve the question in this email thread
before then.)
Context for all:
SDP here is related to DRM protected playback of media streams.
Jens comment in PR:
> So far we have managed to avoid defining our own bindings in OP-TEE,
> instead we've been able to reuse already established bindings. With
> this you're proposing something new. I'm not sure of the best way of
> doing such a thing. Are we sure there is nothing to reuse?
> If not: How should it be reviewed? Who should review it?
DTS in PR:
/*
* Copyright (c) 2021, NXP. All rights reserved.
*
* SPDX-License-Identifier: BSD-3-Clause
*/
/dts-v1/;
/ {
#address-cells = <1>;
#size-cells = <0>;
reserved-memory {
#address-cells = <1>;
#size-cells = <1>;
sdp_mem {
compatible = "optee-sdp";
reg = <0x3E800000 0x00400000>;
};
};
};
However it was modified after that.
Oliver: please reply to this thread (on list please) with the final DTS
you are proposing. fix DT conventions and what are you doing with the
no-map property if anything.
Is the memory above meant to be visible to NS world AND S world? Or is
just for secure world.
Thanks,
Bill
> Best regards,
> Olivier Masse
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
All,
I have no agenda for tomorrow's DT call. Does anyone want to bring up
something?
If I have not heard anything by noon UTC tomorrow (3 hours before the
meeting) I will cancel the call.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
