October 2019 - Tsc - lists.openampproject.org

Re: [OA-Tsc] System Device Tree OpenAMP sub-group call

by Nathalie Chan King Choy

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

5 years, 1 month

2
3
0 0

Re: [OA-Tsc] System Device Tree OpenAMP sub-group call

by Kumar Gala

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

5 years, 1 month

2
1
0 0

System Device Tree OpenAMP sub-group call

by Nathalie Chan King Choy

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.

5 years, 1 month

1
0
0 0

OpenAMP remoteproc meeting Notes, 2019-10-24

by Mills, William

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

5 years, 1 month

1
0
0 0

FW: Zephyr OpenAMP sample relying on a resource table

by Nathalie Chan King Choy

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.

5 years, 1 month

1
0
0 0

Agenda: "OpenAMP classic" work-group call - Thur Oct 24 at 15:00 UTC

by Nathalie Chan King Choy

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.

5 years, 1 month

1
0
0 0

Canceled: OpenAMP Bi-Weekly Meeting

by Tomas Evensen

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.

5 years, 2 months

1
0
0 0

2019-10-17 OpenAMP TSC meeting notes

by Nathalie Chan King Choy

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.

5 years, 2 months

1
0
0 0

[OpenAMP] Resource table and 64 bits addresses/fields

by Clément Leger

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

5 years, 2 months

1
0
0 0

OpenAMP TSC Meeting 10/17/19 (New time!)

by Nathalie Chan King Choy

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.

5 years, 2 months

1
0
0 0

2024

2023

2022

2021

2020

2019

Tsc October 2019