Hi Compositor team, In the BIT we are discussing the spring update to the Genivi Baseline and meta-ivi and I would like to check your plans for the Compositor component and ivi-extension. + Source + meta-ivi release v14.50.1 was based on YP 2.5 (Sumo) and released in October 2018. It uses ivi-extension v2.1.0 and SRCREV = "d2c2e262f3bdc9db33b3014293fcdbcfdc90ab27". The current dev cycle for the spring releases will be for meta-ivi release v15.0.x and based on YP 2.6 (Thud). The meta-ivi master branch is the working branch for this and has already been rebased on Thud. It currently points at the ivi-extension commit SRCREV = "9acdaa1a9c79558691b1513cc4917f2ced91af8a", which is up to date except for a series of commits in November updating EGLWLMockNavigration. Can you update the BIT on your roadmap? Do you plan new functionality for us to adopt for this cycle? Will a new release be made? Should we adopt the MockNavigation changes? Do you plan to rebase and merge PR #82? Can we assume that PR #103 will stay unmerged as an example? + Compliance + Although it will not affect the meta-ivi updates we have been discussing the next Genivi specification update with the compliance team. They are looking at what component updates might be needed. Do you see a need for a Compositor component specification update? Regards Steve BIT Lead

Hi Steve, We are planning to use the Weston 6.0 release which not ready now, I'm not when is the deadline to the 15.0 release but without Weston 6.0 there are no interesting features. Weston 6 will bring: Xdgshell support in ivi-shell (we would be able to merge the pull request 103) General improvements in Weston Debug protocol, which can be used to implement better reporting from Weston core Mocknavigation update can be ignored it is just an better looking demo, no new functionality + Compliance + Currently don't see a need for a compliance update, only if we will be ontime with the Weston 6.0 update , we should bump up the reference implementation version, but there will be no interface change Best regards Eugen Friedrich Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6921 > -----Original Message----- > From: genivi-ivi-layer-management <genivi-ivi-layer-management- > bounces@lists.genivi.org> On Behalf Of Stephen Lawrence > Sent: Montag, 18. Februar 2019 18:10 > To: genivi-ivi-layer-management@lists.genivi.org > Cc: Ejdestig, Martin <MEjdestig@luxoft.com>; > Christian.Schulenberg@bmw.de; gandersson@genivi.org > Subject: Compositor/IVI-Extension component update for meta-ivi 15.0 > (thud) and compliance > > Hi Compositor team, > > In the BIT we are discussing the spring update to the Genivi Baseline and > meta-ivi and I would like to check > your plans for the Compositor component and ivi-extension. > > + Source + > meta-ivi release v14.50.1 was based on YP 2.5 (Sumo) and released in > October 2018. It uses ivi-extension v2.1.0 > and SRCREV = "d2c2e262f3bdc9db33b3014293fcdbcfdc90ab27". > > The current dev cycle for the spring releases will be for meta-ivi release > v15.0.x and based on YP 2.6 (Thud). > The meta-ivi master branch is the working branch for this and has already > been rebased on Thud. > It currently points at the ivi-extension commit SRCREV = > "9acdaa1a9c79558691b1513cc4917f2ced91af8a", > which is up to date except for a series of commits in November updating > EGLWLMockNavigration. > > Can you update the BIT on your roadmap? Do you plan new functionality for > us to adopt for this cycle? > Will a new release be made? Should we adopt the MockNavigation changes? > Do you plan to rebase and merge PR #82? > Can we assume that PR #103 will stay unmerged as an example? > > + Compliance + > Although it will not affect the meta-ivi updates we have been discussing the > next Genivi specification > update with the compliance team. They are looking at what component > updates might be needed. > Do you see a need for a Compositor component specification update? > > Regards > > Steve > BIT Lead > > _______________________________________________ > genivi-ivi-layer-management mailing list > genivi-ivi-layer-management@lists.genivi.org > http://lists.genivi.org/mailman/listinfo/genivi-ivi-layer- > management_lists.genivi.org

