Date   

Re: agl-compositor

Marius Vlad
 

On Wed, Dec 02, 2020 at 02:29:58PM +0330, Farshid Monhaseri wrote:
Hi Marius,
Hi Farshid,
I have a question about the capability of AGL-Compositor, first I want to
post a bug/feature in AGL Jira, but then I decided to ask you first then
step further.
I have senario, like this: I have top-bar which is in panel layers, then I
have a fullscreen app. In some cases I want show the topbar(make it
visible) but without scaling down the app (change layers to normal). As I
understood the layers groups like this: bg < normal < panel < pop-up <
fullscreen. So I need to change the app layer to some layer like bg (I
think it is not possible at run time) or change the topbar layer to the
fullscreen layer (I think this also not possible since it panel initialized
statically).
Not setting any window/surface property at all should make the window
maximized (as in, it will be in the normal layer). Compositor tells the
surface to redraw itself to the correct width/height and set itself as
maximized. The surface area would not exceed those width/height values (total
surface area - minus the panel sizes).

Changing it from fullscreen to maximized should, in theory, reveal the
panels. The application can take measures to resize correctly when that
happens.

Now, I have no idea how exactly you set your window to be fullscreen, if
you're using agl-shell-desktop protocol to let the compositor know that
the surface should be fullscreen.

This shows that we're missing (in that protocol) the ability to tell the
compositor that it should basically, put/make the surface back as
maximized (in order to reaveal the panels).

I know the whole scenario is not unexpected in real-world apps but I have
lots of other similar scenarios in my mine, I am just strugling to find
answer for them.
If you not want to resize the surface to maximized, like I've said
above, do not create any panels, but instead make them a pop-up type,
that matches the panel dimensions.

The dialog/pop-up window is like an on-screen virtual keyboard it is
above all other layers. You can also de-activate it and activate (to
hide/show it) using the agl-shell-desktop protocol. alexa-viewer is a
dialog/pop-up type of application so you can use that to see what that
needs to be done.

PS: I hope you do not mind, I've CC'ed the mailing lists as maybe others
would like to be in the loop as well about this, and I'd like to ask you
do the same in the future. Either that or we use JIRA directly to
further discuss issues.

Thanks
Farshid Monhaseri


Re: Fw: Related to agl-compositor

Anusha Gugale
 

Hello Marius,


Yes,we can discuss this topic in today's call. 



Thanks & Regards,
Anusha Gugale


From: agl-dev-community@... <agl-dev-community@...> on behalf of Walt Miner <wminer@...>
Sent: Tuesday, December 1, 2020 11:40 PM
To: agl-dev-community@...
Subject: Re: [agl-dev-community] Fw: Related to agl-compositor
 
Hi Anusha, 
I can add this topic to the Application Framework Expert Group call tomorrow if you are available to attend. 

Regards,
Walt

Walt Miner
AGL Community Manager
The Linux Foundation

Visit us at:




On Tue, Dec 1, 2020 at 3:18 AM Marius Vlad <marius.vlad@...> wrote:
On Tue, Dec 01, 2020 at 02:44:50AM +0000, Anusha Gugale wrote:
> Hello All,
Hi Anusha,
>
> I want to ask few questions to @Marius
>
> Q.  Is there any plan to modify Weston/clients/simple-egl.c application so that we can run for 'agl-compositor'?
No, not really. simple-egl belongs to upstream (community). That should be
the way to do it.
> Tryout:
> - I tried to run, it just added a particular surface in pending_list, there no log for surface role added and nothing is displayed onscreen.
simple-egl does not set the app id only the title. Modifying it to set
the app_id just like the title is trivial. Could try upstreaming that,
but I do know how to argue about that change. Using app_id is specific
to AGL, but on other hand maybe updating all apps to use it might be
something desirable. Guess it is worth a shoot to see.
> - Also, run for remoting plugin with localhost but it didn't succeed.
This is a bit vague. Specifying which application is streamed to that
output is done by either using config file (in the remote-output section
you use agl-shell-app-id=app_id_of_application) or by
using agl-shell-desktop protocol. You also need a receiver application
that receives the incoming buffers and that connects to the local
compositor.

