Posts by chewitt

RK has a native 10-bit pipeline, same as S912.

Kodi supports Wayland as the long-term successor to X11 (a successful Kodi GSOC project from 2017) and there are several desktop oriented distro's that support Wayland and people who actively tinker with that combo. LE has no need or plan to use Wayland though. Maybe the lack of browser in Kodi (e.g. via CEF) will be resolved.. nobody knows.

u-boot stores the MAC in efuse and the kernel reads the values back from efuse

Have you looked at the Bluetooth Audio Switcher add-on in our repo? .. this auto-switches Kodi to pulseaudio when BT audio device is paired to the HTPC and reverts to alsa (e.g. HDMI output) when the device un-pairs.

LibreCopter?

I normally recommend people search wikidevi for devices using the ath9k_htc driver as it's in-kernel and fully open source and well written, but S805 requires the 3.10 kernel which has prehistoric support for everything so I no guarantees that it would be supported either. Hence the modern kernel comment I made in my first reply. Plan B.. get an old Apple a1rport from eBay and use it as a wireless bridge via Ethernet and eliminate all driver hassles. The last one I acquired was $20.

Probably not. Android will support whatever WIFI card is in the box and not much else.

In the mid-term the difference between T860 (RK3399) and T820 (S912) should become moot because both will be using panfrost. The current advantage of RK3399 is that the T860 blob is available publicly and it's the more stable option, and we can elect when to make the change vs. S912 which can only use panfrost. Fortunately panfrost is making rapid progress

Your options are:

a) Wait patiently for 12 months (maybe) until there's viable mainline kernel support for S805 hardware

b) Swap the S805 device for a Raspberry Pi or Intel NUC device (anything running a modern kernel)

c) Swap the unsupported USB wireless dongle for something that is supported

People have compiled Chromium to be used with a GBM back-end and a large number of people have pointed this out to us since we are generally moving towards a V4L2/GBM video pipeline in Kodi. There's no guarantees this will be viable though, and we've maintained Chromium in the past and found it to be a rapidly iterating pain in the rear to keep current. TL/DR; don't hold your breath.

^ that video shows update of an old/existing OpenELEC install being updated to LibreELEC. It does not show first-time install of LibreELEC using an S905 image. If you had some random community image installed before you need to clean install.

If you want to pirate movies you're in the wrong forum.

No schedule as it's all community "best-efforts" work. I'd guesstimate months not weeks. How long is a piece of string?

Quote from buzzmarshall

on another note... just what exact linux revision are they trying to unify to as I am thinking about spending a bit of time going back and revisiting the kernel issue. years ago a couple of us move the old meson8m up to a custom 3.14 kernel which works good but now with the newer stuff i am assuming were talking about unitfing up in the 4.xx range ?

Meson8* has reasonable support as large amounts of the platform are similar to GXBB, but the HDMI chip is different and there is no driver for that at the moment. One of the Amlogic maintainers (Martin Blumenstingl) has the intent (if not much time) to write one that hooks into the DRM/KMS code for Meson GX, but until that work bears fruit there's not much to be done. That said, if you're keen on those devices it wouldn't hurt to get them booting and send the device trees upstream. Current efforts are tracking Linux 4.20+ kernels.

Bootleg DDK access isn't the solution. We have sources with DDK access but if we ever released blobs we'd be violating ARM license/redistribution agreements and it would massively compromise our ability to engage with ARM people in other areas. Staff in their open-source group are tracking lima/panfrost and have asked for internal permission to contribute. Both projects will be fine whether it comes or not, but having ARM people with inside knowledge on the many errata in their chips would be a big bonus. Lima is very solid for Kodi use now (at least via GBM/V4L2).

Meson8/8b/8m2 hardware currently has quite good core platform support and an active kernel maintainer. The one critical component missing is the HDMI driver (Meson8 does not use the same DesignWare IP in newer GX devices). Martin has some early stage driver code but it's not functional at the moment (screens are still dark). Until his effort bears fruit there's not much point looking into making LE images, but (famous last words) it should be simple to create something once there's a eureka moment.

S912 has a bright future. See YouTube for evidence. Panfrost still has some serious bugs to solve before we can think about public testing, but considering the infancy of panfrost code it's in good shape. The lead panfrost developers have publicly stated good Kodi support is one of their goals

Ahh.. after Googling I see mention of "Dreambox One" being an 8x Core device so it has to be S912 or S922. If you are lucky the uboot bootloader is not locked and it can run LE