[agl-discussions] Xen integration

Fulup Ar Foll fulup.arfoll at iot.bzh
Fri Feb 2 10:40:17 UTC 2018


Oleksandr,

For audio with Eel & 4A the audio policy while technical possible, some 
real work needs to be done before moving to a production ready system.

For a POC accessing audio policy from an other user domain should be 
relativity simple. 4A high level API is exposed through a standard AGL 
binder/binding and if you enable TCP on the audio binder you can request 
it from outside AGL. This behing said two things remains to be done:
  - 4A handle signalling but not the stream. 4A will return you with a 
sound URI, potentially an ALSA PCM or something more specific to your 
virtualisation environment.
  - AGL security model relies on SMACK and API protection does not cross 
operating systems boundaries. While be have as project to extend API 
protection to OpenID-connect for vehicule to cloud, as today nothing as 
been decided to extend AGL application framework capabilities to a 
virtualized environment.

I thing this would be a nice discution topic for next AMM in Japan, will 
you attend ?

Fulup


On 31/01/18 15:41, Oleksandr Grytsov wrote:
> Hi All,
> 
> I'm from EPAM company  and we are working on integration Xen for automotive solutions. Recently we did some demo running Xen with AGL and Android on same board. From HW point of view it is Renesas board with two displays. One display is dedicated for AGL HomeScreen second one for Android. Basically AGL related tasks were to integrate our Display and Sound backends.  Display backend is a user space application with multiple wayland surfaces. Also Sound backend is a user space application with multiple pulse audio streams. For Sound backend we did nothing special as it works in AGL dab branch without interaction with AudioManager or adjusting any audio policies. But for Display beckend we did some tricks to make it works.
> 
> Now I'm looking for proper backends integration. And have following questions:
> 
> Display:
> 
> * Multiple display support: I see some issue recently created to support it. Is there any draft spec?
> * Multiple surface support: is there any possibility to support one application with multiple surfaces? If not is there plan to support it?
> * Is it possible to work with WindowManager and HomeScreen if the application is not AGL widget but system daemon, for example?
> 
> Sound:
> 
> * What is proper way to integrate the application with AudioManager?
> * Shell this application be AGL widget or it could be any user space application?
> 
> Thanks.
>    
>   Oleksandr Grytsov
>   Lead Software Engineer
>     
>   Office: +380  44 390 5457 x 66834    Cell: +380  67 751 0148   Email: oleksandr_grytsov at epam.com
>   Kyiv, Ukraine (GMT+3)   epam.com
>    
> CONFIDENTIALITY CAUTION AND DISCLAIMER
> This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged  and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All  unintended recipients are obliged to delete this message and destroy any printed copies.
> _______________________________________________
> automotive-discussions mailing list
> automotive-discussions at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
> 



More information about the automotive-discussions mailing list