User Tools

Site Tools


agl-sat-meetings

AGL System Architecture Team (SAT) Meetings

Meetings of the System Architecture Team are held every other Thursday at 13:00 UTC. The upcoming schedule can be found below.

Conference Information:

AGL-SAT Biweekly Meeting

Join Zoom Meeting
https://zoom.us/j/443971577

Meeting ID: 443 971 577

Find your local number: https://zoom.us/u/ameRude4a


July 2, 2020

Attendees: Walt, Jan-Simon

  • DRM Lease RFQ - SPEC-3388
  • Fast Boot RFQ - SPEC-3371 -Reviewed the updated version that is uploaded in the Jira ticket. Added review comments in the ticket.
  • Toyota Update - No update. Will be providing an update to the Steering Committee and AB. Will review the proposal with the SAT on the July 17 SAT/EG meeting.
  • Reference Hardware was received in Yokohama. Will shipped out next week to members who requested it.
    • Board documentation can be found on the RHSA EG group page
    • Scott commented that the documentation is insufficient without schematics for the boards.
    • Walt will request the schematics from Panasonic,
    • 7/2 -Reviewed the disclaimer in the RHSA manuals.

New Business:

  • DRM Lease RFQ will be sent out to mail list and the responses reviewed by the IC EG.
  • Sound System RFQ review. Nishiguchi-san will create a JIRA ticket for the review. Would like George to take part in the review. Will ask George to participate in the July 17 SAT/EG meeting and added a time slot for the review.

June 18, 2020

Attendees: Walt, Jan-Simon

  • DRM Lease RFQ - SPEC-3388
  • Fast Boot RFQ - SPEC-3371 - Kusakabe-san not available today. Haraki-san reported that he spoke to Kusakabe-san and he will update the RFQ document for the next meeting. He will add the M2 as an alternative device as well as address the concerns from the last review.
  • Toyota Update - No update. Will be providing an update to the Steering Committee and AB.
  • Reference Hardware was received in Yokohama. Will shipped out next week to members who requested it.
    • Board documentation can be found on the RHSA EG group page
    • Scott commented that the documentation is insufficient without schematics for the boards.
    • Walt will request the schematics from Panasonic,

New Business:

  • DRM Lease RFQ will be sent out to mail list and the responses reviewed by the IC EG.

June 4, 2020

Attendees: Walt, Jan-Simon, Yamaguchi, Michael, Kurokawa, Hosokawa, Nomoto, Scott, Hanaoka, Sekine, Tanikawa, Haraki,

  • Virtual AMM CFP closes on Friday.

May 28, 2020

Attendees: Walt, Jan-Simon, Scott, Kusakabe, Kurokawa, Daniel, Hosokawa, Joel Catala, Jesus Cabrera, Nishiguchi, Haraki, Bernd Niedermeier, Anusha,

Special meeting to review IC EG RFQs

  • DRM Lease RFQ - SPEC-3388
  • Fast Boot RFQ - SPEC-3371

May 21, 2020