Using the same machine for this might no be that trivial, one compositor
instance does the streaming and you need another instance of the
compositor (one the same machine) with the receiver connecting to the
last one. You can specify the which wayland compositor to connect to
by using WAYLAND_DISPLAY environmental variable. Probably using
DRM backend might worth while by using ssh. Might be able to use other
backends but you need the DRM backend for dmabuf import/export so unsure
how that might work out.

>
> It will be helpful for checking RBA policy activity if this application run.
>
> Q. To implement RBA policy in agl-compositor, the plan is to use existing policy hooks so further we are thinking to create different 'policy.so'. As in current implementation existing policy code is also included in 'agl-compositor' binary. Is this ok according to the design and implementation perspective?
There's no plan to have compositor plug-ins at the moment. The policy
engine will likely be as is, as that defines the interface so that each
policy implements its own specialized versions. Even so, the ability to
dynamically load policies isn't that far-fetched so I guess that is
worth adding on next meetings to see what others think about it. A
concern here would be about security.

A small note, if you need to extend the policy engine itself (so not the
policy) that will probably need to happen directly in the compositor.

>
>
> Thanks & Regards,
> Anusha Gugale
> ________________________________
>
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Technologies Limited ( formerly known as "Sasken Communication Technologies Limited" ) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
> Read Disclaimer at http://www.sasken.com/mail-disclaimer/
>
> ________________________________
>
>
>
>
>






Re: AGL distro and redis failure

Jan Simon Moeller
 

Hi Stefan !

The package is likely there, but:
redis was skipped: redis - redis: system username redis does not have a static ID defined. Add redis to one of these files: /home/stefan/agl/jellyfish/meta-agl/meta-agl-profile-core/files/passwd

This means:
- AGL uses the 'static userid' feature of OpenEmbedded/Yocto.  This means any user required by a service needs to be pre-created.

- This happens in our case in
/home/stefan/agl/jellyfish/meta-agl/meta-agl-profile-core/files/passwd

- for a quick test, add a redis user there with:
 echo "redis::1008:1008:::" >> /home/stefan/agl/jellyfish/meta-agl/meta-agl-profile-core/files/passwd
 echo "redis::1008:" >> /home/stefan/agl/jellyfish/meta-agl/meta-agl-profile-core/files/group
then rebuild.

- To make that more permanent, create a layer and set its priority to >=81 and add these two files in
 meta-mylayer
   files/passwd
   files/group
   conf/layer.conf                 # with layer priority >= 81


Best regards,
Jan-Simon

------
Jan-Simon Möller
AGL Release Manager
The Linux Foundation

Visit us at:
www.automotivegradelinux.org
lists.automotivelinux.org
www.linuxfoundation.org


On Tue, Dec 1, 2020 at 7:56 PM Stefan Gudmundsson <exologic@...> wrote:

Hello,

 

I have a recipe that uses jsonrpc-cpp (1.3.x) and that now pulls in hiredis, which is dependent on redis.

In AGL 9 jsonrepc-cpp (0.7.x) does NOT use hiredis and thus builds there.

 

As this seems to be dependent on an AGL provided profile, I thought I’d ask here first, before digging deeper, more people may experience this at some point. Please note that the same issue with redis is in both AGL9 as AGL 10, but it is not used in 9 in my case.

 

 

stefan@Yocto:~/agl/jellyfish/build$ bitbake redis

Loading cache: 100% |############################################| Time: 0:00:01

Loaded 3893 entries from dependency cache.

Parsing recipes: 100% |##########################################| Time: 0:00:13

Parsing of 2718 .bb files complete (2661 cached, 57 parsed). 3952 targets, 329 skipped, 3 masked, 0 errors.

WARNING: No bb files matched BBFILE_PATTERN_agl-distro '^/home/stefan/agl/jellyfish/meta-agl/meta-agl-distro/'

