Versions Compared

Version Old Version 2 New Version Current
Changes made by

Jerry, Zhao Jiancong

Walt Miner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2
minLevel2

Jan 21,

...

2025

Attendees:

Agenda: 

  • Topic 1: VirtIO-loopback RFC

    • Michele Paolinopresented closing activities for phase3

      View file
      namevirtio-loopback-recap-rfc-2025-01-20.pdf

  • Topic 2: Unified HMI Application Discussion

  • Topic 2: Unified HMI GRPC I/F

    • Jira Legacy
      serverSystem Jira
      serverId28dd2583-f97f-3492-8dcd-520f3459580a
      keySPEC-5280

View file
nameAGL_official_demo_withUHMI.pptx

Minutes

Key Discussion Points

  • Introductions and Updates:

    • New attendees introduced themselves, including Mujdat Soyturk from Marmara University, who shared insights about his research lab's focus on connected cars, V2X communication, and software-defined vehicles.

  • Unified HMI and GRPC Integration:

    • Unified HMI Capabilities:

      • Static application layers across multiple displays.

      • Mirroring applications on multiple displays.

      • Current support for Wayland Ivi-shell; GRPC integration is in progress.

    • Demo Scenarios:

      • Two proposed demo scenarios:

        1. Switching between multiple layout patterns using buttons.

        2. Dynamically launching applications on selected displays.

      • GRPC integration is critical for advanced demos.

    • Development Needs:

      • GRPC integration for AGL compositor is a priority.

      • Additional application development and interface work required for demos.

  • GRPC and Wayland Ivi-Shell Discussion:

    • Marius Vlad raised questions about whether to fully migrate to GRPC or maintain compatibility with Wayland Ivi-shell.

    • Consensus: GRPC integration is the priority, but Wayland Ivi-shell support should remain for flexibility.

    • Marius requested a state diagram to better understand the architecture and interactions between components like ULA, ULA Node, and Unified HMI.

  • Application Development:

    • Panasonic will provide navigation and turn-by-turn applications.

    • Additional development (e.g., buttons for layout switching) will require collaboration with AGL developers.

  • Demo Preparation Timeline:

    • The proposed demos are not targeted for Embedded World due to time constraints.

    • Focus will be on preparing for the next AGL All Member Meeting (AMM) in Berlin.

  • RFC and Community Feedback:

    • Michele Paolino provided updates on the RFC for loopback features:

      • Security concerns raised by the community have been addressed.

      • Next steps include pushing updates to the AGL repository and continuing discussions with the community.

  • Miscellaneous:

    • Discussion on hardware requirements for demos (e.g., number of boards and outputs).

    • Marius Vlad highlighted the need to reuse existing code for GRPC integration to save time.

...

Action Items

  1. Kenta Murakami (PAS):

    • Upload slides to the conference page and attach

...

    • the state diagram to the Jira ticket for GRPC integration.

    • Provide additional details or clarifications on Unified HMI architecture as requested by Marius Vlad.

  2. Marius Vlad:

    • Continue prototyping GRPC integration and provide feedback on missing information or challenges.

  3. Walt Miner:

    • Finalize the schedule for upcoming events and ensure alignment on demo preparation timelines.

  4. Michele Paolino (VOSYS):

    • Push updates to the AGL repository regarding loopback RFC and security improvements.

  5. All Participants:

    • Prepare for the next AGL All Member Meeting in Berlin, with a focus on showcasing Unified HMI demos.

Feb 04, 2025

Attendees:

Agenda: 

  • Topic 1: Unified HMI GRPC I/F

    • Jira Legacy
      serverSystem Jira
      serverId28dd2583-f97f-3492-8dcd-520f3459580a
      keySPEC-5280

  • Topic 2: VirtIO-loopback RFC

    • Michele Paolinopresented closing activities for phase3

      View file
      namevirtio-loopback-recap-rfc-2025-01-20.pdf

Minutes

