Posts by jernej

    From previous answer I have understood that in case of TX6 Libreelec uses 64 bit kernel for aarch64 architecture and 32 bit userspace for running 32-bit widevine library needed fo netflix/amazon etc. Am I right?

    Yes.

    I'm curious how to use widevine with pure aarch64 kernel and system. The purpose is very simple: I want to do the same for archlinuxarm TX6 project. They released 6.1 aarch64 kernel and uboot which run quite well on Tanix TX6. The only one problem that kodi can't run widevine with "Unsupported 64-bit userspace found. User needs 32-bit userspace on arm64".

    You can't use 32-bit widevine with pure 64-bit system. You would need to build or install 32-bit Kodi and all needed libraries by Kodi and their dependencies and so on, down to glibc. So in short, you would have 32-bit system along 64-bit one. Under Linux, you can't mix 32-bit and 64-bit apps and libraries. Same thing is true on x86.

    Not sure what you want to know. It's only difference of building LE with PROJECT=Allwinner ARCH=arm DEVICE=H6 UBOOT_SYSTEM=tanix-tx6 make image for 32-bit and PROJECT=Allwinner ARCH=aarch64 DEVICE=H6 UBOOT_SYSTEM=tanix-tx6 make image for 64-bit. This only changes compiler and adjust compiler flags, so 32-bit compiler is used instead of 64-bit.

    tested latest LibreELEC-H6.arm-11.0-nightly-20221203-164bd92-beelink-gs1.img.gz, still unable to boot, same error.

    Sorry for late response, but obviously I took some time off LE. I'll surely work on this issue before stable is released.

    Is openvfd module included in kernel for Tanix TX6 in development release?

    No, but I2C bus is exposed and you can write script to drive display. I have some python script example, but it wasn't tested on LE. I can provide it to you as example, if you want.

    Do the nightly images for the H6 include phy ethernet driver support for the Orange Pi 3 LTS?

    No.

    How it can be possible? What mechanism or tricks do you use?

    Simple. While kernel is really 64-bit, userspace in 32-bit. In fact, widevine is the only reason why we release all ARM images with 32-bit userspace.

    Orange Pi 3 LTS

    While I have it on my desk, I didn't add support for it just yet in LE. It needs Ethernet PHY driver and wifi is totally unsupported by mainline Linux. I plan to add PHY driver, but no for wifi.

    H6 (SoC on OPi 3 LTS) has solid support in LE. Missing features are analog audio output (I have wip driver for that, but no time to fix minor issues) and 10-bit display pipeline. This means that 10-bit HEVC videos are correctly decoded but they are displayed as 8-bit, so some banding can be visible in HDR output.

    offbeat can you check board version? Test on 1.0 didn't show any issues. From what I've been told, there is also 2.0.

    Regarding network issue - It seems that other dwmac based drivers also experience it based on quick google search, but that doesn't necessarily mean that the issue is in common code.

    While there is kernel bugzilla, I'm not sure how much is used by netdev people. ML is still best way to go.

    Use something that is already supported by Linux kernel, e.g. without out-of-tree drivers. Integrated wifi and both of your USB devices are Realtek based. Sad thing is that only a handful of Realtek wifi adapters are supported by upstream Linux kernel and yours are not among them. Before you ask, we don't accept out of tree wifi drivers anymore and we are reducing number of existing ones. It's not worth the hassle.

    There are many wifi related topics on this forum, use search.

    Sorry to say, but I went over H6 DDR3 driver so many times that I don't think I can find any important difference between mainline and vendor driver anymore. Actually, there is one pretty big difference in code for checking bus width and rank, but code based on vendor driver was unreliable. Once that was fixed, most H6 DRAM issues have gone away. You can try getting additional output with adding #define DEBUG 1 at the very top (before includes) of H6 DRAM driver in U-Boot and look for additional info. You can also test older versions of U-Boot, but that's most I can help you with.

    And Kodi upscaling seems to take literally no effort on the CPU/GPU.i

    That's true when using DRMPRIME rendering, which is default for all boards except Generic (I think). DRMPRIME renderer uses DRM planes for video rendering, which are implemented via dedicated HW blocks inside display pipeline. So this is basically the third option, which is actually more common than GPU scaling on ARM boards and most efficient too. Usually there is little to no scaling options in HW, so quality is what it is.