ERROR: Nothing PROVIDES 'redis'

redis was skipped: redis - redis: system username redis does not have a static ID defined. Add redis to one of these files: /home/stefan/agl/jellyfish/meta-agl/meta-agl-profile-core/files/passwd

 

/Stefan

 


AGL distro and redis failure

Stefan Gudmundsson
 

Hello,

 

I have a recipe that uses jsonrpc-cpp (1.3.x) and that now pulls in hiredis, which is dependent on redis.

In AGL 9 jsonrepc-cpp (0.7.x) does NOT use hiredis and thus builds there.

 

As this seems to be dependent on an AGL provided profile, I thought I’d ask here first, before digging deeper, more people may experience this at some point. Please note that the same issue with redis is in both AGL9 as AGL 10, but it is not used in 9 in my case.

 

 

stefan@Yocto:~/agl/jellyfish/build$ bitbake redis

Loading cache: 100% |############################################| Time: 0:00:01

Loaded 3893 entries from dependency cache.

Parsing recipes: 100% |##########################################| Time: 0:00:13

Parsing of 2718 .bb files complete (2661 cached, 57 parsed). 3952 targets, 329 skipped, 3 masked, 0 errors.

WARNING: No bb files matched BBFILE_PATTERN_agl-distro '^/home/stefan/agl/jellyfish/meta-agl/meta-agl-distro/'

ERROR: Nothing PROVIDES 'redis'

redis was skipped: redis - redis: system username redis does not have a static ID defined. Add redis to one of these files: /home/stefan/agl/jellyfish/meta-agl/meta-agl-profile-core/files/passwd

 

/Stefan

 


Re: Fw: Related to agl-compositor

Walt Miner
 

Hi Anusha, 
I can add this topic to the Application Framework Expert Group call tomorrow if you are available to attend. 

Regards,
Walt

Walt Miner
AGL Community Manager
The Linux Foundation

Visit us at:




On Tue, Dec 1, 2020 at 3:18 AM Marius Vlad <marius.vlad@...> wrote:
On Tue, Dec 01, 2020 at 02:44:50AM +0000, Anusha Gugale wrote:
> Hello All,
Hi Anusha,
>
> I want to ask few questions to @Marius
>
> Q.  Is there any plan to modify Weston/clients/simple-egl.c application so that we can run for 'agl-compositor'?
No, not really. simple-egl belongs to upstream (community). That should be
the way to do it.
> Tryout:
> - I tried to run, it just added a particular surface in pending_list, there no log for surface role added and nothing is displayed onscreen.
simple-egl does not set the app id only the title. Modifying it to set
the app_id just like the title is trivial. Could try upstreaming that,
but I do know how to argue about that change. Using app_id is specific
to AGL, but on other hand maybe updating all apps to use it might be
something desirable. Guess it is worth a shoot to see.
> - Also, run for remoting plugin with localhost but it didn't succeed.
This is a bit vague. Specifying which application is streamed to that
output is done by either using config file (in the remote-output section
you use agl-shell-app-id=app_id_of_application) or by
using agl-shell-desktop protocol. You also need a receiver application
that receives the incoming buffers and that connects to the local
compositor.

Using the same machine for this might no be that trivial, one compositor
instance does the streaming and you need another instance of the
compositor (one the same machine) with the receiver connecting to the
last one. You can specify the which wayland compositor to connect to
by using WAYLAND_DISPLAY environmental variable. Probably using
DRM backend might worth while by using ssh. Might be able to use other
backends but you need the DRM backend for dmabuf import/export so unsure
how that might work out.

>
> It will be helpful for checking RBA policy activity if this application run.
>
> Q. To implement RBA policy in agl-compositor, the plan is to use existing policy hooks so further we are thinking to create different 'policy.so'. As in current implementation existing policy code is also included in 'agl-compositor' binary. Is this ok according to the design and implementation perspective?
There's no plan to have compositor plug-ins at the moment. The policy
engine will likely be as is, as that defines the interface so that each
policy implements its own specialized versions. Even so, the ability to
dynamically load policies isn't that far-fetched so I guess that is
worth adding on next meetings to see what others think about it. A
concern here would be about security.

