As long as it is IR related, it's fine IMO.
Posts by jernej
-
-
I know, I own the board. However, Linux rule is that if something is missing, it's not enabled. Sockets/headers don't count. So just add above lines and it should work.
-
Neither wifi nor IR receiver are present on Pine64+ board by default. Did you add any of them by yourself? If so, you should activate them via DT overlays first. Just add FDTOVERLAYS /overlays/sun50i-a64-ir.dtbo /overlays/sun50i-a64-pine64-wifi-bt.dtbo to extlinux/extlinux.conf on FAT32 partition.
-
No, issues are not the same. 4K 10-bit decoding works, but as I said, colours are not 100% correct, because it's rendered as 8-bit. I'm working on this.
I doubt you'll find any 1 GB RAM H6 box. Lowest specs are 2 GB and that's already enough. Note that most boxes use 100 Mbit ethernet for some reason. Also worth considering is wifi. Most chips are not supported, but at least for 3 most popular modules, drivers are WIP. Last but not least, only 2 distinct H6 boxes are supported by LE - Tanix TX6 and Beelink GS1. Most of cheap boxes on market will be compatible with Tanix TX6 image. However, they will probably have different IR remote keymap, which will make them impossible to wake from sleep via IR and of course, you'll have to set up your own IR keymap for navigating.
-
hieppo At this time, very well. Recently, two HEVC fixes were merged, which will land in LE 10.0.2. However, HEVC already decodes correctly for me, even without those two fixes.
What are your requirements? Note that 10-bit HEVC also works, but it's decoded and rendered as 8-bit. I'm working on this, but it will take a while to make whole pipeline 10-bit.
-
-
Freeman I just updated images based on latest 10.0 stable branch. I think Kodi had some TrueHD fixes, so please test if it helps.
-
Only x86 based images include X and even there X is on it's way out (HDR is not possible to implement with X afaik). So no, you can't run X app, unless you create custom image with X included. But that will probably bring another set of problems.
-
do you see the vendor-specific ARM-based stuff as the 'future' of Kodi?
LibreELEC migrated from vendor specific codebase (RaspberryPi, Amlogic) to mainline. So this is past, not future.
-
Wake on LAN isn't supported on Allwinner boxes, right?
As far as I'm aware, it's not. You can ask smaeul what would be needed to implement it in Crust.
-
Still trying to figure out my low library scan issue and saw this is being posted to dmesg every few seconds
There are few ways you can check what is going on. With top try to determine which process takes most CPU time. I guess Kodi, but you never know. Next, you can check perf top, which will tell you which functions currently take most CPU time. This should give good pointer where to look next.
dw_hdmi_cec_hardirq: stat=11 LOW_DRIVE
Is this relevant?I don't think this should cause any issue. Actually, I'm thinking of removing that message or even whole patch, which introduced it. But yes, it's not ideal to have it. Are you testing this with monitor or TV? If on TV, toggle CEC state in TV settings (on <-> off). Note that TV manufacturers usually use different name for CEC, like simplink, viera link, etc.
-
Side note: only 4K (4000x2250) movie was to slow. Music was correct but video was slow, hanging and jumping. For me that is no issue, as I don't have a 4K TV anyway.
Ordinary 8-bit 4k should work, but the issue is in buffer/memory management (not enough CMA memory), so it falls back to SW decoding (press "o" during playback and check info). I'm working on IOMMU support, which would solve this issue completely, but it seems IOMMU driver doesn't always work correctly. This will take some time to solve.
-
offbeat everlanes I just found the issue and potential solution. It seems that width and height need to be multiple of 32 when converting from original NV12 tiled format to standard NV12. Please test following update: http://jernej.libreelec.tv/test/vp9/ If it works, I'll PR fix/workaround.
-
At least simple OpenGLES things like kmscube seem to render and output at 144FPS just fine, so it's only video plane output that has some glitch.
Correct. I believe the issue is timing - HW scaler for video plane is a bit sensitive when registers are updated and I'm pretty sure we don't write them at optimal moment.
Jernej, I have just tried that but it says it was unable to run one, or two media files and I can find info in log files.
This is not debug log. Not a single line which would say "DEBUG".
-
It's entirely possible that 144 Hz output needs some things to be done in more precise ways. Sorry, I don't see this being addressed anytime soon.
-
So its DRM driver, guess it can be reported to mesa bugtracker?
No, display driver (sun4i-drm) has nothing to do with GPU. I'm actually main maintainer for DE3 variant (used by H6). Wait, are you testing this on LE?
-
Yes, prime decoder=ON + prime render=EGL helps, video is OK.
ok, so issue is either with rendering code in Kodi or with DRM driver. Either way, I can't do anything more without having 144 Hz monitor.
-
Here is a different issue I mentioned in previous comment, broken hardware decoding outputing to 144Hz, video is plain h264.
That might be DRM rendering issue. Can you try with switching DRMPRIME rendering from "direct to plane" to EGL? If that doesn't help, I don't know... I would need such monitor to test directly.