Attendees: Walt, Haraki, Scott, Sekine, Kurokawa, Nomoto, Tanikawa

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .
  • Yocto version discussion
    • Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release.
    • SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release.
      • JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July)
      • KK - YP 3.1 + 4.14 kernel
      • LL - YP 3.1 + 5.4 kernel.
      • MM - YP 3.1 + 5.4 Kernel
    • Yamaguchi-san asked about support for Ubuntu 20.4. Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1. Jan-Simon will check with YP on their plans for 20.4 support.
  • 4/23 - Plan to merge next with dunfell (YP 3.1) to master. Scott has built all platforms except Renesas.
    • YP 3.1 was released April 21 (Tuesday)
    • Noted an issue with using the QEMU image on Intel hardware that needs to be addressed.
    • QEMU runs fine
    • H3 and BBE do not work in CI.
    • Jan-Simon notes that H3 would boot to kernel with old version of the BSP by adding Ronan's patches in gerrit plus another one. Would need to skip H3 from test suite until official patch comes out from Renesas. Could leave it in CI and only run boot test.
    • BBE fails uboot so it needs to be updated by Sanclound. Will need to be skipped in CI
    • Target from Renesas is May 18 for the starter kit BSP update.
    • Ubuntu 20.4 releases today and Fedora 32 is coming out soon, We expect that the next point release of 3.1 will include support for both of them.
    • Proposal is to merge next to master next week.
  • 5/5 - Merge to master is complete. Work is ongoing for RCar H3 BSP. Will be pushed to their GitHub end of next week.
    • 5/21 - Merge complete. Looking pretty good. Yocto accepting patches upstream and about two start a two week cycle for merging updates. Schedule for point releases is still under discussion. 3.1.1 current plan is to release July. Will stick to point releases only for master and our release branches.
  • Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG
    • Kusakabe-san will post the document for further review.
    • Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call.
    • 4/23 - Revised version was delayed due to coronavirus issues at Denso-Ten. Should be ready for the next meeting.
    • 5/5 - Updated version was posted to the SC, but not generally to the community. We will release the document to the community and review it at the next SAT call.
    • 5/21 - Document posted to SPEC-3371. Added comments in the Jira ticket during the call. IC EG needs to review with Kusakabe-san,
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
  • 5/5 - PO went out last week, Delivery expected end of May
  • 5/21- Still expecting hardware at the end of May. will be shipped to Yokohama LF office and then sent to companies that have requested it. Software delivery from Panasonic will not be downloadable, but provided on media. Expected deliverable will be patches against the Renesas BSP.
  • Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
    • 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting,
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
    • 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.latest status
    • Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.
    • 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.
    • 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in Confluence.
    • 4/23 - Ohiwa-san reviewed the use cases that he added to SPEC-3322. Questions about the specifics of the use cases.
      • Positioning - What is the difference between what agl-service-gps and the Toyota code that was dropped and what benefits are there to changing to it? AGL is using open source components that are well maintained upstream.
      • Communication - What is difference between agl-service-can-low-level and Toyota's communication component and what benefits do we derive from switching the Toyota component?
      • Tanikawa-san - Is there a statement of what the purpose of the code drop is? What is Toyota's expectation and vision for contributing this code? How are we going to use this code?
      • Additional questions can be added to the Confluence Q&A page
    • 5/5 - Presentation is being prepared to address the questions asked at the last meeting and should be ready in early June.
      • Ohiwa-san showed a comparison of the Toyota code with the AGL positioning and low CAN service and concluded that there is no large gap between the what AGL has and the Toyota code.
    • 5/22 - Nothing to report. Ohiwa-san out sick.
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.
    • 4/26 - Dr. Yamaguchi provided an update on the ELISA AGL cooperation proposal.
    • 5/5 - Preparing for the ELISA virtual workshop later this month. There is a new automotive working group that will be kicked off during the workshop.
    • 5/22 - ELISA workshop was held this week. Slides from presentations are still be updated. Dr. Y will provide further updates during the next SAT meeting. Automotive WG was kicked off and is working out their charter. Dr. Y will propose to the AGL AB that Walt participate in the ELISA Automotive WG by attending their meetings and reporting back to the SAT and SC on their progress.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • 3/26 - Multiple issues blocking getting FOSSology server going,
  • 4/23 - 9.0.1 run and results sent to Li. 360,000 files that need to be cleared if we look at the entire code base including the kernel. Li asked if we can limit it to just the AGL created code which would limit it to 2000ish files.
  • 5/5 - Li started reviewing the QEMU results today and should be finished this week.
  • 5/22 - Review is ongoing. Open question of what to with packages that were not reviewed. Only AGL developed packages are currently being reviewed.

New Business:

  • Kurokawa-san completed the first draft of the DRM sharing RFQ. Will put in a JIRA ticket and we will schedule a separate SAT call for next Thursday to review since we anticipate the next regular SAT call to be busy with the new Toyota proposal. Will also see if we can get Kusakabe-san on the call to discuss the fast boot RFQ.

May 7, 2020