A small note, if you need to extend the policy engine itself (so not the
policy) that will probably need to happen directly in the compositor.

>
>
> Thanks & Regards,
> Anusha Gugale
> ________________________________
>
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Technologies Limited ( formerly known as "Sasken Communication Technologies Limited" ) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
> Read Disclaimer at http://www.sasken.com/mail-disclaimer/
>
> ________________________________
>
>
>
>
>






GSoD Weekly Update: Week 14

Shankho Boron Ghosh
 

Week 14 :
--------------
- Developer Guides
- Revised [1], [2] Developer Guides with tutorials on installing
the "SDK" [3] and creating a new "service" [4] from scratch.
- Revised [5], [6] Developer Guides with a tutorial on creating a
new QT "application" [7] from scratch.
- Revised [8], [9] and added "AGL Layers" [10] as a part of
Developer Guides.
- Revised [11], [12] and added "Application Framework" [13] as a
part of Developer Guides.
- Revised [14], [15] and added "Application Framework Binder"
[16] as a part of Developer Guides.
- Meta refreshed [17], [18] the "AppFW Privileges Management"
page [19] to the pdf [20].
- Revised [21], [22] and added "AFB Helper Guide" [23] as a part
of Developer Guides.
- Revised [24], [25] and added "Using CMAKE Applications Module"
[26] as a part of Developer Guides.

- Minor Fixes
- Corrected [27], [28] internal link in documentation homepage [29].
- Removed [30], [31] redundant directory in APIs and Services [32].

- Final Notes
- These final Change Requests are in process of review on Gerrit.
The final state of the documentation site [33] would be as
agl-docs.readthedocs.io [29], once the Change Requests are accepted.
Also, all the weekly reports are available on my personal website
[34].
- Currently working for the "Project finalization phase" of Season
of Docs which requires a final work report and mentor evaluation,
further leading to the conclusion of GSoD.
- Last but not least, I would like to express my gratitude to my
mentors, Jan-Simon, and Walt for helping me through GSoD and also to
the whole AGL community for being so inclusive and friendly. I plan to
continue my involvement here at AGL for the foreseeable future.

[1] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25610
[2] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25642
[3] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/1_Setting_Up_AGL_SDK/
[4] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/2_Creating_a_New_Service/
[5] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25660
[6] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25612
[7] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/3_Creating_a_New_Application/
[8] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25661
[9] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25613
[10] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/6_AGL_Layers/1_Overview/
[11] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25662
[12] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25614
[13] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/1_Application_Framework/0_Introduction/
[14] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25663
[15] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25615
[16] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/2_Application_Framework_Binder/0_Overview/
[17] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25664
[18] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25676
[19] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/3_AppFW_Privileges_Management/AppFW-Privileges_Management/
[20] : https://iot.bzh/download/public/2016/appfw/03-AGL-AppFW-Privileges-Management.pdf
[21] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25665
[22] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25677
[23] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/4_AFB_Helper_Guide/1_Usage/
[24] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25666
[25] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25678
[26] : https://agl-docs.readthedocs.io/en/master/#3_Developer_Guides/5_Using_CMAKE_Applications_Module/1_Project_Architecture/
[27] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25667
[28] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25679
[29] : https://agl-docs.readthedocs.io/en/master/#
[30] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25668
[31] : https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25680
[32] : https://agl-docs.readthedocs.io/en/master/#4_APIs_and_Services/0_API_Reference/
[33] : https://docs.automotivelinux.org/
[34] : https://growupboron.github.io/blog/


AGL testing cycle for master branch

Edi Feschiyan
 

Hello everyone,

Overall summary: working

Audio works locally as well as over bluetooth.
Bluetooth, wifi and ethernet are working.
Contacts, sync, dialer, navigation and radio are working

Best regards,
Eddie


Re: Upcoming AGL Events and Announcements

Emily Olin
 

