56 replies to this topic

[Frenske]

I contacted Uclan again as IMHO no action is seen.

[A.A.]

@Frenske

thanks, it would be nice to have all done in a few days.

 

I will check again this evening, I've already seen a missing patch for meta-gi (OPENPLI_FEATURES += "kodi").

 

@WanWizard

basically all BSP were using OPENPLI_FEATURES for kodi so I did it in the same way.

Once finished you can decide.

 

Cheers

A.A.

[WanWizard]

I can live with that, "kodi" is not a MACHINE_FEATURE (i.e. it is not a hardware related feature, it is an application).

 

What is currently in the pipeline, or is still coming?

 

I would like to do another update of 8.1-release to fix some issues, but I don't want to end of with a broken Kodi in the release image.

[A.A.]

I am looking for possible neon/cortexa15 optimizations, like OE-A seems trying to do.

 

For you to build the feeds, as long as we keep the BSP stuff in kodi_18.inc all should build as before.

Once the BSP have applied the patches we can clean the .inc.

 

In the inc will remain for the moment the SRC_URI/patches for

- kodi on vuduo4k/4kse

- old headers patch -> also BSP fixes

 

and the INSANE_SKIP_${PN}_ which *could* be settled with one generic line in the .bb (I would prefer to have the BSP fixed).

Once this kodi_18.inc is empty we are done for 8.1.

 

For hardknott we'll have to move to kodi_19 and this will be easy enough.

I would add meta-kodi -> hardknott and replace our kodi_19.bb with a .bbappend.

(and the broken p8platform/kodiplatform recipes)

So basically kodi will NOT BE in meta-openpli,  like other big recipes like samba, browsers, etc.

 

A.A.

Edited by A.A., 4 October 2021 - 13:29.

[WanWizard]

Ok, thanks.

[rantanplan]

Kodi 18 is no problem for hardknott.
Works already now.

After the changes that have been made so far, you should take a look at the directfb vu +.
Otherwise this leads to errors in the rebuild.

[A.A.]

Ok, I'll take  a look.

 

About kodi 19 it looks like it is required to support latest inputstream helpers / widevine.

In meta-kodi in the hardknott branch there is only _git (19.1) so once we switch to meta-kodi we must upgrade.

 

That for the sake of simplicity

[rantanplan]

For hardknott only webkit from vu + is a problem.
So hhbtv things. I don't think VU + will fix this, so you would have to consider your own other solutions.
Or rather gratefully take over solutions from OE-Alliance.

 

The image is already running perfectly from the hard knot branch.
But some adjustments to busybox and Samba are certainly still desirable.
That’s image starts up faster than before.

[rantanplan]

Widevine has already been patched (glibc), thanks to OE-Alliance and ATVCaptain.
This also works with Kodi 18.

So you could definitely continue with Hardknott, first step in python2 and Kodi 18.
If at some point python3 e2, then of course switch to kodi 19.

Edited by rantanplan, 4 October 2021 - 14:20.

[WanWizard]

For hardknott only webkit from vu + is a problem.
So hhbtv things. I don't think VU + will fix this, so you would have to consider your own other solutions.
Or rather gratefully take over solutions from OE-Alliance

 

The problem with this is that all HbbTV solutions as added to the BSP by vendors are closed source, as they are using software under license (which is probably also why is has never been updated since).

 

OE-A uses a ripped solution from one of the vendors, patched to work on all boxes. As that violates licenses, it is against our policies.

[A.A.]

@rantanplan

excellent news, kodi_18 has long to go.

 

Still...the actual kodi-ecosystem is horrible (p8platform/kodiplatform) and does not allow correct rebuild from sstate afaik.

Not a major hassle anyway.

[rantanplan]

 

For hardknott only webkit from vu + is a problem.
So hhbtv things. I don't think VU + will fix this, so you would have to consider your own other solutions.
Or rather gratefully take over solutions from OE-Alliance

 

The problem with this is that all HbbTV solutions as added to the BSP by vendors are closed source, as they are using software under license (which is probably also why is has never been updated since).

 

OE-A uses a ripped solution from one of the vendors, patched to work on all boxes. As that violates licenses, it is against our policies.

 

I am aware of this discussion.

But the question is, which licenses are you talking about?
The webkit is open source.
Edision has shown it long ago and if you want to move away from qt5.9 and consistently follow the Hardknott branch, then this feature must be deactivated in the VU + receiver in order to build the image.
The question is how to go about it.
I don't even know if hbbtv is still running properly at vu + in the current branch.
It is certainly not a perfect solution.

[WanWizard]

HbbTV itself (which is a compiled javascript app that extends the HTML language with custom tags) isn't.

 

For the 4K boxes, VU+ has switched to Chromium (but again with a closed source HbbTV component), but that hasn't worked for a long time (I assume due to changes in our Enigma which it needs to interface with).

[rantanplan]

This is due to the update of the zeus branch.
In principle, you would have to reset the qt for vu + or create an extra downgraded Branch.
This is how OE-Alliance does it too.
This does not make much sense for further updates in the direction of Hardknott.
It no longer works anyway?
So you should part with it.
Then one could in any case already be thinking in the direction of Hardknott.

[WanWizard]

Most likely, VU+ itself has never updated their OE, they're still using something from 2013 or so...

 

Nobody ever looked at it, as I don't use it (no HbbTV in my country) and I don't really have the correct debugging skills.

[rantanplan]

It's relatively simple.
The basis of the solution is based on qt5.9. All further updates result in an unusable plugin hbbtv
Conversely, you cannot fix a qt branch until further notice because of a plugin (regardless of the closed source).
openhbbtv is the better way anyway and it needs the updates.

[Frenske]

Uclan received this reply from the Chinese maintainer of the BSP.

I have answer from engineers, they wrote that in China holidays now till 7 of October.

[A.A.]

We are again off-topic but my 2 cents here: if hbbtv is broken please remove it.

In my country it is already at 3.x (raiplay) so no plugin is working (well, kodi-plugins do).

A.A.

Edited by A.A., 4 October 2021 - 21:03.

[rantanplan]

meta-openpli/recipes-mediacenter/kodi/kodi_18.bb: Variable key RDEPENDS_${PN} ( vuplus-kodi-vuduo4k) replaces original key RDEPENDS_kodi ( vuplus-kodi-${MACHINE})

 

[A.A.]

meta-openpli/recipes-mediacenter/kodi/kodi_18.bb: Variable key RDEPENDS_${PN} ( vuplus-kodi-vuduo4k) replaces original key RDEPENDS_kodi ( vuplus-kodi-${MACHINE})

yes, meta-vuplus is updated and kodi_18.inc is redefining the variable

 

We are in the middle of the changes...

Edited by A.A., 5 October 2021 - 14:10.