Attendees: Walt, Jan-Simon, Scott, Li, Michael, Andrey, Mikhail, Leonid, Sebastien, Hosokawa, Ohiwa, Nishiguchi, Dr, Yamaguchi, Mr, K, Haraki,

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .
  • Yocto version discussion
    • Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release.
    • SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release.
      • JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July)
      • KK - YP 3.1 + 4.14 kernel
      • LL - YP 3.1 + 5.4 kernel.
      • MM - YP 3.1 + 5.4 Kernel
    • Yamaguchi-san asked about support for Ubuntu 20.4. Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1. Jan-Simon will check with YP on their plans for 20.4 support.
  • 4/23 - Plan to merge next with dunfell (YP 3.1) to master. Scott has built all platforms except Renesas.
    • YP 3.1 was released April 21 (Tuesday)
    • Noted an issue with using the QEMU image on Intel hardware that needs to be addressed.
    • QEMU runs fine
    • H3 and BBE do not work in CI.
    • Jan-Simon notes that H3 would boot to kernel with old version of the BSP by adding Ronan's patches in gerrit plus another one. Would need to skip H3 from test suite until official patch comes out from Renesas. Could leave it in CI and only run boot test.
    • BBE fails uboot so it needs to be updated by Sanclound. Will need to be skipped in CI
    • Target from Renesas is May 18 for the starter kit BSP update.
    • Ubuntu 20.4 releases today and Fedora 32 is coming out soon, We expect that the next point release of 3.1 will include support for both of them.
    • Proposal is to merge next to master next week.
  • 5/5 - Merge to master is complete. Work is ongoing for RCar H3 BSP. Will be pushed to their GitHub end of next week. .
  • Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG
    • Kusakabe-san will post the document for further review.
    • Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call.
    • 4/23 - Revised version was delayed due to coronavirus issues at Denso-Ten. Should be ready for the next meeting.
    • 5/5 - Updated version was posted to the SC, but not generally to the community. We will release the document to the community and review it at the next SAT call.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
    • 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions.
    • 5/5 - PO went out last week, Delivery expected end of May
  • Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
    • 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting,
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
    • 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.latest status
    • Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.
    • 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.
    • 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in Confluence.
    • 4/23 - Ohiwa-san reviewed the use cases that he added to SPEC-3322. Questions about the specifics of the use cases.
      • Positioning - What is the difference between what agl-service-gps and the Toyota code that was dropped and what benefits are there to changing to it? AGL is using open source components that are well maintained upstream.
      • Communication - What is difference between agl-service-can-low-level and Toyota's communication component and what benefits do we derive from switching the Toyota component?
      • Tanikawa-san - Is there a statement of what the purpose of the code drop is? What is Toyota's expectation and vision for contributing this code? How are we going to use this code?
      • Additional questions can be added to the Confluence Q&A page
    • 5/5 - Presentation is being prepared to address the questions asked at the last meeting and should be ready in early June.
      • Ohiwa-san showed a comparison of the Toyota code with the AGL positioning and low CAN service and concluded that there is no large gap between the what AGL has and the Toyota code.
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.
    • 4/26 - Dr. Yamaguchi provided an update on the ELISA AGL cooperation proposal.
    • 5/5 - Preparing for the ELISA virtual workshop later this month. There is a new automotive working group that will be kicked off during the workshop.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • 3/26 - Multiple issues blocking getting FOSSology server going,
  • 4/23 - 9.0.1 run and results sent to Li. 360,000 files that need to be cleared if we look at the entire code base including the kernel. Li asked if we can limit it to just the AGL created code which would limit it to 2000ish files.
  • 5/5 - Li started reviewing the QEMU results today and should be finished this week.

New Business:

  • New AGL service binder proposal for cloud proxy. See SPEC-3351

April 23, 2020