For Automotive Linux Summit, you can use code 20ALSOSSJ for a 20% discount, making registration only $40. 

Here is the link to register: http://www.cvent.com/d/fhqrr2/4W. The code will be entered at the end of registration.

On Mon, Nov 30, 2020 at 11:09 PM Walt Miner <wminer@...> wrote:
Some reminders about events happening in the AGL community the next few weeks. 

1) There is another AGL Webinar scheduled for tomorrow, December. Leon Anavi of Konsulko Group who has done great work with AGL on the Raspberry Pi and on the Raspberry Pi project in general will present "Getting Started with AGL using a Raspberry Pi". To sign up see 


2) Automotive Linux Summit and Open Source Summit Japan starts December 2 (Japan time) or tomorrow night here in the US.  If you have not already signed up, registration is very reasonably priced and there will be a lot of great talks including updates from the AGL Virtualization, Instrument Cluster, and Production Ready IVI Expert Groups. You can register for ALS and OSS-Japan here:


If the time zone of the live event is awkward for you, the recordings will be available for 30 days after the event to view. 

3) Next week (Dec 8 and 9) we will hold a Virtual Face-To-Face meeting mainly to discuss architecture and design work being done by the Instrument Cluster Expert Group and the Production Ready IVI Expert Group as well continuing to discuss any open topics from the last Virtual F2F meeting. The final agenda will be published on Thursday after the SAT meeting.  Meanwhile, you can sign up and add any topics to the wish list on the wiki page. 


 
4) Speaking of the Product Ready IVI Expert Group, that new EG will officially launch on December 10, led by Toyota.  The Expert Group will take the work that was started in the System Architecture to create a version of the IVI profile that is closer to being ready for production.  You can learn more about the PR IVI Expert Group during their ALS presentation. 



Regards,
Walt



Walt Miner
AGL Community Manager
The Linux Foundation

Visit us at:


--
Emily Olin
eolin@...


Re: Fw: Related to agl-compositor

Marius Vlad
 

On Tue, Dec 01, 2020 at 02:44:50AM +0000, Anusha Gugale wrote:
Hello All,
Hi Anusha,

I want to ask few questions to @Marius

Q. Is there any plan to modify Weston/clients/simple-egl.c application so that we can run for 'agl-compositor'?
No, not really. simple-egl belongs to upstream (community). That should be
the way to do it.
Tryout:
- I tried to run, it just added a particular surface in pending_list, there no log for surface role added and nothing is displayed onscreen.
simple-egl does not set the app id only the title. Modifying it to set
the app_id just like the title is trivial. Could try upstreaming that,
but I do know how to argue about that change. Using app_id is specific
to AGL, but on other hand maybe updating all apps to use it might be
something desirable. Guess it is worth a shoot to see.
- Also, run for remoting plugin with localhost but it didn't succeed.
This is a bit vague. Specifying which application is streamed to that
output is done by either using config file (in the remote-output section
you use agl-shell-app-id=app_id_of_application) or by
using agl-shell-desktop protocol. You also need a receiver application
that receives the incoming buffers and that connects to the local
compositor.

Using the same machine for this might no be that trivial, one compositor
instance does the streaming and you need another instance of the
compositor (one the same machine) with the receiver connecting to the
last one. You can specify the which wayland compositor to connect to
by using WAYLAND_DISPLAY environmental variable. Probably using
DRM backend might worth while by using ssh. Might be able to use other
backends but you need the DRM backend for dmabuf import/export so unsure
how that might work out.


It will be helpful for checking RBA policy activity if this application run.

Q. To implement RBA policy in agl-compositor, the plan is to use existing policy hooks so further we are thinking to create different 'policy.so'. As in current implementation existing policy code is also included in 'agl-compositor' binary. Is this ok according to the design and implementation perspective?
There's no plan to have compositor plug-ins at the moment. The policy
engine will likely be as is, as that defines the interface so that each
policy implements its own specialized versions. Even so, the ability to
dynamically load policies isn't that far-fetched so I guess that is
worth adding on next meetings to see what others think about it. A
concern here would be about security.

