56 replies to this topic

[A.A.]

The final target is to have just a kodi_git.bbappend in OpenPLi.

To do this we have first to add meta-kodi layer and wait/work to have that in OE one day.

 

Immediate steps are:

 1 - more logic in the kodi recipe to add specific patches

 2-  move the EXTRA_OECMAKE_append_pn-kodi to the BSP layer.

 

This second step should be done possibly in parallel and sourcing from OpenPLi.

Now the problem: we have different definitions between OpenPLi and OE-A.

 

What here is

 

EXTRA_OECMAKE_append_pn-kodi = " -DWITH_V3D=nxcl"

there is

 

EXTRA_OECMAKE_append_pn-kodi = " -DWITH_V3D=nxclient"

 

and so on (more fiffs)

 

What is the right way to put that in the BSP? Mimic OE-A?

 

 

The final step is to actually build kodi for the machines having it in MACHINE_FEATURES and this is another round of BSP updates.

 

Please let me know, thx

A.A.

[WanWizard]

I personally have no problem syncing these things with OE-A, if that makes life easier for everyone.

[A.A.]

Oops, the issue is a bit different:

 

their stb patch uses

EXTRA_OECMAKE += " \ -DWITH_PLATFORM=GB-cortexa15 \ -DWITH_FFMPEG=stb \

"

While the initial commit in OpenPLi uses DWITH_V3D=.

 

At this point we could send our round of patches.

 

[A.A.]

@WanWizard

we are blocked for now, can you please ask zhtq about the BSP pending pull requests?

thanks

A.A.

[WanWizard]

Was afraid that would happen. We have no clue who this zhtq is or how to reach this person. And gigablue has been unresponsive for months as well...

 

Maybe @Frenske has more options, we'll have to wait until he's back from cow-bell-country .

[betacentauri]

Regarding Gigablue or Octagon changes?

[A.A.]

meta-gigablue

meta-octagon

meta-uclan

 

meta-vuplus was promptly updated

 

This in preparation for one/two rounds of BSP changes...

 

 

What is actually blocking OpenPLi development is https://github.com/z...igablue/pull/10

Edited by A.A., 23 September 2021 - 18:44.

[A.A.]

>What is actually blocking OpenPLi development is https://github.com/z...igablue/pull/10

 

@WanWizard

we can simply (re) add comments for these models and go forth

[WanWizard]

Give Frenske a few days...

[betacentauri]

I have asked the developer to merge these PRs:

https://github.com/z...-octagon/pull/9
https://github.com/z...gigablue/pull/8
https://github.com/z...gigablue/pull/9
https://github.com/z...igablue/pull/10
https://github.com/z...igablue/pull/11
https://github.com/z...ta-uclan/pull/5

@Frenske: I don't know whether the developer reads my message. So better also push (kick ) from other side.

[betacentauri]

All except the meta-uclan PR were merged.
This this not, I don’t know.

[A.A.]

@betacentauri

thanks! the meta-uclan is not blocking.

 

Now what is your opinion about updating the BSP for kodi?

 

Should we do it once for all compatible with PLi and OE-A?

I started with this idea but then I have seen the machine-names differ (see meta-gigablue) so maybe the idea is premature and OE-A will continue to use 'unofficial' BSP's.

 

The key differences are in the patches and have to be translated in the machine conf files in the BSP:

 

https://github.com/o...port.patch#L100

vs

https://github.com/O...-v3d-mali.patch

 

Hints?

Cheers

A.A.

 

 

P.S.

example is  EXTRA_OECMAKE_append_pn-kodi = " -DWITH_V3D=nxpl"

once we have this lines we can remove that from kodi_18.inc

 

second step is to rework/extend with the new tags the SRC_URI in kod_18 recipe, finally cleaning the .inc.

i.e.

${@bb.utils.contains('MACHINE_FEATURES', 'v3d-nxpl', 'file://egl/EGLNativeTypeV3D-nxpl.patch', '', d)} \

 

here if you see PLi patchset does provide pre-cooked EGLNativeTypeSTB.cpp files.

Edited by A.A., 26 September 2021 - 10:45.

[WanWizard]

BSP's are updated in develop.

[Frenske]

I’m back in ‘business’ but I still have to get used to the present daily things in comparison to the things we did in Austria.

[A.A.]

I have asked the developer to merge these PRs:

https://github.com/z...-octagon/pull/9
https://github.com/z...gigablue/pull/8
https://github.com/z...gigablue/pull/9
https://github.com/z...igablue/pull/10
https://github.com/z...igablue/pull/11
https://github.com/z...ta-uclan/pull/5

@Frenske: I don't know whether the developer reads my message. So better also push (kick ) from other side.

 

 

All except the meta-uclan PR were merged.
This this not, I don’t know.

@Frenske

could you please ask zhtq about this single PR still not applied in meta-uclan? Thanks!

[Frenske]

I ‘requested’ my contact to ‘kick’ their developer to accept this PR.

[Frenske]

I already got an answer that my request has been forwarded to the developer. Let’s wait and see how fast he’ll respond.

[A.A.]

Thank you, I have sent another couple of fixes before the big round of changes for kodi.

A.A.

[A.A.]

With the last round I hope to have sent out all necessaries BSP patches.

 

meta-gi and meta-xtrend are already updated

 

Let's wait some days then finally purge our poor kodi recipe.

I imagine it as .bbappend of meta-kodi for next release.

 

A.A.

Edited by A.A., 3 October 2021 - 22:24.

[WanWizard]

I've updated our OE too.