Attendees: Walt, Jan-Simon, Scott, Yamaguchi, Kurokawa, Abe, Tanikawa, Haraki, Ohiwa

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .
  • Yocto version discussion
    • Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release.
    • SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release.
      • JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July)
      • KK - YP 3.1 + 4.14 kernel
      • LL - YP 3.1 + 5.4 kernel.
      • MM - YP 3.1 + 5.4 Kernel
    • Yamaguchi-san asked about support for Ubuntu 20.4. Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1. Jan-Simon will check with YP on their plans for 20.4 support.
  • 4/23 - Plan to merge next with dunfell (YP 3.1) to master. Scott has built all platforms except Renesas.
    • YP 3.1 was released April 21 (Tuesday)
    • Noted an issue with using the QEMU image on Intel hardware that needs to be addressed.
    • QEMU runs fine
    • H3 and BBE do not work in CI.
    • Jan-Simon notes that H3 would boot to kernel with old version of the BSP by adding Ronan's patches in gerrit plus another one. Would need to skip H3 from test suite until official patch comes out from Renesas. Could leave it in CI and only run boot test.
    • BBE fails uboot so it needs to be updated by Sanclound. Will need to be skipped in CI
    • Target from Renesas is May 18 for the starter kit BSP update.
    • Ubuntu 20.4 releases today and Fedora 32 is coming out soon, We expect that the next point release of 3.1 will include support for both of them.
    • Proposal is to merge next to master next week.
  • Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG
    • Kusakabe-san will post the document for further review.
    • Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call.
    • 4/23 - Revised version was delayed due to coronavirus issues at Denso-Ten. Should be ready for the next meeting.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
    • 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions.
  • Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
    • 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting,
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
    • 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.latest status
    • Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.
    • 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.
    • 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in Confluence.
    • 4/23 - Ohiwa-san reviewed the use cases that he added to SPEC-3322. Questions about the specifics of the use cases.
      • Positioning - What is the difference between what agl-service-gps and the Toyota code that was dropped and what benefits are there to changing to it? AGL is using open source components that are well maintained upstream.
      • Communication - What is difference between agl-service-can-low-level and Toyota's communication component and what benefits do we derive from switching the Toyota component?
      • Tanikawa-san - Is there a statement of what the purpose of the code drop is? What is Toyota's expectation and vision for contributing this code? How are we going to use this code?
      • Additional questions can be added to the Confluence Q&A page
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.
    • 3/26 - Dr. Yamaguchi provided an update on the ELISA AGL cooperation proposal.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • 3/26 - Multiple issues blocking getting FOSSology server going,
  • 4/23 - 9.0.1 run and results sent to Li. 360,000 files that need to be cleared if we look at the entire code base including the kernel. Li asked if we can limit it to just the AGL created code which would limit it to 2000ish files.

New Business:

April 9, 2020

Attendees: Walt, Jan-Simon, Michael, Stephane, Kusakabe, Kurokawa, Yamaguchi, Haraki, Hosokawa, Tanikawa, Nomoto, Abe, Ohiwa, Scott,

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .
  • Yocto version discussion
    • Renesas plans to use 4.14 kernel for dunfell this year and would upgrade to 5.4 for the LL release.
    • SAT agreed on the following plan for YP versioning + Renesas BSP kernel version. Other platforms will support 5.4 kernel at initial release.
      • JJ - YP 3.1 + 4.14 kernel (best case end of June to IoT.bzh with release in July)
      • KK - YP 3.1 + 4.14 kernel
      • LL - YP 3.1 + 5.4 kernel.
      • MM - YP 3.1 + 5.4 Kernel
    • Yamaguchi-san asked about support for Ubuntu 20.4. Probably has not been tested. Ubuntu release is 1 day before the YP release so it is unlikely to be explicitly support on day 1. Jan-Simon will check with YP on their plans for 20.4 support.
  • Reviewed the Fast Boot RFQ developed by Kusakabe-san for the IC EG
    • Kusakabe-san will post the document for further review.
    • Plenty of comments were provided. Another round of updates will take place and a new version will be available in two weeks (Kusakabe-san to confirm the timing) for the next SAT call.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
    • 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions.
  • Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
    • 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting,
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
    • 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.latest status
    • Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.
    • 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.
    • 4/9 - SPEC-3322 written with details on the code that was uploaded to gerrit including build instructions and other documentation in Confluence.
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.
    • 3/26 - Dr. Yamaguchi provided an update on the ELISA AGL cooperation proposal.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • 3/26 - Multiple issues blocking getting FOSSology server going,

New Business:

March 26, 2020