A small note, if you need to extend the policy engine itself (so not the
policy) that will probably need to happen directly in the compositor.



Thanks & Regards,
Anusha Gugale
________________________________

SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Technologies Limited ( formerly known as "Sasken Communication Technologies Limited" ) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/mail-disclaimer/

________________________________





Upcoming AGL Events and Announcements

Walt Miner
 

Some reminders about events happening in the AGL community the next few weeks. 

1) There is another AGL Webinar scheduled for tomorrow, December. Leon Anavi of Konsulko Group who has done great work with AGL on the Raspberry Pi and on the Raspberry Pi project in general will present "Getting Started with AGL using a Raspberry Pi". To sign up see 


2) Automotive Linux Summit and Open Source Summit Japan starts December 2 (Japan time) or tomorrow night here in the US.  If you have not already signed up, registration is very reasonably priced and there will be a lot of great talks including updates from the AGL Virtualization, Instrument Cluster, and Production Ready IVI Expert Groups. You can register for ALS and OSS-Japan here:


If the time zone of the live event is awkward for you, the recordings will be available for 30 days after the event to view. 

3) Next week (Dec 8 and 9) we will hold a Virtual Face-To-Face meeting mainly to discuss architecture and design work being done by the Instrument Cluster Expert Group and the Production Ready IVI Expert Group as well continuing to discuss any open topics from the last Virtual F2F meeting. The final agenda will be published on Thursday after the SAT meeting.  Meanwhile, you can sign up and add any topics to the wish list on the wiki page. 


 
4) Speaking of the Product Ready IVI Expert Group, that new EG will officially launch on December 10, led by Toyota.  The Expert Group will take the work that was started in the System Architecture to create a version of the IVI profile that is closer to being ready for production.  You can learn more about the PR IVI Expert Group during their ALS presentation. 



Regards,
Walt



Walt Miner
AGL Community Manager
The Linux Foundation

Visit us at:



Cancelled Event: AGL System Architecture Team - Thursday, 31 December 2020 #cal-cancelled

agl-dev-community@lists.automotivelinux.org Calendar <noreply@...>
 

Cancelled: AGL System Architecture Team

This event has been cancelled.

When:
Thursday, 31 December 2020
2:00pm to 3:00pm
(UTC+00:00) UTC

Where:
https://zoom.us/j/443971577?pwd=bjg5dGdpTTlPdmpNWlZSQ0RVTWtwZz09

Organizer: Walt Miner wminer@...

Description:

Walt Miner is inviting you to a scheduled Zoom meeting.
 
Topic: [AGL-SAT]Biweekly Call
Time: This is a recurring meeting Meet anytime
 
Join Zoom Meeting
https://zoom.us/j/443971577?pwd=bjg5dGdpTTlPdmpNWlZSQ0RVTWtwZz09
 
Meeting ID: 443 971 577
Passcode: 239723
One tap mobile
+16699006833,,443971577# US (San Jose)
+16465588656,,443971577# US (New York)
 
Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        877 369 0926 US Toll-free
        855 880 1246 US Toll-free
Meeting ID: 443 971 577
Find your local number: https://zoom.us/u/ameRude4a
 


Cancelled Event: EG Connectivity - Thursday, 24 December 2020 #cal-cancelled

agl-dev-community@lists.automotivelinux.org Calendar <noreply@...>
 

Cancelled: EG Connectivity

This event has been cancelled.

When:
Thursday, 24 December 2020
2:00pm to 3:00pm
(UTC+00:00) UTC

Where:
https://zoom.us/j/151930034?pwd=OEt1VnhIUmdQZEwwTzE2cHdCYzZTZz09

Organizer: Walt Miner wminer@...

Description:

Walt Miner is inviting you to a scheduled Zoom meeting.
 
Topic: AGL Connectivity EG Biweekly Meeting
 
Join Zoom Meeting
https://zoom.us/j/151930034?pwd=OEt1VnhIUmdQZEwwTzE2cHdCYzZTZz09
 
