I want to try it and see if the Kodi menu will not be faster. Now that menu in kodi is jerky with late response.
It will be the same on eMMC and SD card. What needs to be done is to enable GPU dynamic frequency scaling, which is actually already possible but not enabled, because it's untested. In order to enable it, DT patch is needed. This way, higher frequency can be set, which allows for smoother animations.
The USB drivers cause lock-ups and performance (~100Mbps via iperf) is worse than out-of-tree modules (~270Mbps).
In aforementioned patches is a lot of locking fixes but hard to tell if a additional fix is needed without dmesg output. Performance is lower, since USB (and SDIO) transport part of RTW88 driver is community driven, but you have to start somewhere. In any case, this is best that you'll get, out of tree drivers are rejected for a reason.
Yes, you just need to add additional CPU operation point, either by editing DTB file or via DT overlays. Why would you want overclock your board? It doesn't give you much benefit for LE purposes.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
and read following conversation: https://oftc.irclog.whitequark…sunxi/2021-06-16#30012323 and maybe check openvfd code for FD650 commands (chip used in Tanix TX6). Note, above example was never tested in LE. I don't know if above libs are included, most probably not. Last but not least, it's not completely standard I2C communication. For each transmission you have to set "Ignore ACK" or similar flag.
Randomly at reboot (the very first one after resize for instance)
I hoped nobody will experience that. I got such issues when RSB bus was clocked at 4 MHz. I lowered that to 100 kHz and never observed such issue again. I guess I could lower it still. I'll prepare test dtb file, which you can just replace on SD card for testing purposes.
It's stated in OP that H6 image doesn't support analogue audio. Driver is missing. I wrote one, but due to configuration issues, I never PRed it. I guess it's LE12 material.
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?
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.
1) Sure, you can use whatever USB wifi is otherwise supported on Linux. Note that it's good to do a little research before you buy wifi dongle. Dongles, which have no mainline driver, are not supported in LE. If in doubt, tell here which chip is used and I can check.
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.