This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
agl-roadmap [2020/03/25 12:56] waltminer [From App FW and Security EG] |
agl-roadmap [2021/03/11 12:21] (current) YAMAGUCHINaoto |
||
---|---|---|---|
Line 3: | Line 3: | ||
The official AGL Roadmap is maintained in Jira. [[https://jira.automotivelinux.org/issues/?filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:using-jira|here]]. | The official AGL Roadmap is maintained in Jira. [[https://jira.automotivelinux.org/issues/?filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:using-jira|here]]. | ||
- | ===== 2020 Roadmap/ Workplan from SAT ===== | + | ===== Roadmap/ Workplan from SAT ===== |
+ | |||
+ | Beginning in [[https://docs.google.com/spreadsheets/d/1WsFPh_-2wAYE8NvKlBGywYixhhJz9EBlbUR02r0UWF8/edit?usp=sharing | 2021 Feature Planning by Expert Group]] will be managed in a Google Sheet. | ||
- | Updated 13 Feb 2020 | + | Updated 01 March 2021 |
* **Happy Halibut and Itchy Icefish on Yocto 2.6 (thud)** | * **Happy Halibut and Itchy Icefish on Yocto 2.6 (thud)** | ||
- | * **Jumping Jellyfish and Kooky Koi on Yocto 3,0 (zeus)** | + | * **Jumping Jellyfish, Kooky Koi, Lucky Lamprey, and Magic Marlin on Yocto 3,1 (dunfell)** |
- | * | + | |
* Candidate Components to move from meta-agl-devel to meta-agl | * Candidate Components to move from meta-agl-devel to meta-agl | ||
* Voice core components | * Voice core components | ||
* PipeWire | * PipeWire | ||
* meta-agl-profile-graphical-html5 | * meta-agl-profile-graphical-html5 | ||
- | * Review Reference Hardware System Architecture document and consider its implications for the software architecture. | ||
- | * Move RHSA to doc site. | ||
- | * Finish the documentation site improvements and increase the amount of documentation by 100% | ||
- | * **Add video support to mediaplayer binding.** | ||
* Video player and in-vehicle video architecture that allow third-party plug-ins, rear view camera, Autonomous vehicles, encrypted data such as widevine (from Google) for Netflix, Hulu, Android, etc. | * Video player and in-vehicle video architecture that allow third-party plug-ins, rear view camera, Autonomous vehicles, encrypted data such as widevine (from Google) for Netflix, Hulu, Android, etc. | ||
- | * Finish AGL spec 2.0 | + | |
* Speech API maturity | * Speech API maturity | ||
- | * Completion of Home Screen, Window Manager, and Compositor re-architecture | + | |
* Instrument Cluster reference device improvements and maturity | * Instrument Cluster reference device improvements and maturity | ||
* New reference board for 2020? Switch to RHSA board. | * New reference board for 2020? Switch to RHSA board. | ||
Line 57: | Line 55: | ||
* Add real time capabilities on APIs (priorities, predictable execution) to guarantee QoS | * Add real time capabilities on APIs (priorities, predictable execution) to guarantee QoS | ||
- | + | ==== From Instrument Cluster EG ==== | |
+ | * Updated 11 Mar 2021 | ||
+ | * Audio Management (Inter container management) | ||
+ | * Start at 2020. Now working. | ||
+ | * Ref. [[https://jira.automotivelinux.org/browse/SPEC-3471|this issue]] | ||
+ | * Improvement for DRM lease improvement | ||
+ | * Maintenance for AGL upstream. | ||
+ | * Add DRM lease support to AGL compositor | ||
+ | * Ref. [[https://jira.automotivelinux.org/browse/SPEC-3838|this issue]] | ||
+ | * V4L2 overlay support | ||
+ | * <del>Fast Boot</del> Dropped | ||
+ | * OSS reference implementation for the RTOS combinations. | ||
+ | * Develop this task with L.F. mentorship in our plan. | ||
+ | * Implement RTOS with real-time function (ex. CAN communication) and inter OS communication using Bosch iccom. | ||
+ | * Ref. {{sat_meetings:gsoc_sat.pdf}} | ||
+ | * Rename and upstreaming of Bosch iccom. | ||
+ | * AGL IC integration (Qualified IC profile) | ||
+ | * Adding board support | ||
+ | * IC EG members may realize to the qualified ic profile at only one reference board. When we want to add another board, need to another work. | ||
+ | * OSS assessment | ||
+ | * New IC components | ||
+ | * Will be discuss. | ||
+ | * Non volatile RAM disk development. | ||
+ | * PRAMFS was stopped maintenance. Need to same solution. In case of IVI PR, that same situations. | ||
+ | * Non volatile RAM block device?. | ||
==== From App FW and Security EG ==== | ==== From App FW and Security EG ==== | ||
- | * Updated 25 Mar 2020 | + | * Updated 24 Feb 2021 |
+ | * Open questions for IVI PR effort | ||
+ | * Continued use of systemd | ||
+ | * Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution. | ||
+ | * API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another) | ||
+ | * Long-term use of Qt | ||
+ | * IPC should be defined and selected. | ||
* Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | ||
* Changes necessary at binder level for V2C (SSL transport) | * Changes necessary at binder level for V2C (SSL transport) | ||
+ | * App Signing and Installation Mechanism | ||
* Developer workflow is needed for managing keys | * Developer workflow is needed for managing keys | ||
- | * //Development mode and Production mode for app management// | + | * Development mode and Production mode for app management |
* Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. | * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. | ||
- | * //Terminal app on home screen// | ||
- | |||
* App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5 | * App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5 | ||
* App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? | * App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? | ||
* App Framework binder communications shall be able to manage return from sleep mode. | * App Framework binder communications shall be able to manage return from sleep mode. | ||
- | * **GG Priorities for App FW** | + | * App Life Cycle |
* Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH | * Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH | ||
* Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread) | * Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread) | ||
* Kill apps individually from life cycle manager | * Kill apps individually from life cycle manager | ||
* Need to define state diagram for app life cycle | * Need to define state diagram for app life cycle | ||
- | + | ||
- | * //Multi-user use case// | + | |
* API for abstraction of hardware mechanism for signing apps, packages, etc. | * API for abstraction of hardware mechanism for signing apps, packages, etc. | ||
- | * //Unit testing for app framework// | ||
* //Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms.// | * //Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms.// | ||
* //Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]]// | * //Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]]// | ||
Line 92: | Line 116: | ||
* Sign at build time in AGL CI system with a check at run time | * Sign at build time in AGL CI system with a check at run time | ||
- | * Web Apps/ HTML 5 | + | * **Web Apps/ HTML 5** |
* Upstream Chromium Webview the API required by Web Application Manager | * Upstream Chromium Webview the API required by Web Application Manager | ||
* Simplify the communication between Chromium and WAM | * Simplify the communication between Chromium and WAM | ||
Line 103: | Line 127: | ||
* Additional demo apps | * Additional demo apps | ||
==== From Graphics EG ==== | ==== From Graphics EG ==== | ||
- | Updated 20 Feb 2020 | + | Updated 29 Jul 2020 |
Our responsibilities have been almost completed in 2019. Our individual activities are not planned for next year. | Our responsibilities have been almost completed in 2019. Our individual activities are not planned for next year. | ||
Line 110: | Line 134: | ||
* Graphic | * Graphic | ||
* **Finish Window Manager and Homescreen work** | * **Finish Window Manager and Homescreen work** | ||
- | * Home Screen API / service | + | * Home Screen API / service -Complete for JJ |
- | * UI for Qt | + | * UI for Qt - Complete for JJ |
- | * UI for HTML5 | + | * UI for HTML5 - in-flight for JJ |
* High level API for virtual keyboard in english and Japanese | * High level API for virtual keyboard in english and Japanese | ||
* Pop-up support | * Pop-up support | ||
Line 143: | Line 167: | ||
* Speech and Text to Speech Services collaboration | * Speech and Text to Speech Services collaboration | ||
* Policy management between mic input and Media player output | * Policy management between mic input and Media player output | ||
- | |||
- | * Questions for EG from SAT: | ||
- | * Do we remove support for IVI protocol is favor of XDG? | ||
- | * Answer: No. Cannot deprecate IVI protocol unless extensions to XDG are made. | ||
- | |||
- | * What is the roadmap for Wayland/Weston versions for 2018? | ||
- | * SAT recommends following Yocto. | ||
Line 186: | Line 203: | ||
==== From Virtualization EG ==== | ==== From Virtualization EG ==== | ||
+ | * VirtIO Porting | ||
+ | * Add VirtIO frontend (OASIS v1.1) to AGL | ||
+ | * Create documents to illustrate how to enable VirtIO | ||
+ | * Add VirtIO support and provide reference implementation on AGL reference hardware. | ||
+ | * EG Demo in ALS | ||
* AGL virtualization support (HOST) | * AGL virtualization support (HOST) | ||
* Add support for open-source hypervisors in meta-egvirt for both ARM and Intel AGL platforms. In this way, at compilation time it will be possible to select the hypervisor to use | * Add support for open-source hypervisors in meta-egvirt for both ARM and Intel AGL platforms. In this way, at compilation time it will be possible to select the hypervisor to use | ||
Line 201: | Line 223: | ||
* VMs/AGL profiles communication | * VMs/AGL profiles communication | ||
* define, design and develop a common API to enable communication/interaction between different VMs/AGL profiles | * define, design and develop a common API to enable communication/interaction between different VMs/AGL profiles | ||
- | * CES2019 demonstrator integration | ||
- | * include virtualization in the CES2019 demo, in a way that all the new features developed in 2018 are demonstrated | ||
- | * showcase at least two operating systems running concurrently (e.g., two AGL profiles), interacting and exchanging data with each other | ||