Meeting ID: 151 930 034
Passcode: 460200
Find your local number: https://zoom.us/u/ameRude4a
 


Cancelled Event: Production Ready IVI EG - Thursday, 24 December 2020 #cal-cancelled

agl-dev-community@lists.automotivelinux.org Calendar <noreply@...>
 

Cancelled: Production Ready IVI EG

This event has been cancelled.

When:
Thursday, 24 December 2020
12:00pm to 1:00pm
(UTC+00:00) UTC

Where:
https://zoom.us/j/98420206742?pwd=WFFleHBYY0lEejdUR2haQnBTMGsyZz09

Organizer: Walt Miner

Description:

Walt Miner is inviting you to a scheduled Zoom meeting.
 
Topic: IVI PR Expert Group
Time: This is a recurring meeting Meet anytime
 
Join Zoom Meeting
https://zoom.us/j/98420206742?pwd=WFFleHBYY0lEejdUR2haQnBTMGsyZz09
 
Meeting ID: 984 2020 6742
Passcode: 121632
 
Meeting ID: 984 2020 6742
Find your local number: https://zoom.us/u/amB4niOD9
 
 


Updated Event: Production Ready IVI EG #cal-invite

agl-dev-community@lists.automotivelinux.org Calendar <noreply@...>
 

Production Ready IVI EG

When:
Thursday, 24 December 2020
12:00pm to 1:00pm
(UTC+00:00) UTC
Repeats: Every 2 weeks on Thursday

Where:
https://zoom.us/j/98420206742?pwd=WFFleHBYY0lEejdUR2haQnBTMGsyZz09

Organizer: Walt Miner

Description:

Walt Miner is inviting you to a scheduled Zoom meeting.
 
Topic: IVI PR Expert Group
Time: This is a recurring meeting Meet anytime
 
Join Zoom Meeting
https://zoom.us/j/98420206742?pwd=WFFleHBYY0lEejdUR2haQnBTMGsyZz09
 
Meeting ID: 984 2020 6742
Passcode: 121632
 
Meeting ID: 984 2020 6742
Find your local number: https://zoom.us/u/amB4niOD9
 
 


Event: Production Ready IVI EG #cal-invite

agl-dev-community@lists.automotivelinux.org Calendar <noreply@...>
 

Production Ready IVI EG

When:
Thursday, 10 December 2020
12:00pm to 1:00pm
(UTC-06:00) America/Chicago
Repeats: Every 2 weeks on Thursday

Where:
https://zoom.us/j/98420206742?pwd=WFFleHBYY0lEejdUR2haQnBTMGsyZz09

Organizer: Walt Miner

Description:

Walt Miner is inviting you to a scheduled Zoom meeting.
 
Topic: IVI PR Expert Group
Time: This is a recurring meeting Meet anytime
 
Join Zoom Meeting
https://zoom.us/j/98420206742?pwd=WFFleHBYY0lEejdUR2haQnBTMGsyZz09
 
Meeting ID: 984 2020 6742
Passcode: 121632
 
Meeting ID: 984 2020 6742
Find your local number: https://zoom.us/u/amB4niOD9
 
 


Fw: Related to agl-compositor

Anusha Gugale
 

Hello All,

I want to ask few questions to @Marius

Q. Is there any plan to modify Weston/clients/simple-egl.c application so that we can run for 'agl-compositor'?
Tryout:
- I tried to run, it just added a particular surface in pending_list, there no log for surface role added and nothing is displayed onscreen.
- Also, run for remoting plugin with localhost but it didn't succeed.

It will be helpful for checking RBA policy activity if this application run.

Q. To implement RBA policy in agl-compositor, the plan is to use existing policy hooks so further we are thinking to create different 'policy.so'. As in current implementation existing policy code is also included in 'agl-compositor' binary. Is this ok according to the design and implementation perspective?


Thanks & Regards,
Anusha Gugale
________________________________

SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Technologies Limited ( formerly known as "Sasken Communication Technologies Limited" ) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/mail-disclaimer/

