Jump to content


Photo

kodi_18 patchset for STB


  • Please log in to reply
56 replies to this topic

Re: kodi_18 patchset for STB #21 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 11 August 2021 - 15:06

Some of the active ones will. Some won't respond at all.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #22 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 11 August 2021 - 15:09

Please let finish the list of supported devices/drivers in kodi_18.inc as first.

 

Isn't that a simple search for all BSP's that provide "virtual/libgles" ? Or is there more to it?
 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #23 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 11 August 2021 - 16:32

 

Please let finish the list of supported devices/drivers in kodi_18.inc as first.

 

Isn't that a simple search for all BSP's that provide "virtual/libgles" ? Or is there more to it?
 

 

seems so, as for starting point.

 Feel free to let all commented as first.



Re: kodi_18 patchset for STB #24 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 11 August 2021 - 17:10

Here you go ;)

./meta-abcom/recipes-bsp/mali/abcom-mali-utgard.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-abcom/recipes-bsp/mali/abcom-mali-pulse4k.bb:require abcom-mali-utgard.inc
meta-abcom/recipes-bsp/mali/abcom-mali-pulse4kmini.bb:require abcom-mali-utgard.inc

./meta-axasuhd/recipes-bsp/drivers/axas-libgles.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-axasuhd/recipes-bsp/drivers/axas-libgles-e4hd.bb:require axas-libgles.inc

./meta-edision/recipes-graphics/libv3d/libv3d.inc:PROVIDES = "virtual/libgles2 virtual/egl"
meta-edision/recipes-graphics/libv3d/libv3d-osmini4k_2.0.bb:require libv3d.inc
meta-edision/recipes-graphics/libv3d/libv3d-osmio4k_2.0.bb:require libv3d.inc
meta-edision/recipes-graphics/libv3d/libv3d-osmio4kplus_2.0.bb:require libv3d.inc

./meta-edision/recipes-graphics/v3d-libgles/v3d-libgles-osmega_1.0.bb:PROVIDES = "virtual/libgles2 virtual/egl"

./meta-gfutures/recipes-bsp/drivers/hd-v3ddriver.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-gfutures/recipes-bsp/drivers/hd-v3ddriver-hd2400.bb:require hd-v3ddriver.inc
meta-gfutures/recipes-bsp/drivers/hd-v3ddriver-hd51.bb:require hd-v3ddriver.inc
meta-gfutures/recipes-bsp/drivers/hd-v3ddriver-vs1500.bb:require hd-v3ddriver.inc

./meta-gfutures/recipes-bsp/mali/hd-mali-utgard.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-gfutures/recipes-bsp/mali/hd-mali-hd60.bb:require hd-mali-utgard.inc
meta-gfutures/recipes-bsp/mali/hd-mali-hd61.bb:require hd-mali-utgard.inc

./meta-gi/recipes-bsp/libgles/nextv-v3ddriver.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-gi/recipes-bsp/libgles/nextv-v3ddriver-et1x000.bb:require nextv-v3ddriver.inc

./meta-gigablue/recipes-bsp/recipes-graphics/libgles/gb-v3ddriver.inc:PROVIDES = "virtual/libgles2 virtual/egl"
COMPATIBLE_MACHINE = "gbquad4k|gbue4k"

./meta-gigablue/recipes-bsp/recipes-graphics/gigablue-opengl.inc:PROVIDES = "virtual/libgles1 virtual/libgles2 virtual/egl"
meta-gigablue/recipes-bsp/recipes-graphics/gigablue-opengl-gbtrio4k.bb:require gigablue-opengl.inc

./meta-maxytec/recipes-bsp/mali/maxytec-mali-utgard.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-maxytec/recipes-bsp/mali/maxytec-mali-multibox.bb:require maxytec-mali-utgard.inc
meta-maxytec/recipes-bsp/mali/maxytec-mali-multiboxse.bb:require maxytec-mali-utgard.inc