Attendees: Walt, Jan-Simon, Scott, Dr. Yamaguchi, Ohiwa, Nomoto, Abe, Kusakabe, Haraki, Hosokawa, Stephane, Parth, Nishiguchi, Tanikawa

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .

SPEC-2538 - Remove support for multiple versions of widgets to be installed simultaneously.

  • 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions,
  • 3/26 - Merged.
  • Icefish final release
    • Done
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
    • 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions.
  • Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
    • 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting,
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
    • 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.latest status
    • Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.
    • 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions.
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.
    • 3/26 - Dr. Yamaguchi provided an update on the ELISA AGL cooperation proposal.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • 3/26 - Multiple issues blocking getting FOSSology server going,

New Business:

  • SPEC-3295 - Apply yocto metadata license file format to AGL layers.
  • New repository requests for POI (SPEC-3291 and SPEC-3293)

March 12, 2020

Attendees: Walt, Jan-Simon, Scott, Stephane, Li, Ohiwa, Kusakabe, Kurokawa, Tanikawa, Haraki, Abe, Hosokawa, Dr. Yamaguchi, Nomoto

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .

SPEC-2538 - Remove support for multiple versions of widgets to be installed simultaneously.

  • 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions,
  • Icefish final release
    • Being slowed down by issues with CI.
    • Waiting for a fix from Igalia on the WAM issue reported by Scott on Tuesday (SPEC-3181).
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
  • Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.
    • 9/26
      • Radio API review
      • Sample API of Denso Ten released in staging/documents
      • Goal is to refine the radio api with additional functions found in the review of above
      • focus on generic calls over hw specifics
      • Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
      • Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
    • 10/10
    • 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.
    • 11/21 - No update.
    • 12/4 - No update. Further translations from Denso Ten may be available at the end of December.
    • 12/19 - No update
    • 1/16 - No update. Scott will start looking at it now that he is done with CES. SPEC-1903 - IoT.bzh will provide a POC for the radio API.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
    • 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.latest status
    • Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG.
  • Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.
    • 11/7 - More discussion needed before Navi EG is ready to present the new architecture.
    • 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware.
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.

New Business:

  • Walt to send out info on the CIP / EILSA webinar scheduled for tomorrow,
  • Fujitsu wants to buy an i.MX8 board for testing, Scott recommended the NXP i.Mx8 EVKB

February 13, 2020

Attendees: Walt, Jan-Simon, Li, Scott, Jose, Sebastien, Kusakabe, Dr. Yamaguchi, Hosokawa, Michael, Jeremy, Kurokawa, Ronan, Sekine, Ohiwa, Guy

  • 2020 Roadmap Review
    • Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list. To be reviewed at SAT F2F at the AMM.
    • Each EG need to update Roadmap .

SPEC-2538 - Remove support for multiple versions of widgets to be installed simultaneously.

  • 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions,
  • Icefish final release
    • Being slowed down by issues with CI.
    • Waiting for a fix from Igalia on the WAM issue reported by Scott on Tuesday (SPEC-3181).
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
  • Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.
    • 9/26
      • Radio API review
      • Sample API of Denso Ten released in staging/documents
      • Goal is to refine the radio api with additional functions found in the review of above
      • focus on generic calls over hw specifics
      • Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
      • Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
    • 10/10
    • 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.
    • 11/21 - No update.
    • 12/4 - No update. Further translations from Denso Ten may be available at the end of December.
    • 12/19 - No update
    • 1/16 - No update. Scott will start looking at it now that he is done with CES. SPEC-1903 - IoT.bzh will provide a POC for the radio API.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
  • Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.
    • 11/7 - More discussion needed before Navi EG is ready to present the new architecture.
    • 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware.
  • FOSDEM
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.

New Business:

  • SPEC-3097 - SOTA Issues (Ronan)
    • Fixed, but SOTA is not built or tested in CI. Feature was broken for an unknown length of time. Ronan asked if we could set up periodic SOTA build. Jan-Simon suggested adding patches to CI management scripts.

January 16, 2020

Attendees: Walt, Dr. Yamaguchi, Kusakabe, Scott, Stephane, Michael

