Arm would like to nominate Tomas.
g.
On 20/02/2020 18:59, Nathalie Chan King Choy via Tsc wrote:
> Hi all,
>
> Tomas has been acting chair for the OpenAMP TSC. We have not formally
> voted in a TSC chair. Tomas is happy to continue, or pass the torch on
> to a new TSC chair.
>
> Please send your nominations to the list by March 5^th , 2020.
>
> Thanks & regards,
>
> Nathalie C. Chan King Choy
>
> Project Manager focused on Open Source & Community
>
>
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 all,
Tomas has been acting chair for the OpenAMP TSC. We have not formally voted in a TSC chair. Tomas is happy to continue, or pass the torch on to a new TSC chair.
Please send your nominations to the list by March 5th, 2020.
Thanks & regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
Hi all,
You can find the notes at: https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2020#20200220
If you attended, please check & update the notes if you spot any errors or important omissions.
Action Items
* Nathalie: Send out email to ask for TSC chair nominees
* Ed: Update push access to libmetal & libopenamp to just Ed & Arnaud
* Ed: Investigate OpenAMP GitHub ownership
* Nathalie: Ask Bill Fletcher about moving over GitHub repo for website to OpenAMP GitHub instead of OpenAMP Project
* Nathalie: Put MISRA & functional safety on agenda for next TSC call
* Bill Mills: write a couple paragraphs on what the policy should be around interface compatibility & send out for review to list
* Nathalie: schedule next TSC call over email
* Nathalie: Check ahead for quorum for next call
* All: Send suggestions for next TSC call agenda
Decisions
* Ed & Arnaud (open-amp & libmetal maintainers) will be the only ones with commit rights to those GitHub repos. Will continue to use GitHub PR flow for contributions. Ed & Arnaud should also submit PRs for what they commit.
* OpenAMP will adopt the Zephyr coding style guidelines
Thanks & regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
Hi all,
The agenda items I've collected are:
* Officially voting in a TSC chair
* Deciding which BUD20 F2F OpenAMP meetings need to be scheduled at a PST-friendly time for call-ins (these will be the last of the day in Budapest)
* TSC discussion topics for F2F at BUD20 so ppl can decide about travel
* Should it be TSC or individual work groups who decide & if TSC:
** Should we use GitHub issues for tracking bugs & upcoming work?
** Should we use GitHub Pull Requests or mailing list submissions for code contributions?
* Vote on if we should adopt the Zephyr guidelines for OpenAMP code
* Remaining time: Continue to go through Ed's list of governance items that need discussion
Thanks & regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
Sent: Tuesday, February 4, 2020 12:13 PM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org
Cc: nathalie-ckc(a)kestrel-omnitech.com; Arun Balaji Kannan; Ed T. Mooring; Vicky Janicki; Felix Burton; Bruce Ashfield; Koning, Maarten; Pratap Chandran; Michael May; Milea, Danut Gabriel (Danut); Loic PALLARDY; Hancock, Jeffrey; Raghuraman, Arvind; Wesley Skeffington; Bill Fletcher; Dannenberg, Andreas; Pierre-Yves Kerbrat
Subject: OpenAMP TSC - February call
When: Thursday, February 20, 2020 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Zoom
Hi all,
Please join on Zoom: https://zoom.us/my/openampproject
(If you need the meeting ID, it's 9031895760)
The notes from the previous call (Jan 17) can be found at https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2020#20200117
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source and Community
Hi all,
I’ve posted the notes from the TSC call to the OpenAMP wiki. Please let us know if you spot any errors or important omissions.:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2020
Action items:
* Non-Linaro members: Contact Nathalie, Tomas, or Vicky if you are not a Linaro member and need the OpenAMP discount code to attend Linaro Connect BUD20
* All: Review the Zephyr guidelines, for discussion next TSC all if we should adopt these for OpenAMP
https://docs.zephyrproject.org/latest/contribute/index.htmlhttps://docs.zephyrproject.org/latest/contribute/index.html#coding-style
* Ed: Check with Wendy if Xilinx had put OpenAMP through MISRA C checking in the past
Thanks & regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
Sent: Wednesday, January 8, 2020 6:19 PM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org; Glaropoulos, Ioannis
Cc: 肖翔; Tony McDowell; Ed T. Mooring; nathalie-ckc(a)kestrel-omnitech.com; Bruce Ashfield; Milea, Danut Gabriel (Danut); Clément Leger; mathieu.poirier(a)linaro.org; Raghuraman, Arvind; Mills, William; Wesley Skeffington; Loic PALLARDY; Tomas Evensen; Koning, Maarten; Grant Likely; Vicky Janicki; Michael May
Subject: OpenAMP TSC - January call
When: Friday, January 17, 2020 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Zoom
Happy New Year!
Please join the first OpenAMP TSC call of 2020 on Zoom: https://zoom.us/my/openampproject
(If you need the meeting ID, it’s 9031895760)
The notes from the previous call (Dec 12) can be found on the OpenAMP wiki at this link:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Dec12
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source and Community
Hi all,
Calling for agenda items for this Friday’s TSC call.
Here’s what I collected so far:
* Re-cap decisions from last TSC meeting for the wider audience
* Governance topics: (it’s a long list, we’ll start chipping away at it in this call)
* Development workflow
* Submitting patches & requirements
* Patch commit process
* Bug tracking
* New feature development
* Testing
* Documentation
* Code style guidelines
* Branching & tagging strategy
* Releases
* Coding standards
* Certification concerns
Thanks & regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
Sent: Wednesday, January 8, 2020 6:19 PM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org
Cc: 肖翔; Tony McDowell; Ed T. Mooring; nathalie-ckc(a)kestrel-omnitech.com; Bruce Ashfield; Milea, Danut Gabriel (Danut); Clément Leger; mathieu.poirier(a)linaro.org; Raghuraman, Arvind; Mills, William; Wesley Skeffington; Loic PALLARDY; Tomas Evensen; Koning, Maarten; Grant Likely; Vicky Janicki
Subject: OpenAMP TSC - January call
When: Friday, January 17, 2020 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Zoom
Happy New Year!
Please join the first OpenAMP TSC call of 2020 on Zoom: https://zoom.us/my/openampproject
(If you need the meeting ID, it’s 9031895760)
The notes from the previous call (Dec 12) can be found on the OpenAMP wiki at this link:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Dec12
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source and Community
Hi Arnaud,
Happy New Year!
Thanks. It will be a to-do item for this year to get the OpenAMP Project website cleaned up & pointing to the right things.
Until that gets set up, sending them to me & Tomas can be a start.
Best regards,
Nathalie
From: Tsc <tsc-bounces(a)lists.openampproject.org> On Behalf Of Arnaud POULIQUEN via Tsc
Sent: Friday, December 20, 2019 1:46 AM
To: Tsc(a)lists.openampproject.org
Subject: [OA-Tsc] OpenAMP contact for new member
EXTERNAL EMAIL
Hello,
Just a mail to mention that a contact information is probably missing in OpenAMP page<https://www.openampproject.org/about/>.
There is a contact link in the footer, but that points to the Linaro contact page.
What/who is the point of contact to get information and become a member?
Regards,
Arnaud
Hello,
Just a mail to mention that a contact information is probably missing in OpenAMP page<https://www.openampproject.org/about/>.
There is a contact link in the footer, but that points to the Linaro contact page.
What/who is the point of contact to get information and become a member?
Regards,
Arnaud
Hi all,
The Thursday TSC call will be an administrative one, so I'm cancelling the general invitation & will send a new invitation to the member representatives.
Thanks & regards,
Nathalie
Hi all,
Please send your suggestions for agenda items for next week's call. We'll have had a couple OpenAMP Board meetings since the last TSC call, so there will be governance topics that the Board will have deferred the decision to the TSC & we will cover those.
The notes from the previous call (Oct 17) can be found on the OpenAMP wiki at this link:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Oct17
Action items from the previous call:
* Tomas & Stefano: will lead the meetings for System DT sub-group
* Nathalie: Follow up with Steve so we don't clash with DT meetings
* Stefano: will lead the meetings for Hypervisor sub-group
* Tomas: will lead the meetings for TSC
* Loic: will send email to Matthieu about leading OpenAMP rpmessage, remoteproc sub-group & CC Tomas and Nathalie
* Matthieu: Lead 1st OpenAMP rpmessage, remoteproc sub-group call during next Thursday's 15:00 UTC slot
* Sub-group leaders: We have this timeslot once a week & groups can feel free to use it. If leader wants to reserve a slot, send Tomas & Nathalie email
* All: If you want to propose other topics for discussion, can update the relevant sub-group wiki page:
https://github.com/OpenAMP/open-amp/wiki#Future_topics
* Nathalie: Ask Linaro about Google Doc area for OpenAMP project
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source and Community
Hi all,
Nov 28 is US Thanksgiving, so cancelling this week's OpenAMP Thursday slot with so many of the participants out of office.
Best regards,
Nathalie
Hi All,
Attached are some short notes on some of the current issues. There may be couple of different implementations floating around, so issues may vary.
Regards
Suman
-----Original Appointment-----
From: Nathalie Chan King Choy [mailto:nathalie@xilinx.com]
Sent: Sunday, November 03, 2019 9:52 AM
To: Nathalie Chan King Choy; Anna, Suman; tsc(a)lists.openampproject.org; openamp-rp(a)lists.openampproject.org
Cc: Christian Daudt; Felix Burton; Michael May; nathalie-ckc(a)kestrel-omnitech.com; Manjukumar Harthikote Matha; Joe Fabbre; Raghuraman, Arvind; Vincent Chardon; Clément Leger; Tony McDowell; Bruce Ashfield; Grosen, Mark; mathieu.poirier(a)linaro.org; Wesley Skeffington; Ed T. Mooring; Mills, William; don.harbin(a)linaro.org
Subject: FW: OpenAMP weekly slot for TSC and sub-groups
When: Monday, November 25, 2019 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Zoom
Suman,
Welcome back!
Are you getting these meeting requests?
This one on Monday I want to talk about patch backlog. I think you should attend.
There appears to be pretty decent interest in the socket based interface.
You told me before that is has some warts. Can you write that up?
Are the limitations due to the current kernel implementation or inherent in the rpmsg protocol?
I expect there is some of both. Either way it would be good to get down in writing.
Thanks,
Bill
-----Original Appointment-----
From: Nathalie Chan King Choy [mailto:nathalie@xilinx.com]
Sent: Sunday, November 3, 2019 10:52 AM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org<mailto:tsc@lists.openampproject.org>; openamp-rp(a)lists.openampproject.org<mailto:openamp-rp@lists.openampproject.org>
Cc: Christian Daudt; Felix Burton; Michael May; nathalie-ckc(a)kestrel-omnitech.com<mailto:nathalie-ckc@kestrel-omnitech.com>; Manjukumar Harthikote Matha; Joe Fabbre; Raghuraman, Arvind; Vincent Chardon; Clément Leger; Tony McDowell; Bruce Ashfield; Grosen, Mark; mathieu.poirier(a)linaro.org<mailto:mathieu.poirier@linaro.org>; Wesley Skeffington; Ed T. Mooring; Mills, William; Don Harbin
Subject: OpenAMP weekly slot for TSC and sub-groups
When: Monday, November 25, 2019 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Zoom
https://zoom.us/j/4762224131
Hi all,
Due to travel for the OpenAMP Remoteproc discussion leads, we’re pushing this Thursday’s call out to Monday.
Notes from the meetings can be found on the GitHub wiki:
https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
<< File: ATT00001.txt >>
Hi OpenAMP TSC,
Maarten led our first call for the Higher-level (Application) Services sub-group of OpenAMP this week. I cleaned up my notes & posted them here: https://github.com/OpenAMP/open-amp/wiki/OpenAMP-Application-Services-Subgr…
If you were one of the speakers, please check for correctness & make updates as appropriate, or merge in your notes if I missed anything important.
Because app-services is likely to be a much smaller list of interested individuals compared to the TSC & some of the other sub-groups, please subscribe yourself if you are interested. Link below in the action items.
Action items
* All interested: Subscribe yourself to the app-services mailing list if you're interested in this topic (https://lists.openampproject.org/mailman/listinfo/app-services)
* Maarten: Send out the slides
* Maarten: Schedule next call for 1 month later, same timeslot, if it looks like there's enough activity to warrant a call.
* Loic: (give a little time for ppl to subscribe to the mailing list) Send pointer to example: small driver on top of rpmsg & very small piece of code.
* Bill & Etsam: (give a little time for ppl to subscribe to the mailing list) Continue discussion on list: virtio-net & socket layer
Thanks & regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
All,
Please subscribe to the openamp-rp mail list if you have not yet. We won't keep using this big To: and CC: list.
https://lists.openampproject.org/mailman/listinfo/openamp-rp
and all openamp lists here:
https://lists.openampproject.org/mailman/listinfo
As Nathalie says we will next meet on Monday 11/25.
The proposed agenda is:
1st 30 min:
Brainstrom on carried patches and if we should create a collective staging tree
2nd 30 min:
Discuss CI loop next steps
I created a page on my impressions from Manju's and Ed's work on a docker image
Thanks Guys, It is a very good start.
See:
https://github.com/OpenAMP/open-amp/wiki/Using-OpenAMP-CI
Thanks,
Bill
-----Original Appointment-----
From: Nathalie Chan King Choy [mailto:nathalie@xilinx.com]
Sent: Sunday, November 3, 2019 10:52 AM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org; openamp-rp(a)lists.openampproject.org
Cc: Christian Daudt; Felix Burton; Michael May; nathalie-ckc(a)kestrel-omnitech.com; Manjukumar Harthikote Matha; Joe Fabbre; Raghuraman, Arvind; Vincent Chardon; Clément Leger; Tony McDowell; Bruce Ashfield; Grosen, Mark; mathieu.poirier(a)linaro.org; Wesley Skeffington; Ed T. Mooring; Mills, William; Don Harbin
Subject: OpenAMP weekly slot for TSC and sub-groups
When: Monday, November 25, 2019 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Zoom
https://zoom.us/j/4762224131
Hi all,
Due to travel for the OpenAMP Remoteproc discussion leads, we're pushing this Thursday's call out to Monday.
Notes from the meetings can be found on the GitHub wiki:
https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
<< File: ATT00001.txt >>
https://zoom.us/j/4762224131
Hi all,
Due to travel for the OpenAMP Remoteproc discussion leads, we're pushing this Thursday's call out to Monday.
Notes from the meetings can be found on the GitHub wiki:
https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
Hi all,
Cancelling the Nov 14th call -> Maarten is planning for the OpenAMP higher level services sub-group call to be on Monday Nov 18th at 8am Pacific time. He would be sending that calendar invitation, as mentioned in his email to the TSC list earlier this week.
Best regards,
Nathalie
==========
https://zoom.us/j/4762224131
Hi all,
Hopefully the change to Standard Time in US/Canada won't cause too much chaos for you & your global meetings this week.
Here is a meeting series that runs until the end of 2019. (I will send out a January-onwards meeting series later.) The idea is that the sub-groups & TSC will share use of this timeslot and cycle through.
Notes from the meetings can be found on the GitHub wiki:
https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
Hi all,
You will shortly see an invite to a meeting for Monday Nov 18th 8am Pacific time to discuss topics to pursue within the OpenAMP higher-level application services group AKA “app-services”. Tomas, Nathalie and I chose this timeslot specifically for this one meeting due to temporary scheduling issues with the Thursday meetings. It might be a one-time meeting or we may simply choose to break out the app services to this timeslot if the interested parties prefer it.
The purpose of this meeting is to describe some potential areas to pursue, to identify interested parties and to gather high-level input. Since this is a one hour meeting, we won’t be able to go into deep technical detail on identified topics and we won’t be making any binding decisions. Thus, it won’t be a PowerPoint-fest – it will be more of an open discussion.
During the meeting, we will brainstorm on potential topics and discuss value and priority. To prime the pump on the sorts of topics we will discuss, here are a few we have identified already:
- file sharing
- proxy and/or forwarding of IP ports
- debug proxy
- high level IPC APIs for send-receive-reply / byte streams / message-based connections / pub/sub
- IPC server registration and client binding
- application partitioning using RPCs, C & non-C languages, canonical format
- bare metal APIs (using RPC) for stdio, socket IO, other APIs
I will go over these in the call.
Hope you can join,
Maarten
Ps. If you are interested in higher-level OpenAMP application services, you can subscribe to the app-services list here: https://lists.openampproject.org/mailman/listinfo/app-services
Canceling the series this time ;-)
Moved to the morning.
Adding tsc(a)lists.openampproject.com<mailto:tsc@lists.openampproject.com>
As discussed, moving to bi-weekly.
Join Zoom Meeting
https://zoom.us/j/4762224131<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F4762224131&sa=D&us…>
One tap mobile
+16465588656,,4762224131# US (New York)
+17207072699,,4762224131# US
Dial by your location
+1 646 558 8656 US (New York)
+1 720 707 2699 US
+1 888 788 0099 US Toll-free
+1 877 853 5247 US Toll-free
Meeting ID: 476 222 4131
Find your local number: https://zoom.us/u/acoazVTIVY<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fu%2FacoazVTIVY&sa=D&us…>
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
https://zoom.us/j/4762224131
Hi all,
Hopefully the change to Standard Time in US/Canada won't cause too much chaos for you & your global meetings this week.
Here is a meeting series that runs until the end of 2019. (I will send out a January-onwards meeting series later.) The idea is that the sub-groups & TSC will share use of this timeslot and cycle through.
Notes from the meetings can be found on the GitHub wiki:
https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi Kumar & all,
During today's System DT call, the proposal is to meet every 4 weeks. Since the DTE call that Steve runs at 9am Pacific Time is bi-weekly, we propose to use that slot when it's not being used by DTE.
Does that cause problems for anyone who plans to be an active participant in the System DT efforts? If it does, please speak up in the next few days.
Note: we will also have a system-dt mailing list, so the calls aren't the only way to participate. I will send out info about the mailing list in the next few days.
Thanks & regards,
Nathalie
-----Original Message-----
From: Tsc <tsc-bounces(a)lists.openampproject.org> On Behalf Of Nathalie Chan King Choy via Tsc
Sent: Wednesday, October 30, 2019 10:46 AM
Subject: Re: [OA-Tsc] System Device Tree OpenAMP sub-group call
EXTERNAL EMAIL
Hi Kumar and all,
> -----Original Message-----
> From: Kumar Gala <kumar.gala(a)linaro.org>
> Sent: Wednesday, October 30, 2019 3:03 AM
> Subject: Re: [OA-Tsc] System Device Tree OpenAMP sub-group call
>
> EXTERNAL EMAIL
>
> I know schedule is always difficult, the Zephyr project has had a standing dev
> meeting at the current time slot this meeting is at. So for one, I’d like to see if
> we can change the time slot.
I checked with Tomas, since he's co-ordinating the System DT sub-group:
He'd like to proceed with this Thursday's call at the 15:00 UTC time and
then we come up with future call options, factor in the Zephyr project dev
call, in order to get things going.
All:
To help us come up with good options for a future system-DT call recurring
slot, if there are other recurring project calls likely to affect a chunk
of system-DT call attendees, especially active participants, please send those
times (specify if weekly, bi-weekly, monthly).
Best regards,
Nathalie
>
> - k
>
> > On Oct 29, 2019, at 7:36 PM, Nathalie Chan King Choy via Tsc
> <tsc(a)lists.openampproject.org> wrote:
> >
> > https://zoom.us/j/4762224131
> >
> > Hi all,
> >
> > The next System Device Tree OpenAMP sub-group call will be this Thursday at
> 15:00 UTC. Although the OpenAMP TSC should already have a calendar invite
> for this slot as the standing weekly, I’m sending a separate calendar invitation
> because:
> > • We want to invite additional Device Tree people
> > • This is a test after some fiddling with OpenAMP TSC mailing list settings to
> see if I can get a calendar invitation to make it through
> >
> > A system-dt mailing list is in the works. I’m configuring & testing it this week.
> >
> > Initial proposed agenda:
> > • What works for a regular meeting slot and cadence?
> > • Interrupt handling
> > • Address mappings
> > Please let me know if you would like to propose additional topics.
> >
> > We now have a landing page for System Device Trees in the OpenAMP wiki:
> > https://github.com/OpenAMP/open-amp/wiki/System-Device-Trees
> >
> > Notes from the previous meetings can be found on the OpenAMP wiki:
> > https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
> >
> > Best regards,
> > Nathalie C. Chan King Choy
> > Project Manager focused on Open Source & Community
> >
> > This email and any attachments are intended for the sole use of the named
> recipient(s) and contain(s) confidential information that may be proprietary,
> privileged or copyrighted under applicable law. If you are not the intended
> recipient, do not read, copy, or forward this email message or any attachments.
> Delete this email message and any attachments immediately. <Mail
> Attachment.ics>--
> > Tsc mailing list
> > Tsc(a)lists.openampproject.org
> > https://lists.openampproject.org/mailman/listinfo/tsc
--
Tsc mailing list
Tsc(a)lists.openampproject.org
https://lists.openampproject.org/mailman/listinfo/tsc
I know schedule is always difficult, the Zephyr project has had a standing dev meeting at the current time slot this meeting is at. So for one, I’d like to see if we can change the time slot.
- k
> On Oct 29, 2019, at 7:36 PM, Nathalie Chan King Choy via Tsc <tsc(a)lists.openampproject.org> wrote:
>
> https://zoom.us/j/4762224131
>
> Hi all,
>
> The next System Device Tree OpenAMP sub-group call will be this Thursday at 15:00 UTC. Although the OpenAMP TSC should already have a calendar invite for this slot as the standing weekly, I’m sending a separate calendar invitation because:
> • We want to invite additional Device Tree people
> • This is a test after some fiddling with OpenAMP TSC mailing list settings to see if I can get a calendar invitation to make it through
>
> A system-dt mailing list is in the works. I’m configuring & testing it this week.
>
> Initial proposed agenda:
> • What works for a regular meeting slot and cadence?
> • Interrupt handling
> • Address mappings
> Please let me know if you would like to propose additional topics.
>
> We now have a landing page for System Device Trees in the OpenAMP wiki:
> https://github.com/OpenAMP/open-amp/wiki/System-Device-Trees
>
> Notes from the previous meetings can be found on the OpenAMP wiki:
> https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
>
> Best regards,
> Nathalie C. Chan King Choy
> Project Manager focused on Open Source & Community
>
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. <Mail Attachment.ics>--
> Tsc mailing list
> Tsc(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/tsc
https://zoom.us/j/4762224131
Hi all,
The next System Device Tree OpenAMP sub-group call will be this Thursday at 15:00 UTC. Although the OpenAMP TSC should already have a calendar invite for this slot as the standing weekly, I'm sending a separate calendar invitation because:
1. We want to invite additional Device Tree people
2. This is a test after some fiddling with OpenAMP TSC mailing list settings to see if I can get a calendar invitation to make it through
A system-dt mailing list is in the works. I'm configuring & testing it this week.
Initial proposed agenda:
* What works for a regular meeting slot and cadence?
* Interrupt handling
* Address mappings
Please let me know if you would like to propose additional topics.
We now have a landing page for System Device Trees in the OpenAMP wiki:
https://github.com/OpenAMP/open-amp/wiki/System-Device-Trees
Notes from the previous meetings can be found on the OpenAMP wiki:
https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes
Best regards,
Nathalie C. Chan King Choy
Project Manager focused on Open Source & Community
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
All,
Nathalie has set a very high bar for note taking!
https://github.com/OpenAMP/open-amp/wiki/OpenAMP-remoteproc-Subgroup-Meetin…
Here are the action items from today's call (on page as well)
* Topic owners to fill in their topics on the OpenAMP remoteproc future topics page
** Bill: Big data, Resiliency, Late attach, IPC only, Communal Linux repo, CI
** Loic: system resource mgmt
** Xilinx: Hardware description
** Etsam: Lifecycle mgmt, Protocol documentation
** Mark: Discuss with Kumar & post for RTOS side
* Maarten & Stefano: Let Nathalie know which sub-group is going next Thur at 15:00 UTC
* Manju/Ed to send mail to list when the "CI in Docker" work is ready for first looks (expected 11/1 ish)
X Nathalie to post this week's notes & Bill to fill in on wiki (done)
X Arnaud to publish example pull request to list (done, captured in notes)
Our next meeting will be in the same time slot on 11/7.
Thanks,
Bill
Looks like this got sent to tsc-bounces by accident
-----Original Message-----
From: Arnaud POULIQUEN <arnaud.pouliquen(a)st.com>
Sent: Thursday, October 24, 2019 9:02 AM
To: tsc-bounces(a)lists.openampproject.org
Subject: Zephyr OpenAMP sample relying on a resource table
Hi,
Here is the Pull request sent to Zephyr that proposes an OpenAMP sample answering to the Linux rpmsg sample client driver <https://elixir.bootlin.com/linux/latest/source/samples/rpmsg/rpmsg_client_s…> .
https://github.com/zephyrproject-rtos/zephyr/pull/16985 <https://github.com/zephyrproject-rtos/zephyr/pull/16985>
Regards
Arnaud
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
This Thursday's call (https://zoom.us/j/4762224131) will be the first of our OpenAMP work-group calls: "OpenAMP classic" - i.e. rpmessage, remoteproc, virtio, etc.
Agenda:
* Review the topics in the wiki list for OpenAMP classic and that were discussed at Connect SAN19 meeting. Rank the different topics and identify those that are applicable to Linux and/or OpenAMP.
** Notes from meeting at Connect SAN19: https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#20190926
** Old "future topics" list from before: https://github.com/OpenAMP/open-amp/wiki/Future-Topics-for-OpenAMP-classic-…
* Housekeeping details
** Decide what the group should be called (helps with consistent naming going forward)
** Get some volunteers for roles (e.g. note taker for future meetings of this work-group, champions/contributors/reviewers for specific topics)
** Decide if every 4 weeks cadence in this time slot works, or if more calls are needed
Please let me know if you have any additional suggestions for topics.
Thanks & regards,
Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Moved to Thursday mornings.
See separate invite.
Adding tsc(a)lists.openampproject.com<mailto:tsc@lists.openampproject.com>
As discussed, moving to bi-weekly.
Join Zoom Meeting
https://zoom.us/j/4762224131<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F4762224131&sa=D&us…>
One tap mobile
+16465588656,,4762224131# US (New York)
+17207072699,,4762224131# US
Dial by your location
+1 646 558 8656 US (New York)
+1 720 707 2699 US
+1 888 788 0099 US Toll-free
+1 877 853 5247 US Toll-free
Meeting ID: 476 222 4131
Find your local number: https://zoom.us/u/acoazVTIVY<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fu%2FacoazVTIVY&sa=D&us…>
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
I've posted the notes from yesterday's meeting. Please let us know if you spot any errors or important omissions.
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Oct17
Action items:
- Tomas & Stefano: will lead the meetings for System DT sub-group
- Nathalie: Follow up with Steve so we don't clash with DT meetings
- Stefano: will lead the meetings for Hypervisor sub-group
- Tomas: will lead the meetings for TSC
- Loic: will send email to Matthieu about leading OpenAMP rpmessage, remoteproc sub-group & CC Tomas and Nathalie
- Matthieu: Lead 1st OpenAMP rpmessage, remoteproc sub-group call during next Thursday's 15:00 UTC slot
- Sub-group leaders: We have this timeslot once a week & groups can feel free to use it. If leader wants to reserve a slot, send Tomas & Nathalie email
- All: If you want to propose other topics for discussion, can update the relevant sub-group wiki page:
https://github.com/OpenAMP/open-amp/wiki#Future_topics
- Nathalie: Ask Linaro about Google Doc area for OpenAMP project
Have a great weekend!
-Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
As stated in the previous OpenAMP meeting, we encountered a
limitation with remoteproc resource table. Indeed, all resources
are encoded using 32 bits fields whereas the memory accessible
on our processor is above the 32 bits boundary.
For instance, when the physical address is 0x1_0000_0000, then
this PA can't be inserted in the resource table or it will be
truncated to 0. This can temporarily be workarounded by using
device tree dma-ranges (at least on Linux) to have a correct DA
but the PA will still be truncated. Moreover, this only work
if you can remap the 64 bits memory zone to a 32 bits one (this
almost implies to have an IOMMU in front of the device).
Since 64 bits systems are now pretty common, it seems clear that
we need to modify the resource table to support 64 bits addresses.
In the same time, it will also be necessary to use 64 bits storage
for virtio device features. Some of them already need more than
32 bits (virtio-net features for instance).
Both modifications requires to handle versionning in the resource
table.
The following suggestions are mainly a RFC ! Please feel free
to comment any of the proposed modifications.
Versionning
-----------
Currently, the supported version is "1".
I propose to increment this number (version 2 ?) which will allow
to add necessary evolutions for 64 bits support. This version
should probably support both old format and new 64 bits support
(comments are welcomed).
64 bits addresses
-----------------
Since most of the systems are now using 64bits addresses, it is
necessary to support such configuration
There are various problems which occurs when modifying these fields
- Retro compatibility (We probably must keep it)
- Fields alignment (Some architecture might not handle misalignment)
- 32 bit remote vs 64 bits master
Regarding the retrocompatibility, it appears clear that modifiying
existing resources is probably not feasible due to missing
reserved fields. It will probably be necessary to create a
secondary type of resources which are almost the same as the 32bits
one. For instance for a vdev, we will have the "classic" rsc flavor:
struct fw_rsc_carveout {
u32 da;
u32 pa;
u32 len;
u32 flags;
u32 reserved;
u8 name[32];
} __packed;
And the 64 bits one:
struct fw_rsc_carveout_64 {
u64 da;
u64 pa;
u32 len;
u32 flags;
u32 reserved;
u8 name[32];
} __packed;
This does not seems really ideal and adds a lot of duplication but
I do not have (yet) any better idea (again, comments are welcomed !).
However, what should we do with the other fields ? Let them on 32
bits or change them all to use 64 bits ? If keeping some of them on
32bits, this can lead to misaligned members (since they are packed,
the compiler will force the alignment). Since some architecture do
not support that well, it's probably better to ensure all fields
will be aligned on their natural type boundary. it also means that
all structures sizes must be a multiple of 8 bytes.
If we don't want to guarantee alignment, then I do not have yet
a clear picture of what it would involve on various drivers which
accesses the memory of the resource table (rproc, virtio for the
config space, etc) and what are their assumptions about that.
If this can be accepted, then the question of the 64 bits master
versus the 32 bits remote can be addressed. I think this is probably
orthogonal to the fact we can have 64 bits addresses in the resource
table. Indeed, if both PA and DA are stored using 64 bits, then,
there is no limitation on what can be done on theses addresses.
For instance, on Linux Kernel, the device tree can allow remapping
64 bits to 32 bits using dma-ranges.
Features
--------
In virtio, the set of features is a bitfield of 64 bits. The current
virtio-rproc implementation only allows for 32bits features. This
is already limiting since virtio-net needs more than 32 bits
(VIRTIO_NET_F_STANDBY and VIRTIO_NET_F_SPEED_DUPLEX).
So these fields (gfeatures, etc) will also need to be udated to 64
bits variants. It might also be a good idea to keep in mind that
future evolutions will probably extend the available features.
Comments are welcomed !
Regards,
Clément Léger
Hi all,
Here is the proposed agenda for this upcoming OpenAMP TSC meeting.
Please let Tomas & me know if you have any additional topics.
1. Close on owner to drive each of the sub-groups
* OpenAMP: rpmessage & remoteproc, big buffers --> Bill & Loic had action item to find owner
* Higher level services: Proxy, eRPC, WindRiver islet --> Do we have interest from NXP or Wind River to be owner?
* Standardizing hyper calls, hypervisor interfaces --> Stefano volunteered
* System DT --> Tomas volunteered if no one else wants to take it
1. Decide on order for cycling sub-groups (i), (ii), (iii), and TSC meetings through this timeslot. (System DT calls will be in a different slot, because also inviting the DT people)
*New time!* 15:00 UTC (8am PDT, 11am EDT, 4pm BST, 5pm CEST)
https://zoom.us/j/4762224131
Notes from the previous TSC call: https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Oct10
Best regards,
Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
I've posted the notes and action items here from today's call: https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Oct10
Most notable is change to the meeting schedule to a standing weekly slot with subgroups rotating through. See the notes for details.
Next meeting will be next Thur Oct 17th at a new time -> 15:00 UTC (8am PDT, 11am EDT, 4pm BST, 5pm CEST) and will be TSC to close on owners of the subgroups
i. OpenAMP: rpmessage & remoteproc, big buffers
ii. Higher level services: Proxy, eRPC, WindRiver islet
iii. Standardizing hyper calls, hypervisor interfaces
iv. System DT (invite also the DT people)
so that those subgroups can then begin diving in.
If you have additional agenda items for next week, please send them to Tomas & me.
Thanks & regards,
Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Adding tsc(a)lists.openampproject.com<mailto:tsc@lists.openampproject.com>
As discussed, moving to bi-weekly.
Join Zoom Meeting
https://zoom.us/j/4762224131<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F4762224131&sa=D&us…>
One tap mobile
+16465588656,,4762224131# US (New York)
+17207072699,,4762224131# US
Dial by your location
+1 646 558 8656 US (New York)
+1 720 707 2699 US
+1 888 788 0099 US Toll-free
+1 877 853 5247 US Toll-free
Meeting ID: 476 222 4131
Find your local number: https://zoom.us/u/acoazVTIVY<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fu%2FacoazVTIVY&sa=D&us…>
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Adding tsc(a)lists.openampproject.com<mailto:tsc@lists.openampproject.com>
As discussed, moving to bi-weekly.
Join Zoom Meeting
https://zoom.us/j/4762224131<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F4762224131&sa=D&us…>
One tap mobile
+16465588656,,4762224131# US (New York)
+17207072699,,4762224131# US
Dial by your location
+1 646 558 8656 US (New York)
+1 720 707 2699 US
+1 888 788 0099 US Toll-free
+1 877 853 5247 US Toll-free
Meeting ID: 476 222 4131
Find your local number: https://zoom.us/u/acoazVTIVY<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fu%2FacoazVTIVY&sa=D&us…>
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
Here is the proposed agenda for this upcoming OpenAMP TSC meeting. Please let Tomas & me know if you have any additional topics.
1. TSC, Board & subgroups meeting scheduling
2. Starting up the subgroups & determining who will drive each
* OpenAMP: rpmessage & remoteproc, big buffers
* Higher level services: Proxy, eRPC, WindRiver islet
* Standardizing hyper calls, hypervisor interfaces
* System DT (invite also the DT people)
1. Interim release process until we have the working group going for remoteproc, rpmessage
Tomas plans to send an updated calendar invitation using the new OpenAMP TSC email list. The Zoom info for the meeting is below just in case... Tomas' email will be the first test of sending a calendar invitation through our new list...
If you wish to be removed from the list or know someone who wants to join the list, you can use this page (https://lists.openampproject.org/mailman/listinfo/tsc) or let me know.
Reminder: the notes from the previous meetings can be found at https://github.com/OpenAMP/open-amp/wiki/Meeting-Notes .
Best regards,
Nathalie
Join Zoom Meeting at 12pm PDT on Thur 10 Oct 2019
https://zoom.us/j/4762224131
One tap mobile
+16465588656,,4762224131# US (New York)
+17207072699,,4762224131# US
Dial by your location
+1 646 558 8656 US (New York)
+1 720 707 2699 US
+1 888 788 0099 US Toll-free
+1 877 853 5247 US Toll-free
Meeting ID: 476 222 4131
Find your local number: https://zoom.us/u/acoazVTIVY
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
I've posted the notes from Thursday's OpenAMP TSC meeting/call during Linaro Connect SAN19 to the OpenAMP wiki:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#20190926
Action items are summarized at the end.
Please let me know if you spot any errors or important omissions.
Thanks & regards,
Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
I hope all the mailing list issues are now sorted out. Linaro IT & I were doing some tests this morning. This list contains everyone who got the bi-weekly OpenAMP call invitation. If you wish to be removed, then please email me directly.
This Thursday's OpenAMP sessions have now been added the public Connect schedule, if you are on-site & using that to organize your week. I've pasted the Zoom links to both below if you are calling in.
9:00-10:30am PDT - "DTE Discussions: System Device Tree Discussion (Bayview Room)"
https://zoom.us/j/617455510
12:15-2:00pm PDT - "OpenAMP TSC Meeting (Sunset 1)"
https://zoom.us/j/4762224131
Best regards,
Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Hi all,
As discussed last week, please find below a list of evolutions for OpenAMP and/or Linux kernel we can discuss next week during SAN19.
Regards,
Loic
Secure coprocessor support:
Add a generic rproc driver to support secure and isolated coprocessor thanks to some trusted services based on OPTEE or other Trusted OS.
Standard flow will be to load coprocessor firmware and its associated signature somewhere in secure/non-secure shared memory and then to request secure world to load, authenticate coprocessor image and then start coprocessor
Some tasks:
- Define a standard file format for firmware to authenticate (is ELF still relevant or should we rely on PKCS11 header like to integrate signature ?)
- Define TA API to control secure coprocessor (load, start, stop...)
- How to manage resource table in that case? Should we rely on some secure services or should we consider it as input for communication link (aka rpmsg) configuration between coprocessor and Linux kernel (and in that case could stay non-secure)
- ...
Improve Coprocessor debug capabilities
Today rproc framework offers access to a virtual trace file (circular buffer filed by coprocessor) which limit coprocessor debug capabilities.
Tracks to explore:
- How to store coprocessor traces in a log file (syslog like) to improve trace depth?
- How to get same timestamp between Linux and coprocessors to correlate trace
- How to control coprocessor debug infrastructure (coresight?)
- Is it possible to debug coprocessor firmware thanks to GDB/GDB server over rpmsg or mailbox?
Improve coprocessor reliability/recovery
Review remoteproc recovery procedure to be more scalable to product configuration
- Decorrelate recovery and core dump generation
- Create client (user space and kernel space) notification
- Be able to delay coprocessor restart after ack from all clients
- Silent coprocessor restart preserving resources and communication channels
Silent main processor reboot
- Don't reload coprocessor firmware
- Resynchronize Virtio and RPMSG communication link
- Notify main processor crash to coprocessor...
Generic Cortex-M33 support
- How to load firmware for new ARMv8-M coprocessor? One or two binary images?
- Could it be a generic driver?
Coprocessor 64bit support
- Ongoing elf 64bit support (almost OK)
- Missing 64bit resource table support --> need rsc table versioning
Rpmsg over virtio
Virtio_rpmsg is based on dma_coherent for buffer allocation. In the other hand, virtio vrings are allocated by rproc driver and not by virtio ring.
This is leading to an inconsistent situation where virtio is not aware of the way vrings and buffers are allocated and so consider them as "kernel memory" accessible via sg list and not dma_coherent one.
Virtio owns one flag named IOMMU allowing to allocate and handle dma_coherent memories.
Virtio_rpmsg and virtio_ring memory management should be realigned to work correctly on any CPU architectures (32 and 64bit)
System resource management via SCMI
- How coprocessor could access system resource? Could SCMI protocol be used on the top of rpmsg?
Rproc/rpmsg test farm
- How to test rproc and rpmsg feature set?
- How to check compatibility with OpenAMP bare metal/real time OS rpmsg implementation ?
Next features coming from ST
- RPMSG over UART serdev
- Virtual I2C over RPMSG
- Virtual SPI over RPMSG
Hi OpenAMP TSC,
This is the first message to our new TSC mailing list for the OpenAMP community project! It contains everyone who got the bi-weekly OpenAMP call invitation. If you wish to be removed, then please email me directly.
If you had the previous wiki page bookmarked for the notes, please update your bookmark to https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019 . I changed it from the generic "Meeting Note 2019" title because now we also have meeting notes for the System DT calls (the first was Wed Sep 11) posted on the OpenAMP wiki, since it's the OpenAMP community project driving the System DT effort.
More shiny new things: we did a final round of feedback on the logo proposals from the graphic designer, and attached are the files for our project logo!
Our next call will be a combo face-to-face/call happening at Linaro Connect SAN19 from 12:15pm-2pm Pacific time on Thur Sept 26. The slightly later time is to give people a chance to grab their lunch, as this is the conference lunch period.
The System DT face-to-face/call at Connect will be 9:00-10:30am on Thur Sept 26.
Notes from this week's call:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2019#2019Sept12
Have a wonderful weekend,
Nathalie
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.