Key Discussion Points:

  1. Architecture and Development Updates:

    • Kenta Murakami presented a revised architecture slide, proposing that the "Unified HMI Window Manager" may not be necessary due to gRPC compatibility with Go language.

    • Marius Vlad emphasized the need for a test component (AGL IVI Window Manager) to validate API connections and simulate demo requirements. This component is temporary and intended for testing purposes only.

    • The team discussed the importance of a testbed to validate data exchange between ULA Node and the compositor before finalizing implementation in the shell.

  2. Demo and Benchmarking:

    • The current demo setup uses KVM to run Zephyr and containers for Linux-based applications.

    • A proposal was made to explore dual architecture:

      • One using Xen Hypervisor.

      • Another using KVM and non-hypervisor solutions.

    • The goal is to maintain a unified interface while supporting different backend implementations.

  3. Xen Hypervisor Considerations:

    • Xen Hypervisor is seen as a strong candidate for production environments, especially in automotive use cases.

    • Challenges with Xen include limited support for graphics output (e.g., Virtio GPU).

    • Collaboration with ARM, Linaro, and Renesas was suggested to leverage existing work on Xen Hypervisor.

  4. AMM (Automotive Grade Linux All Member Meeting) Preparation:

    • Michele Paolino's session is currently on the waiting list. Walt Miner will review the schedule and confirm availability.

    • Michele was asked to prepare slides summarizing achievements for potential inclusion in the keynote or STVG session.

    • Discussions at AMM will focus on the future direction of hypervisor and non-hypervisor solutions.

  5. Future Work and Action Items:

    • The team discussed the possibility of a dual architecture approach:

      • Hypervisor-based solution using Xen.

      • Non-hypervisor solution using containers and KVM.

    • The importance of balancing committee member interests and technical feasibility was highlighted.

    • The need to address the graphics output limitations of Xen Hypervisor was noted.

...

Action Items:

  • Michele Paolino:

    • Prepare slides summarizing achievements for AMM and share them with Jerry.

    • Include options for dual architecture (Xen and KVM) in the presentation.

  • Marius Vlad:

    • Update the architecture diagram to clarify the testing and implementation process.

    • Continue working on the AGL IBI Window Manager as a testbed for validating API connections.

  • Jerry (PAS_趙健淙):

    • Coordinate discussions on Xen Hypervisor and KVM at AMM, including potential collaboration with ARM, Linaro, and Renesas.

  • Walt Miner:

    • Confirm Michele's session status for AMM and finalize the schedule.

  • All Members:

    • Continue discussions on dual architecture (Xen and KVM) and finalize the approach for Phase 4.

    • Prepare for in-depth discussions at the AMM regarding the future direction of hypervisor and non-hypervisor solutions.

Feb 18, 2025

Attendees:

Minutes

Key Discussion Point

  • AMD Embedded Boards:

    • Yuichi Kusakabe raised questions about AMD embedded evaluation boards and their compatibility with open-source communities.

    • Walt Miner mentioned discussing this with AMD at the upcoming Embedded World event.

  • Jira Ticket Review:

    • Participants reviewed open Jira tickets and discussed their statuses.

    • Some tickets were marked as resolved or inactive due to lack of ongoing work.

    • Permissions for resolving tickets were identified as an issue for some attendees, which Walt Miner will address.

  • Unified Topics and AMM (All Members Meeting):

    • Discussions on unified usage topics and their inclusion in the AMM agenda.

    • Jerry suggested skipping certain topics during the face-to-face workshop due to Murakami-san's absence.

  • Bluetooth Contributions:

    • Jerry highlighted the potential for contributions to Bluetooth profiles (e.g., HFP, messaging) in AGL (Automotive Grade Linux).

    • This would enhance AGL's capabilities and showcase its features to customers.

  • SDV Reference Platform:

    • Discussions on the SDV (Software Defined Vehicle) reference platform and its integration with existing AGL features.

    • Jerry emphasized the importance of consolidating AGL features into the SDV platform to align with community goals.

    • Honda expressed interest in contributing a Zephyr RTOS implementation to AGL, which will be further discussed at the next face-to-face meeting.

  • Virtualization and Hypervisor Architectures:

    • Michele Paolino presented proposals for virtualization architectures using KVM and Xen hypervisors.

    • Key points included:

      • Running containers for instrument clusters and IVI (In-Vehicle Infotainment) alongside a real-time OS in a virtual machine.

      • Challenges with GPU virtualization in Xen.

      • Alternative architectures using Cortex-R processors and OpenAMP for communication between domains.

    • The group agreed to further discuss these options during the face-to-face meeting.

  • ARM and Intel Engagement:

    • Discussions on re-engaging ARM and Intel with AGL.

    • ARM's potential rejoining of AGL was discussed, with meetings planned at Embedded World.

    • Intel's interest in AGL was noted, though their current state was described as challenging.

Action Items

  1. Jira Ticket Permissions:

    • Walt Miner to address the issue of some participants lacking permissions to resolve Jira tickets. SPEC-5373 written to address the problem.

  2. AMD Embedded Boards:

    • Walt Miner to follow up with AMD at Embedded World regarding evaluation boards.

  3. SDV Reference Platform:

    • Further discussions on SDV architecture and goals to take place during the face-to-face meeting.

  4. ARM and Intel Engagement:

    • Continue discussions with ARM and Intel to encourage their participation in AGL.

  5. Zephyr RTOS Contribution:

    • Honda to prepare for discussions on Zephyr RTOS implementation at the next meeting.