Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Gunnar: Walking through the ARM SBSA presentation to pick up comments / feedback / further discussion points

...

raw notes (to be checked by Gunnar)

  • discussion on HV booting
  • Matti: UEFI - bootloader less flexible than uboot, it might make sense to reference UEFI work, but UEFI is "a beast"
  • Kai: @Matti you put the complexity in the device tree, what do you think ?
  • Matti: mentions ACPI
  • Gunnar: what about the embedded os ?
  • Matti: linux and android can be booted using UEFI
  • Matt: makes comment about EBBR spec (Embedded Base Boot Requirement)s, it is time to talk to linaro guys IMHO
  • Artem: there are some platforms that use already UEFI
  • Artem: we can summarize some of the requirements from EBBR
  • /TODO/ Artem summarize EBBR requirements in the automotive virtualization platform spec
  • discussion on booting AUTOSAR
  • unidentified: important to be agnostic to which AUTOSAR OS is booted
  • Matti: very valid point to consider, a couple of years ago, boot was project specific, separate boot protocol per ^project, this has changed now !!
  • short discussion on how AUTOSAR might engage in the booting process specification
  • back to SBSA - power state coordination interface PSCI
  • Matti: on arm systems, all hw and hv vendors support PSCI, note that PSCI is for cores only, SCMI is for peripherals
  • Artem: discussion on SCMI specifications (not captured), how to write specs for this ?
  • Mmatti: would be very difficult to harmonize this, automotive is a niche at the end, and cannot be maintained elsewhere
  • Matt: do we think this is a requirement in the automotive space?
  • Matt: mentions the thermal constraint, we might have to shutdown some VMs due to overheat

HV Workshop topics

  • Matti: 1) Audio virtualisation - update on our VIRTIO proposal, and discussion
               2) Video (codecs and camera) - present and talk about it
  • Artem: 1) Xen-PV as option to VIRTIO protocol
                2) Native TrustZone access for guests, including our recent OPTEE changes
                 (Matti requests also this)
  • Gunnar: We also have Kai's presentation on VIRTIO "natively"

...