./meta-octagon/recipes-graphics/octagon-opengl.inc:PROVIDES = "virtual/libgles1 virtual/libgles2 virtual/egl"
SF8008, SF8008M

./meta-qviart/recipes-bsp/drivers/v3d-libgles-qviart.inc:PROVIDES = "virtual/libgles2 virtual/egl"
LUNIX4K, LUNIX3-4K

./meta-uclan/recipes-graphics/uclan-opengl.inc:PROVIDES = "virtual/libgles1 virtual/libgles2 virtual/egl"
meta-uclan/recipes-graphics/uclan-opengl-ustym4kpro.bb:require uclan-opengl.inc

./meta-vuplus/recipes-bsp/drivers/libgles.inc:PROVIDES = "virtual/libgles2 virtual/egl"
meta-vuplus/recipes-bsp/drivers/libgles-vuduo2.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vuduo4k.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vuduo4kse.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vusolo2.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vusolo4k.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vusolose.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vuultimo4k.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vuuno4k.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vuuno4kse.bb:require libgles.inc
meta-vuplus/recipes-bsp/drivers/libgles-vuzero4k.bb:require libgles.inc

./meta-xtrend/recipes-bsp/libgles/et-v3ddriver.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl"
meta-xtrend/recipes-bsp/libgles/et-v3ddriver-et10000.bb:require et-v3ddriver.inc

./meta-zgemma/recipes-bsp/drivers/zgemma-v3ddriver.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl virtual/libgbm"
meta-zgemma/recipes-bsp/drivers/zgemma-v3ddriver-h7.bb:require zgemma-v3ddriver.inc

./meta-zgemma/recipes-bsp/mali/zgemma-mali-utgard.inc:PROVIDES = "virtual/libgles2 virtual/libgles1 virtual/egl virtual/libgbm"
COMPATIBLE_MACHINE = "^h9$|^h9se$|^h9combo$|^h9combose$|^h10$|^i55plus$|^i55se$"
COMPATIBLE_MACHINE = "^h11$"

 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #25 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 14 August 2021 - 18:16

I am building for those models, WIP.



Re: kodi_18 patchset for STB #26 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 14 August 2021 - 19:27

I'll currently looking into kodi dependencies. For some reason it compiles at every build run, adding 40min+ per box, which is not acceptable.

 

One of the issues was that Kodi was build for TUNE_ARCH, while some boxes have EGL drivers built for MACHINE_ARCH. Fixing this has reduced the problem, but it's not gone yet.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #27 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 14 August 2021 - 21:49

What I see is samba rebuilding too often, even with only two arm tunes

 

all-oe-linux

armv7vehf-neon-vfpv4-oe-linux-gnueabi

cortexa15hf-neon-vfpv4-oe-linux-gnueabi

e4hd-oe-linux-gnueabi         

osmini4k-oe-linux-gnueabi

osmio4k-oe-linux-gnueabi

osmio4kplus-oe-linux-gnueabi

pulse4k-oe-linux-gnueabi
pulse4kmini-oe-linux-gnueabi

x86_64-linux
 



Re: kodi_18 patchset for STB #28 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 14 August 2021 - 21:54

That would be odd, samba is build from a tarball with a fixed PV. If that changed you'd immediately see checksum issues.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #29 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 14 August 2021 - 23:03

I am now at meta-edison in your list and samba was rebuilt 3 times for armv7vehf-neon-vfpv4-oe-linux-gnueabi and 3 for cortexa15hf-neon-vfpv4-oe-linux-gnueabi. Just cheking do_compile logs.

 

Please pin it for to-do, let finish kodi now.



Re: kodi_18 patchset for STB #30 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 15 August 2021 - 00:58

Just checked the currently running develop build, no samba in the logs, and the kodi rebuild seems to be triggered by a rebuild of ffmpeg, which had a bug fix a few days ago.

 

We'll see what happens if this run is finished and I start it again. I need this fixed, 8.1-release is overdue, and I've got a week left until I go offline for a while...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #31 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 15 August 2021 - 18:23

I see you're in hurry with 8.1.

 

