Amlogic releases their BSP codebase which is the same awful code from 3.10 ported to 3.14 ported to 4.9 ported to 4.19 (in process) where each iteration focusses only on supporting their latest/greatest chipsets. Their technical focus on new devices frequently stomps on support for older devices so it's a long-term nightmare to support a wide range of devices with and you cannot take the latest buildroot release and use it with Meson 8. It's also fragile code which is a pain in the arse to maintain; fixing one problem constantly breaks something else. LE's strategy is to move all of our target hardware platforms onto mainline kernel to solve these issues; mainline provides a maintainable codebase that supports a broad range of hardware using well written drivers using modern kernel API frameworks. The root of the problems with the BSP drivers is they were written long before many of the upstream frameworks existed (or matured) so Amlogic evolved their own proprietary ones (with no external scrutiny, hence the many architectural and code quality issues). This means the BSP drivers don't fit modern kernels and writing from scratch is cleaner and usually easier than attempting to adapt them. The solution for Meson 8 is someone (Martin B unless anyone else starts contributing) writing a new HDMI driver that fits into the current kernel DRM (direct rendering manager) framework. There's been a lot of work in the last 18m on the dw-hdmi IP Amlogic used with GXBB and up (and common with Allwinner/Rockchip). Meson 8 uses different IP so it needs a different driver, but dw-hdmi provides strong guidance on what the structure of the missing driver needs to be like. I'm confident it will happen, but HDMI drivers are complex, there is limited documentation on the IP used (and the in-use BSP drivers frequently disagree with Amlogic's internal documentation) so it's a reverse engineering effort. Martin has been experimenting with HDMI code for a while now, but it's only quite recently that surrounding core board support was really in a stable enough or complete enough state to start making a serious effort. And I'm sure he has a life outside of poking Meson 8 code, so it won't be quick.
Posts by chewitt
-
-
I'm not sure who added KVM to the OVA description but AFAIK no staff members run it on KVM and we've never formally supported "user" use on any form of virtual platform (we create it as a staff userspace development/testing tool) so the description should be corrected to remove the reference.
-
LE has a long history of encouraging community created images that prove the relevance of features to our userbase and you are welcome to release images with ZFS support via our forums. If we see broad use (we track stats from named builders so we can see exact numbers) we would be happy to "adopt" the capability and make it more generally available. Historicially most storage related things (encryption, RAID, etc.) remain niche but we keep an open mind.
-
If you'd like to submit the kernel defconfig change to our master branch it's no drama to add it to future Generic releases.
-
The original SliceOS update function is based on noobs and points to files that probably don't exist anymore (as 5Ninjas are no longer around). I would clean install the current LE image (re-flash the eMMC storage) .. Kodi v15 (SliceOS) to Kodi v18.5 is a large jump.
-
-
You can just create the same rules on both clients as rsync (with the right comman) does action "sync" not a simple push of content from A > B.
-
The connman tethered AP feature "is what it is" unless someone submits code to connman to add features and we (LE staff) have no plans to start writing connman features. It's probably not impossible to add packages for host_apd and more fucntions, but we have no desire to be a router OS so there are no plans to do that either - but we're open source so you're welcome to experiment on your own. The practical solution to "I want a cheap wireless router" is to get a cheap (hardware) router. Or you can switch distro to something with package management that allows configurability. LE is by deliberate design a locked-down and fixed medicentre purpose (not router or general purpose) distro.
-
We have no plans to create add-ons for pCloud but you can probably find a Docker container that includes the client.
-
You can use rsync (in the network tools add-on) with SSH key authentication (to avoid passwords) to sync the thumbnail cache from client 1 (master) to client 2 (client).
-
Assuming this is Pi hardware you edit cmdline.txt which is on the FAT32 partition.
-
Google have done something which restricts API usage and breaks the add-on. These thing happen once in a while. There's probably more info in the add-on support thread in the Kodi forums.
-
LE bakes all compiled code into the SYSTEM image file which is read-only and there's no package management so it's not possible to change anything. The only way to change would be self-compiling with an older version. The better apprpoach would be reporting the niggly issues to the add-on devs via their support thread in the Kodi forums so the issues get fixed.
-
It needs CONFIG_AQTION=m enabling in the kernel defconfig. Ping milhouse
-
You can append ?mirrorlist to the URL of whatever file you're trying to download.
-
S812 has quite a bit more grunt than S905 but .. not much use without the HDMI driver. Fingers crossed..
-
Thankfully I'm not the only person working on mainline support
-
GT King and King Pro should both work as the hardware is almost identical .. although ealier versions of their Android firmware have u-boot versions that can be fussy with SD card or USB booting. The washed out screen colours are caused by the vendor u-boot setting HDMI properties that the latest kernel releases don't fully understand. The correct but slow fix is extending the DRM driver. The faster but more brutal fix is to replace vendor u-boot with mainline u-boot (which doesn't support the HDMI properties that aren't supported in the kernel .. thus sidesteps the issue). I have Beelink's u-boot sources if we need to go in that direction, but Oleg is also experimenting with another approach which might be more subtle