...
- Discussion on boot times...
- Just for reference: 1 second Linux Boot example (old) (not snapshot or hibernation, if I recall correctly)
"Real-world" might be different.
- Just for reference: 1 second Linux Boot example (old) (not snapshot or hibernation, if I recall correctly)
- Sang-Bum: <100ms hypervisor load is generally possible. What is the requirement?
- /TODO/ Add Sriram's notes
- architecture proposed by Sriram at the bottom of this page is aligned with the rear camera use case
- discussion on EVS (External Video System) on top of android
- discussion on Green Hills solution
- /TODO/ Nikola upload the diagram with microRTOS based architecture (with HV as a thin layer on top of RTOS)
- RTOS is responsible for the scheduling, HV is there to enable Linux
- Nikola: goto GHS website the GHS solution is fully described there
- Nikola; you do not need to boot the whole linux to get the rearview camera up & running, you need to boot only the rtos part
- Sang bum; would you require two video streams, one coming from rtos and the later another one coming form android or linux ?
- discussion on the handover of video streams
Sriram's notes - minor edits and formatting
(Camera use-case an architecture)
- Birds Eye View / Surround View could be possibly only implemented in the Android Partition and may not be available as part of early RVC
- Following are options for supporting such a use case through out the lifetime of a IVI session ( from startup to shutdown)
- Everything in Vehicle domain ( Basic as well as advanced view ) => No handover / arbitration required with any other domain
- Basic implementation in Vehicle domain + Advanced implementation in Linux/Android domain => Handover / arbitration of camera stream is required
- Everything in Linux/Android domain ( Basic as well as advanced ) =>
- Dedicated partition ( potentially a third domain besides Vehicle and Android/Linux domain) that does everything
What are the implications for Hypervisor?
- Constraint as of today in Android : Cannot do early RVC within 2 seconds.. however that is on the roadmap
- Linux does not have this constraint as it is completely Open Architecture and free from Compability aspects
- Solutions for early camera systems
- Snapshot / Hibernation speeds up boot and production solutions with < 2 seconds camera is possible
- Example from a camera product( high end camera )
- No safety aspects in consideration in the above example; non-automotive
- Load time of hypervisor ~ 100 ms
June 19
Agenda:
- VIRTIO intro
- Use Case → Architecture → Problem Statement → Results
...