________________________________


Collabora weekly progress w/e 29th November 2020

Nick Milner
 

Hi All,

Please find below a brief summary of the progress Collabora have made last week on Weston/Wayland and Pipewire.

Weston / Wayland

Marius

- SPEC-3601 - Using PACKAGECONFIG/AGL_FEATURES instead of using DISTRO_FEATURES for customizing remoting/transmitter output. With it, bump SRCREV for agl-compositor to include waltham-transmitter-plugin support and a couple of other fixes (like GDK/GTK client support). These changes will enable building by default the plug-ins, AGL_FEATURES giving the possibility to have the environment already set-up for either cases. 

- SPEC-3694 - (affects also  SPEC-3693, SPEC-3679 and  SPEC-3692) Reviewing and testing libjsonc ref counting issue which plagued installation/uninstallation and made homescreen service crash. 

Pipewire

George

- Investigated the current status of the PipeWire stack on Yocto and AGL and started looking at what changes are necessary in order to upgrade to a more recent version

Kind regards,

Nick


Invited talk for the British Computer Society (Open Source Specialist Group) Evening

Julian M. Kunkel
 

Dear all
I'm member of the BCS Open Source Specialist Group committee and
organizing an evening [1] about open source in automotive on Feb 18th
(18:30-20:30 GMT).
It would be fabulous to get one or two talks from you about open
software/hardware (in automotive) in the evening. If you like to speak
just reply to me with a short title.


Please visit the event draft page [1].
[1] https://ossg.bcs.org/blog/event/open-source-in-automotive/

Attendance is free (registration welcome but we also post the URL of the
event shortly before).
Additionally, we are happy to host on our blog stories regarding open
source.

Best,
Julian Kunkel

--
Dr. Julian Kunkel
Lecturer, Department of Computer Science
+44 (0) 118 378 8218
http://www.cs.reading.ac.uk/
https://hps.vi4io.org/
PGP Fingerprint: 1468 1A86 A908 D77E B40F 45D6 2B15 73A5 9D39 A28E


Re: Not able build telematics for Raspberry Pi3

Leon Anavi
 

Hi Rakesh, Scott,

On 30.11.20 г. 16:14 ч., Scott Murray wrote:
On Wed, 25 Nov 2020, RAKESH wrote:

Hi Scott,
Now i am able to run the simple_can_simulator.py can0 and can see data flowing in... also afbd-telematics-recorder process is running successfully ..
but im not able to connect to *iot.eclispse.org* using my MQTT mobile tool and even in node red!!
my /etc/xdg/telematics.conf looks like below..
[MQTT]
broker=iot.eclipse.org
port=1883
keepalive=60
I've no good ideas on that front, perhaps try pointing at a local
Mosquitto broker instance for testing as I recommended previously.
It's packaged for most Linux distributions, and running it with the "-v"
verbose option makes it pretty easy to see if it's receiving messages.
Rakesh, I don't have particular experience wit the telematics recipes but I guess you may need to update the configurations for public Eclipse MQTT broker according to https://mqtt.eclipse.org/

Otherwise, just like Scott, I personally prefer using my own instance of Mosquitto MQTT broker rather than the free public services.

Best regards, Leon

Scott



--
Leon Anavi
Software Engineer
konsulko.com


Re: Not able build telematics for Raspberry Pi3

Scott Murray
 

On Wed, 25 Nov 2020, RAKESH wrote:

Hi Scott,
Now i am able to run the simple_can_simulator.py can0 and can see data flowing in... also afbd-telematics-recorder process is running successfully ..
but im not able to connect to *iot.eclispse.org* using my MQTT mobile tool and even in node red!!
my /etc/xdg/telematics.conf looks like below..
[MQTT]
broker=iot.eclipse.org
port=1883
keepalive=60
I've no good ideas on that front, perhaps try pointing at a local
Mosquitto broker instance for testing as I recommended previously.
It's packaged for most Linux distributions, and running it with the "-v"
verbose option makes it pretty easy to see if it's receiving messages.

Scott