Hi Eugen, > -----Original Message----- > From: Friedrich, Eugen (ADITG/ESB) <efriedrich@de.adit-jv.com> > Sent: 01 March 2019 09:04 > To: Stephen Lawrence <stephen.lawrence@renesas.com>; genivi-ivi-layer- > management@lists.genivi.org > Cc: Ejdestig, Martin <MEjdestig@luxoft.com>; Christian.Schulenberg@bmw.de; > gandersson@genivi.org > Subject: RE: Compositor/IVI-Extension component update for meta-ivi 15.0 (thud) and > compliance > > Hi Steve, > > We are planning to use the Weston 6.0 release which not ready now, I'm not when is the > deadline to the 15.0 release but without Weston 6.0 there are no interesting features. > > Weston 6 will bring: > Xdgshell support in ivi-shell (we would be able to merge the pull request 103) > General improvements in Weston > Debug protocol, which can be used to implement better reporting from Weston > core Thanks for the update on the roadmap and particularly the notes on the coming benefits. Something for the autumn release perhaps then if the updates drop, although I see that poky master-next is currently pointing at Weston 5.0 still. Perhaps because Weston 6.0 has not dropped. For this meta-ivi 15.0 spring update cycle we will concentrate on the current code then. > > Mocknavigation update can be ignored it is just an better looking demo, no new > functionality Well we are in a dev and test cycle so I see no problem updating to it/the HEAD. Is there any reason we should be cautious? > > + Compliance + > Currently don't see a need for a compliance update, only if we will be ontime with the > Weston 6.0 update , we should bump up the reference implementation version, but > there will be no interface change OK. Good input to the compliance team. Regards Steve

General improvements in Weston
Debug protocol, which can be used to implement better reporting

Hi Steve, Comments below... Best regards Eugen Friedrich Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6921 > -----Original Message----- > From: Stephen Lawrence <stephen.lawrence@renesas.com> > Sent: Freitag, 1. März 2019 17:38 > To: Friedrich, Eugen (ADITG/ESB) <efriedrich@de.adit-jv.com>; genivi-ivi- > layer-management@lists.genivi.org > Cc: Ejdestig, Martin <MEjdestig@luxoft.com>; > Christian.Schulenberg@bmw.de; gandersson@genivi.org > Subject: RE: Compositor/IVI-Extension component update for meta-ivi 15.0 > (thud) and compliance > > Hi Eugen, > > > -----Original Message----- > > From: Friedrich, Eugen (ADITG/ESB) <efriedrich@de.adit-jv.com> > > Sent: 01 March 2019 09:04 > > To: Stephen Lawrence <stephen.lawrence@renesas.com>; genivi-ivi-layer- > > management@lists.genivi.org > > Cc: Ejdestig, Martin <MEjdestig@luxoft.com>; > Christian.Schulenberg@bmw.de; > > gandersson@genivi.org > > Subject: RE: Compositor/IVI-Extension component update for meta-ivi 15.0 > (thud) and > > compliance > > > > Hi Steve, > > > > We are planning to use the Weston 6.0 release which not ready now, I'm > not when is the > > deadline to the 15.0 release but without Weston 6.0 there are no > interesting features. > > > > Weston 6 will bring: > > Xdgshell support in ivi-shell (we would be able to merge the pull > request 103) > > General improvements in Weston > > Debug protocol, which can be used to implement better reporting > from Weston > > core > > Thanks for the update on the roadmap and particularly the notes on the > coming benefits. > Something for the autumn release perhaps then if the updates drop, > although I see that poky > master-next is currently pointing at Weston 5.0 still. Perhaps because > Weston 6.0 has not dropped. > > For this meta-ivi 15.0 spring update cycle we will concentrate on the current > code then. > > > > > Mocknavigation update can be ignored it is just an better looking demo, no > new > > functionality > > Well we are in a dev and test cycle so I see no problem updating to it/the > HEAD. Is there any reason > we should be cautious? [EF] our current head has already a patch to work with Weston 5.0!! So if you still on Weston 3.0 or in general below 5.0 don't use head of wayland-ivi-extension > > > > > + Compliance + > > Currently don't see a need for a compliance update, only if we will be > ontime with the > > Weston 6.0 update , we should bump up the reference implementation > version, but > > there will be no interface change > > OK. Good input to the compliance team. > > Regards > > Steve

Hi, > -----Original Message----- > From: Friedrich, Eugen (ADITG/ESB) <efriedrich@de.adit-jv.com> > Sent: 04 March 2019 08:27 > To: Stephen Lawrence <stephen.lawrence@renesas.com>; genivi-ivi-layer- > management@lists.genivi.org > Cc: Ejdestig, Martin <MEjdestig@luxoft.com>; Christian.Schulenberg@bmw.de; > gandersson@genivi.org > Subject: RE: Compositor/IVI-Extension component update for meta-ivi 15.0 (thud) and > compliance > [snip] >> > Mocknavigation update can be ignored it is just an better looking demo, no >> new >> > functionality > > Well we are in a dev and test cycle so I see no problem updating to it/the > > HEAD. Is there any reason > > we should be cautious? > [EF] our current head has already a patch to work with Weston 5.0!! > So if you still on Weston 3.0 or in general below 5.0 don't use head of wayland-ivi- > extension ok. Poky meta is on Weston 5.0 of course so I expect we will take the head and the new mocknav then. I'll be doing some Thud builds of meta-ivi on R-Car Gen 3 this week so I can try it out and send a meta-ivi PR. Regards Steve