I sent a first patch for kodi, adding 'mali-cortexa15'.

It is not that easy to extend to all machines because some are challenged (as Vu+) anfd need a support-package.

 

OE-A does that in the old way:

https://github.com/o...4kpro_19.bb#L23

 

So there is first to find the correct matching cpu-v3d drivers, we can peek at OE-A for this, but the naming differs.

 

I try to add quickly more devices but be warned I cannot test at runtime.

A.A.



Re: kodi_18 patchset for STB #32 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 15 August 2021 - 19:12

For me, kodi is not on the critical path for 8.1.

 

8.1 is needed urgently because we can't build 7.3 and 8.0 anymore (due to server hardware errors we've lost the PR databases for both).


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #33 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 15 August 2021 - 19:33

no, it's not critical. Some devices just get an unoptimized build (maybe not running).



Re: kodi_18 patchset for STB #34 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 16 August 2021 - 17:13

I have added the missing bits, mostly for mali, and commented about BSP status.

Surely a cleanup and some fixes will be needed.

 

The kodi recipe does some black-magic when hisil or v3d-nxpl are found in MACHINE_FEATURES.

Maybe we could extend that mechanism (see meta-gi notes).

 

Cheers

A.A.


Edited by A.A., 16 August 2021 - 17:15.


Re: kodi_18 patchset for STB #35 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 20 August 2021 - 12:45

For the testers: in PR #1035 mali support is added.



Re: kodi_18 patchset for STB #36 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 20 August 2021 - 13:49

Seen it.

 

I'm waiting with the merge to keep develop stable at the moment, as 8.1-release is being built, and develop may be needed to fix issues.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #37 Taykun345

  • Senior Member
  • 1,297 posts

+41
Good

Posted 22 August 2021 - 08:05

Whats the deal with Kodi on duo4k? It starts now but using default E2player videos are not being played. Using videoplayer videos work but stuttering (software decoding).

Any setting fix or is this intended behavior for now?

Sent from my moto g 5G plus using Tapatalk
Army MoodBlue HD skin modification by me: https://github.com/T...-MoodBlueHD-mod
Matrix10 MH-HD2 skin modification by me: https://github.com/B...-MX-HD2-OpenPli
MetrixHD skin modification by me: https://github.com/T...xHD-WPstyle-mod
Slovenian translation for OpenPLi E2: https://github.com/T...ion-for-OpenPLi

Re: kodi_18 patchset for STB #38 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 30 September 2021 - 21:53

Update: with today's patches we use the same definitions as in OE-A.

 

There are surely more refinements to do (cortexa15 optimizations?)

Once we have the BSP's in sync we'll go further.

 

Any help is appreciated.

thanks

A.A.



Re: kodi_18 patchset for STB #39 WanWizard

  • PLi® Core member
  • 68,605 posts

+1,739
Excellent

Posted 30 September 2021 - 22:19

I wish I could, what you're doing is still magic to me... ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: kodi_18 patchset for STB #40 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 1 October 2021 - 18:43

We are at the last step: push all the build/runtime customisations in kodi_18.inc into the BSP's.

 

To create the packages in the feeds we need one of these two:

 

${@bb.utils.contains('OPENPLI_FEATURES', 'kodi', 'enigma2-plugin-extensions-kodi kodi-addons-meta', '', d)} \
${@bb.utils.contains('MACHINE_FEATURES', 'kodi', 'enigma2-plugin-extensions-kodi kodi-addons-meta', '', d)} \

 

As far as I see OPENPLI_FEATURES is not so widely used

 

meta-octagon/conf/machine/sf8008m.conf:OPENPLI_FEATURES += " qtplugins"
meta-octagon/conf/machine/sf8008.conf:OPENPLI_FEATURES += " qtplugins"
meta-axasuhd/conf/machine/e4hd.conf:OPENPLI_FEATURES += " ci qtplugins kodi"

Should we use this or (preferred) MACHINE_FEATURES?

 

Cheers

A.A.
 




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users