SPEC-2538 - Remove support for multiple versions of widgets to be installed simultaneously.

  • Window manager update from Daniel
  • Icefish RC3 decisions
    • Will release this week.
    • Waiting on the last changes from Daniel and Scott for window manager. Window manager is being rescheduled for January and will have to be in a point release of Itchy Icefish.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
    • 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely.
  • Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.
    • 9/26
      • Radio API review
      • Sample API of Denso Ten released in staging/documents
      • Goal is to refine the radio api with additional functions found in the review of above
      • focus on generic calls over hw specifics
      • Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
      • Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
    • 10/10
    • 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.
    • 11/21 - No update.
    • 12/4 - No update. Further translations from Denso Ten may be available at the end of December.
    • 12/19 - No update
    • 1/16 - No update. Scott will start looking at it now that he is done with CES. SPEC-1903 - IoT.bzh will provide a POC for the radio API.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
    • 1/16 - Added LTS to the SC agenda for February.
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
    • 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0.
  • Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.
    • 11/7 - More discussion needed before Navi EG is ready to present the new architecture.
    • 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware.
  • FOSDEM
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.

New Business:

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • Future meeting scheduling
    • Block scheduling of meetings to consolidate the schedule
    • Japanese members attending the call are ok with this meetings at this time.
    • Might be better one or two hours earlier than currently (Hosokawa)
    • Will bring up at the SC meeting next week. Also post a question on the mail list (maybe create a poll)

Tanibata: Merge Graphics and UI with Instrument Cluster EG starting next year. Schedule for a more EU/Japan joint friendly time. Would like feedback from Haraki-san on this proposal. Tanibata-san will meet with Haraki-san today to discuss. One idea is for meetings to be held at 5:00 pm JST (which is 9 am CET, 2 am Chicago time) Developer call. Can try to hold two sessions per week. One at the current time on Tuesday and a second session at 6 pm Chicago time/ 9 am JST.

January 2, 2020

Meeting Cancelled

December 19, 2019

Attendees: Walt, Jan-Simon, Scott, Stephane, Ohiwa, Kurokawa, Yamaguchi, Fulup, Guy, Li, Sekine, Takada, Nishiguchi, Haraki, Juhyun Doh, Cristoph Stoidner, Fulup, Vincent, George, Sebastien

  • Window manager update from Daniel
  • Icefish RC3 decisions
    • Will release this week.
    • Waiting on the last changes from Daniel and Scott for window manager. Window manager is being rescheduled for January and will have to be in a point release of Itchy Icefish.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
    • 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP.
    • Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic.
  • Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.
    • 9/26
      • Radio API review
      • Sample API of Denso Ten released in staging/documents
      • Goal is to refine the radio api with additional functions found in the review of above
      • focus on generic calls over hw specifics
      • Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
      • Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
    • 10/10
    • 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.
    • 11/21 - No update.
    • 12/4 - No update. Further translations from Denso Ten may be available at the end of December.
    • 12/19 - No update
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
    • 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://confluence.automotivelinux.org/display/TC/Documents
  • Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.
    • 11/7 - More discussion needed before Navi EG is ready to present the new architecture.
    • 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware.
  • FOSDEM
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.

New Business:

FOSSology/ License Review

  • So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work. Will be brought up to AB at their next meeting.
  • Open Chain reported that we have 320 different licenses. How do we plan to collaborate with OpenChain?
  • Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year.
  • Future meeting scheduling
    • Block scheduling of meetings to consolidate the schedule
    • Japanese members attending the call are ok with this meetings at this time.
    • Might be better one or two hours earlier than currently (Hosokawa)
    • Will bring up at the SC meeting next week. Also post a question on the mail list (maybe create a poll)

Tanibata: Merge Graphics and UI with Instrument Cluster EG starting next year. Schedule for a more EU/Japan joint friendly time. Would like feedback from Haraki-san on this proposal. Tanibata-san will meet with Haraki-san today to discuss. One idea is for meetings to be held at 5:00 pm JST (which is 9 am CET, 2 am Chicago time) Developer call. Can try to hold two sessions per week. One at the current time on Tuesday and a second session at 6 pm Chicago time/ 9 am JST.

December 5, 2019

