I prepared initial OrangePi 3 support. Initial image can be found here:
libreelec-h6.arm-9.1-devel-20190603225103-f3b379f-orangepi_3.img.gz
Sources can be found here:
GitHub - jernejsk/LibreELEC.tv at aw_linux_patches
Known issues (apart from those in OP):
- ethernet doesn't work after reboot (physical power disconnection is needed, probably PMU related)
- bluetooth doesn't work (probably wrong firmware)
* The Orange PI PC device tree operating points table has only three states, and the fastest is 1.0 Ghz. As far as I remember, the SoC was supposed to run up to 1.5Ghz @ 1.3volts
Yeah, that's mainline issue due to missing temperature monitor driver. 1.5Ghz @ 1.3volts is actually already a overclocking, more like 1.3 GHz would be maximum. Anyway, you don't need any of that extra speed if you watch videos which are HW decoded.
* There is no cpufreq driver built in the kernel. Is it expected?
I have to check that.
* About CEC, there is a Kodi thread that apparently is using a lot of cpu time related to CEC. Doing a strace over it seems to continously scan the /sys directory in search for something and never stops. Maybe there's something missing to let it find the proper CEC device to listen to
Can you check if this is related to tinkerboard: disable 5s polling for CEC adapters by viulian · Pull Request #3506 · LibreELEC/LibreELEC.tv · GitHub ?
I have somewhere an inet97f2 tablet based on A10 with some old fedora on it, should i have a look for it?
You can, but in this case kernel config needs to be tweaked, to enable A10 drivers. You can try it based on my A20 branch here: GitHub - jernejsk/LibreELEC.tv at a20 (check last 3 commits)
However, I think it would be best to fix A20 support first.
I know it's pretty OT but such tablets would also be a target for a completely free mainlined android,
that's still not possible, but should be close. I think lima drivers needs to be improved? I don't really know.
You nicely summed up all known issues. BT2020 will be hard to implement - display and VPU drivers are missing BT2020 support for now. Currently all 10-bit HEVC videos are decoded as 8-bit.
Regarding audio, this is outside my expertise, but I'll take a look into it once.
I'll try to dig one out. It may have been a 10bit HVEC
That's possible to decode only on H6 and even then only with my WIP patches. What about videos not filling screen? Sample for that would be appreciated too.
"Green screens" on some HVEC videos
can you provide sample video?
Here is test image for PineH64 with working 10-bit H265 (HEVC) decoding and HDR output:
Build from:
GitHub - jernejsk/LibreELEC.tv at hdr
I suggest you put it on separate SD card because it will took some time before all needed patches land in LE master. I wonder how well it works for you.
Any chance of adding a build for the NanoPi M1?
Yes, but note that only version with 1 GiB of RAM will be supported. If you have 512 MiB version you can still use same image, but I don't accept bug reports which occurs due to memory consumption. Which version do you have?
I'm only surpised that H5 is missing here. Is there any reason for it?
Yes, it is. It has different GPU than any other SoC. Even drivers from other companies which use same GPU are not compatible with it. Workaround exist, but adds additional processing for every image rendered, which is far from ideal. This platform waits on Lima to become good enough to be used instead of binary drivers.
Two additional problems were observed - HDMI CEC is not working at all and image is unstable (freezes), maybe because of GPU driver hack or maybe RAM driver issues or maybe something else entirely.
I have also one old image LibreELEC-A64.arm-9.0-devel-20181220210336-147ea78-pine64_plus and this one works fine
This works because it is correct image for your board - note the "plus" in it's name. For some reason nightly image for Pine64 Plus isn't copied to download server (similarly as OrangePi Plus2E).
Due to a lot of problems with nightly builds, I'll probably build images now and then and linked it in OP.
2. The second one was converted from MPEG4 to HEVC1 with default parameters. After trying to play it, the sound starts to play and the system immediately reboots.
Kwiboo solved mystery with your video sample. It won't crash with very latest Kodi, but unfortunately, LE build system uses a bit old version. Not sure when will it be updated. However, it still won't be correctly decoded (blank screen). Your video uses RGB color space in GBR format (just color order is changed), which is not supported by Kodi's DRMPRIME renderer nor with HW video output. To properly display it, additional work on Kodi and maybe also on display driver is needed.
It's strange that default conversion used RGB color space. YUV is much much more common.
I prepared H264 and H265 (HEVC) fixes in this branch: GitHub - jernejsk/LibreELEC.tv at aw_linux_patches
I'm waiting on some patches to be accepted to Linux before I make PR to LE github, but just for information on what I work on:
- all known H264 issues fixed
- H265 decoding improvement
- 10-bit H265 decoding on H6 fixed
If anyone wants to test that, please build image yourself. Otherwise wait until PR is prepared and accepted.
BTW, I'll get OrangePi 3 shortly, so support for it will also added soon. Initial H6 HEVC 10-bit HDR test was also successful, but that won't be added soon.
why image plus2e missing again?
I don't know, I don't have access to that part of infrastructure. I'll ask.
Someone want to install to emmc? If someone want it, i will be introduced step by step
You mean how to dd image to eMMC or something else?
Works in tanix tx6?
Talk about Tanix TX6 is here: Nightly images for A64, H3 and H6 boards
I noticed that when the TV where the Orange PC is connected is turned off, rebooting is not successful.
How do you reboot board?
Is it a CEC problem?
When TV is turned off it sends CEC message to board, which should also turn off. But there might be a bug regarding that. You should be able to disable that in settings somewhere. Similarly, if you power on OrangePi PC when TV is off, TV should automatically turn on when Kodi is fully booted.
ukmark62 I extracted Android DTB and decompile it. You can find it here: http://sprunge.us/ulpcla Don't worry, at least 90% of info there won't be needed.
Regarding UART, yes, that should do it. Just be careful not to fry anything when you're probing for possible RX/TX/GND pins.
ukmark62 First of all, I suggest you find serial port on the board and connect it. Maybe you can find how-to on the internet or you'll have to do it hard way to find it by yourself. I'm sure correct settings for it are 115200 8N1 (I haven't seen different settings on any AW board/box).
Then we'll need DTB from Android. There might be way to extract it from running system, but I usually extract it from Android update file.
These two steps are pre-requirement for later U-Boot and Linux configuration and testing.
ukmark62 At least someone started on supporting DDR3 here: https://github.com/apritzel/u-boot/commits/eachlink-h6-mini-wip So we would need just find the bugs and fix them.
