#Ivi pro pass thru how to#
#Ivi pro pass thru drivers#
#Ivi pro pass thru software#
#Ivi pro pass thru Pc#

Dmitry has done some updates on Camera/MediaВ вЂ“ postpone discussion to next time.ДЇOCUS : GPU virtualization вЂ“ Features of the PowerVR/Imagination GPUs (used in Renesas R-Car SoCs).

Most other requirements will lean on hardware virtualization support, but the group did not want to lose the idea of support simpler hardware too.

#Ivi pro pass thru how to#

Also consider how to handle a non-Linux OS, if that is included in the scenario. We might need a plausible product design scenario to support the inclusion of VIRTIO-GPU / VirGL based requirements.Initial discussion on the structure of final GPU chapter (bringing together all input from previous hardware studies).Chapter will be done, after final polishing. Closed open issues and finalized requirements.

GPIO - clarified misunderstanding that referenced SCMI even though SCMI does not cover GPIO.Participants: Stephen, Gunnar, Dmitry, Adam, Peter.Regular meetings held every week and results tracked in AVPS document and JIRA tickets.Results in AVPS and topic planning (link below) => With a virtual platform abstraction, updating to a new kernel with the new features should be feasible.

#Ivi pro pass thru software#

A hardware vendor that is able to use these latest features could have an advantage (hardware itself not faster, but the software runs faster).

Matti: (Explicit example that shows the current situation).

Also discussed how large part of Linux' functionality is actually used in practice in the industry?.

Such examples makes porting software a challenge. And then a lot of functionality built on systemd.

Gunnar: As an example, consider systemd which early on used Linux-only APIs.

could still be a large effort to port existing functionality. if they have a POSIX API, is that 'enough'.

Discussion turned to evaluating the effort (that the industry is also considering) to create new kernel(s) instead, as a Linux alternative (for safety, and development concerns as shown above).

The theory seems to be that keeping API stable and efficiently port to new hardware, could be more feasible to do in the virtual platform.

It seems this situation can't be avoided, and the industry is looking for a solution to the challenge.

Fast changes, no internal API stability guarantee etc.

Kernel updates are driven by fast development, security issues, etc.

#Ivi pro pass thru Pc#

(partly agreed, discussed the existence of firmware as one abstraction already used, and on PC side the hardware it self was standardized, etc.

It seems the 'new' distinction is a clear focus on a hardware-abstraction layer?

The virtual platform / VIRTIO / Trout and others.

Future challenges: Value-add for SoCs could be difficult if the API is limiting.

Matti: Linux kernel in particular, is an operating system kernel and a hardware-abstraction at the same time, which is challenging.

officially no APIs are stable inside Linux kernel)

#Ivi pro pass thru drivers#

Updating to new kernel drivers difficult (N.B. Adam: BSPs that add a lot of patches to Linux get stuck on older versions.Let's analyze how 'virtual platform API is stable' is different from 'user-space API is stable' (i.e.=> Is this not just shifting portability work 'somewhere else'.I'd like to analyze this idea further, compared to for example just making stable user-space APIs and creating new kernel drivers for new hardware. do we have a proposal for FM tuner? (No, not currently))Дiscussion on the usage of virtual platforms as a hardware-portability solution: We discussed virtual platform specification, if there are additional automotive-specific hardware that need VIRTIO support (e.g. Gunnar: I met with Arm (Bernhard) and Francois Ozog (active in Linaro).Some dates are missing minutes but ideas are always captured on the main project pages here. If meetings are cancelled this would be noted here.