In any case shutting down as well as restarting kodi is very slow
The very slow shutting down feature is also available on the rockchip and amlogic devices not exclusively for H3
In any case shutting down as well as restarting kodi is very slow
The very slow shutting down feature is also available on the rockchip and amlogic devices not exclusively for H3
About KVIM1
I tested the latest nightlies on my KVIM1. I just dd the KVIM-image to emmc, I only read later it should be done with the emmctool, but it boots fine. Now when I test some local streaming services (VRT-NU and VTM GO) the screen is shaking a lot, including the control panels and the video hangs.
Local video's start but without screen. When I stop them the system freezes.
Here is thelog: http://ix.io/2NDN but it seems it stopped logging at some point.
Another problem, but already known probably, is that it takes ages to shut down the system (I have this also on my RK3328).
The name of the images contains rk3328-roc-pc
Stupid of me, I should have seen that
For M1, I release special images LE (arm and aarch64)
Yes, I read that in the forum of firefly, but You didn't put the link to the LE images, only to the Armbian image. So can you provide the link to the LE images?
it's a Station M1. I test it, it works OK, I had to use the dtb from the firefly ROC-RK3328-PC as the Station M1 is in fact a ROC-RK3328-PC with a shell.
I will test this evening a 32-bit image as widevine is not available for 64-bit. I will see how it works out.
Sorry, I made a typo, the M1 is indeed a RK3328. Nevermind, I will take a rk3328 image, burn it to SD and then burn the M1 u-boot to the sd-card. I will see what it does.
I read your explanation about the Station M1 on the firefly forum. There you speak about linux mainline builds for the M1. So if I understand correctly, I just have to use one of your rk3228 testbuilds and burn the u-boot from the firefly forum to the sd-card?
As I understand, DT-overlays should be used to add are change properties in the device tree. So, if I understand this correctly, it shiould activate properties from add-on boards, for example a DAC or Wifi board as available for pine64. So in this case, it should be good to add support for the wifi board and also the audio pot board on the pine64 boards .
I have time
I'm glad some people still have the motivation to put some new life in older hardware.
If I could help I would, but I don't understand a thing about making device trees. I once started reading the documentation, but I have zero background, so it's all chinese to me.
If I find another wetek core, I will contact you regarding Martin's adress.
Just test it on my M8S. Boots fine with the mxIII-plus dtb, but not with the M8S dtb.
Could test further as it seems I got a overload on the usb ports and now the usb doesn't work anymore. I hope there is some kind of overcurrent protection on this box, so when it's cooled down, it works again.
Regarding the wetek core. It seems there is no dtb for the wetek core in mainline.
Edit: My usb-ports don't work anymore...
It's a s812. I asked because this thread is for MIII-plus. So the dtb should match. Or can we select the appropriate dtb?
great news, should it work on the wetek core also? If not, is the sourcecode available on github, so we can build it ourselves?
You are correct. I think I'm getting crazy. I downloaded the latest kernel from github and unpacked it, I can't remember I patched it. But it seems I did. Time to go to sleep.
I just checked them in 5.10 and it seemed they where already there. Patch 01 is according me from line 1190 until line 1220 and patch 02 is on line1146 in sun50i-a64.dtsi
EDIT: my fault, seems my kernel was already patched. Just checked the kernel sources on github.
is it possible some patches are deprecated?
I'm talking about patch 01 and 02 frome here:
Is there a libreelec branch where we can find the necessary stuff to build test images for S805/S812? Or is there still to much hacking involved?
I'm interested in this inet1 stuff. The problem is with these tablets is that you should know which protocol the display is using. This should be defined in the dts to get it working. I don't have the knowledge to create such a dts, so a example of a working dts for a tablet would be a good starting point.