Genivi design direction needed
Friedrich, Eugen (ADITG/SW1)
efriedrich at de.adit-jv.com
Mon Nov 28 08:56:53 EST 2016
There is not such document, or generic rule that doesn’t allow you to pass the fix id from the HMI central controller to you application.
The idea that content which appears on the screen is “confirmed” by the HMI central controller so it is known to the IVI system.
So you can assign fix id’s for you application during compile time of the application and HMI central controller of you can generate id’s during runtime from the HMI central controller
In both cases HMI central controller will exactly now the id’s and can identify and control the applications.
From the ivi system point of view we should never assign the id’s automatically e.g. from the compositor.
But it ok to have e.g. some id range which can be used by app-store and HMI central controller will put this to dedicated layer in order to put this in the correct place or z-order to not cover the security relevant content.
Software Group I (ADITG/SW1)
Tel. +49 5121 49 6921
From: genivi-ivi-layer-management [mailto:genivi-ivi-layer-management-bounces at mailman1.genivi.org] On Behalf Of Rajagopal, Arunkumar (A.)
Sent: Montag, 28. November 2016 14:42
Cc: Murugesan, Manikandan (M.); Velu, Saravanan (S.)
Subject: Genivi design direction needed
Hi Genivi-ivi-layer design team,
We want to understand and direction, where & how we can define the surface ID for the individual client applications.
As per our current design, We are the HMI central controller(using IVI shell) and once our application is boot up then we are passing the static and unique surface ID to every application by VMF message. Until that client should wait for the surface ID from the HMI central controller.
For example, to Navigation client application we are passing a static number once our HMI central controller is ready.
This is for just kind of hand shaking purpose and we are deciding the static and unique surface ID during run time(let say we are passing 110 is the surface ID for every power cycle).
But during our internal discussion we should not pass any static and unique surface id to the navigation client application on every boot up.
Because it is deviating the Genivi design architecture, so navigation client should hard code the surface id and they should not wait for the surface id to pass by HMI central controller.
But I haven’t seen anywhere in the Genivi document that we should not pass the surface ID to any client during boot up.
Please suggest us and clarify.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the genivi-ivi-layer-management