Attendees: Walt, Jan-Simon, Michael, Edi, Stephane, Sebastian, George, Nick, Jasim Quazi, Jeremy Puhlman, Guy, Julian, Ohiwa, Dr. Yamaguchi, Kurokawa, Kusakabe, Nishiguchi, Scott, Sekine

  • Window manager update from Daniel
  • Icefish RC2 decisions
    • Token logic. Edi tested and no regressions noted. WE will include the token logic in the RC2
    • Waiting on one last patch from George. Will take Jacobo's changes and one liner from Scott for low CAN.
    • Waiting on the last changes from Daniel and Scott for window manager. Really need to get this into RC2 today. Guy will check with Daniel.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
    • 12/4 - Block diagram uploaded to the wiki page. Will be reviewed at the steering committee on Monday/Tuesday.
  • Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.
    • 9/26
      • Radio API review
      • Sample API of Denso Ten released in staging/documents
      • Goal is to refine the radio api with additional functions found in the review of above
      • focus on generic calls over hw specifics
      • Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
      • Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
    • 10/10
    • 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.
    • 11/21 - No update.
    • 12/4 - No update. Further translations from Denso Ten may be available at the end of December.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
    • 12/5 - Following up next week.
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
    • 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.
      • Discussion on whether the existing AGL data persistence binder can be reused/ extended.
      • Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash).
      • Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.
  • Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.
    • 11/7 - More discussion needed before Navi EG is ready to present the new architecture.
    • 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware.
  • FOSDEM
    • FOSDEM stand accepted. Deadline for embedded devroom talk submissions is Dec 6.
    • Will put together a sign up for staffing the stand at FOSDEM
    • Deadline for AMM CFP is Dec 6
  • ELISA updates
    • ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found here
    • ELISA groups.io page can be found here
    • New ELISA development process subgroup has formed. See their groups.io page for more information and to sign up.

New Business:

  • Future meeting scheduling
    • Block scheduling of meetings to consolidate the schedule
    • Japanese members attending the call are ok with this meetings at this time.
    • Might be better one or two hours earlier than currently (Hosokawa)
    • Will bring up at the SC meeting next week. Also post a question on the mail list (maybe create a poll)

November 21, 2019

Attendees: Walt, Jan-Simon, Sebastien, Guy, Michael, Stephane, Nick, Hosokawa, Haraki, Kurokawa, Sekine, Ohiwa, Kusakabe, Nishiguchi, Dr. Yamaguchi,

  • Daniel getting window manager into Gerrit for Karlsruhe next week.
  • SPEC-2927 - Window Manager for WAM
  • RHSA RFQ - updated the RFQ document with comments. The revised version is here.
    • 8/29 Panasonic is reviewing
    • 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco.
    • 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon.
    • 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG.
    • 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week.
    • 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP. Also will get a quote for creating the BSP from Konsulko.
  • Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September.
    • 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week.
    • 9/26
      • Radio API review
      • Sample API of Denso Ten released in staging/documents
      • Goal is to refine the radio api with additional functions found in the review of above
      • focus on generic calls over hw specifics
      • Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
      • Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
    • 10/10
    • 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API.
    • 11/21 - No update.
  • LTS
    • 9/26 (Berlin F2F)

* AI: identify base services. What is in core-image-minimal that is available in all profiles.

  • 'core' LTS vs. IVI or Cluster LTS
    • depends on changes required e.g. by IC
  • 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.
    • There were a number of talks last week in Lyon about using a combination of Debian/Fedora/CentOS for user space and Yocto for BSPs for LTS in embedded projects.
    • 11/21 - SC did not get to this topic, Will be addressed at December meeting.
  • Toyota Code Drop
    • 10/10
      • No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion.
      • Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
    • 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC.
    • 11/21 -
    • Notes from SC meeting
    • Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure.
    • Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see Confluence for more on the documents.
  • Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call.
    • 11/7 - More discussion needed before Navi EG is ready to present the new architecture.
    • 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware.

New Business:

  • FOSDEM stand accepted. Deadline for embedded devroom talk submissions is Dec 6.
agl-sat-meetings.txt · Last modified: 2020/07/02 13:58 by wminer