Amlogic-ne, New Era

[hungphutho]

@Portisch

S4 S905Y4, S905W2

i tested on s905w2 , hardware video decoding does not work .
Generic Amlogic Device , device tree S4
log http://ix.io/4cNZ

[  224.548252@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.548873@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.549516@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.550115@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.550701@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.551273@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.551844@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.552413@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.552703@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.553319@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.553928@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.554521@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.555114@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.555707@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.556315@3]  0: MH264 the TEE fw loading failed, err: ffff0007
[  224.556649@3]  0: MH264 the TEE fw loading failed, err: ffff0007

[Portisch]

ok, thx. we missed this part. it will be included in next nightly

[clarkss12]

Right now, I am playing a movie with the “enable debug logging” enabled. I will post the log when the box locks up.

I have another issue regarding the IP address. It has changed the IP address twice since I installed the new NE version.

[freddy]

Just starting to Test NE
Hk1x4 4/32
Rtl 8211f

Ethernet working
Issues with wifi…
Strange Blutooth is working on s905x4

Have yet to config remote
And vfd

More testing

Happy Testing

[clarkss12]

VFD is working perfectly. Have not used the stock remote.

[Blackie]

Amlogic, I believe that the expensive flagship S922x CPU deserves to be added support for the 5.4 kernel.
Maybe if a new device with official DolbyVision support appears I will upgrade but until then I wait.
But I understand the development must go on so good luck with the new-era chips support.

[bhf]

And where - do you think - will this support come from, if and when AMLogic decides to drop its support for the S922 SoC? Nexus isn’t even beta yet, so you have at least three years of support still to come.

[Portisch]

@hungphutho you need to give me more information. What dtb you exactly used?
How many ram do your device have? 1GB?

Because S905W2 is same structure S4 like S905Y4, so the firmware should already be included and working.

[hungphutho]

@Portisch

How many ram do your device have? 1GB?

Tx3 Mini Plus S905W2 RAM 4G / s4_s905y4_4g.dtb
Tanix W2 S905W2 RAM 2G / s4_s905y4_2g.dtb
i have both devices , same result

 MH264 the TEE fw loading failed, err:

[Portisch]

You can try systemctl mask opentee_linuxdriver.service then reboot

[hungphutho]

I tried .
does not solve the problem “TEE”

[hungphutho]

CoreELEC:~ # fw_printenv | paste
http://ix.io/4d3Z

[Blackie]

Sry, but I don’t understand your question. Companies like Hardkernel can help with S922 long-term support but here we care for future CE versions.
My argument was that S922x/A311D as expensive flagship SoC deserves longer official support. It has all the performance we need for KODI now and after Nexus.
Question is why AML promised to support cheap S905X3 in the new kernel if it’s tech.level is the same and performance is worse? It just doesn’t make sense to me…

[Tim_Taylor]

@Blackie

S922 long-term support

How long ?
10 years
50 years ?

You can use any S922 device a few years
My old S905X devices are runnig old kernel without any issues as daily driver.
My N2 will run next five years, so what

[Portisch]

Because the hardware structure changed with G12A (SM1) and it changed again a lot with SC2. And it’s hard to support both hw structures within one kernel. So don’t touch the already working code and implement only new hardware structures in new kernel.

You need to see this as complete “package”. AML sell dev board + SoC + sw, ready for the vendor to implement his own design. There is no reason for AML to change a part of this package. It’s just easier for them. When the user choose another SoC he get another “complete package”. But every part is tailored to the others.

AML want to sell the new stuff, not the old ones. So there is really no reason for them to port the old hw to new sw. It’s kind of their business strategy.

So right now it looks like using SoC till SM1 will use 4.9. Since SM1 5.4.

[Blackie]

Thank you for the explanation. As expected the reasons are mainly business-related.
Which is a bit sad but what can we do, buy a box with new Rockchip SoC with promised mainline support?
I don’t believe they can deliver KODI experience on par with AML, no real alternative.
I’ll wait for improvements the new NE platform can bring(AV1, NPU?, DV?) whether they convince me to upgrade (or stay on Nexus version).

[emveepee]

If all you want is mainline support and not CoreElec AML enhancements maybe just try LibreElec. That doesn’t mean LE will keep it going until Kodi 21 either.

[Blackie]

No I don’t, and have never said that.
Mainline just came to my mind as one (unfortunately not realistic) way how to get long-term kernel support without paying every few years for a new device with similar performance…
My history is S905, S905X, S905D, S905X3, S922X(2x) and don’t like the idea that show must go on…