Posts by chewitt

  • Issues with RF Remote w/ IR Learning Feature (Odroid C2)

    ir-keytable needs to be listening on the right protocol to see anything and some remotes have odd vendor invented stuff for power-on events; for the same reason you might not be able to teach a remote that only understands specific protocols and doesn't just capture/record whatever signal is transmitted to it. I'm about to start playing around with the current official HK remote to ensure it works on mainline kernel images using mainline u-boot, but that's not an endorsement and might not be a quick solution.

  • Libreelec only in DHCP

    The connection manager (connman) stores static connection details against the MAC address, and if you investigate you'll probably discover that the kernel is assigning a random MAC address on each reboot, so there is no matching profile and it defaults to DHCP again. The cause is the hardware manufacturer being too cheap to spend some $$ getting a block of unique MAC addresses for their hardware. To advise a workaround we'll need to know what hardware you have?

  • Passtrough

    Users often and wrongly believe pass-through is some magic "hardware doesn't touch the bitstream" method, but in reality the hardware has to support the stream format to correctly detect and handle it as a pass-through stream. Raspberry Pi doesn't support any HD formats.

  • Early community images for H3, H6 and A64

    Quote from noblock

    chewitt, now, when using the mainline kernel, everything is the same at the linux packages level between Allwinner and Amlogic. With one exception, the m2m cedrus and meson implementation are not compatible. Is there some standardization / merge in progress on that matter?

    The video pipelines for Amlogic, Raspberry Pi and Exynos have stateful decoders while Allwinner and Rockchip have stateless decoders. It's not possible to combine them into a single m2m implementation as stateful/stateless work in fundamentally different ways, although we are working to minimise the differences and have ffmpeg mask the implementations so there's still a single/common interface with Kodi. As there's no prior art for anything it's a "two steps forwards, one step backwards" kind of process, and there's still a ton of code to write, but the direction is still forwards, and each month ever more bits of the big jigsaw puzzle are falling into alignment.

  • Information Regarding Linux on Rockchip SoC's

    The DesignWare HDMI driver used in Amlogic (and Allwinner/Rockchip) devices still needs to evolve 10-bit video support, and the Intel developers still need to get their HDR and colorimetry patches merged into the upstream kernel (still work in progress). In the last week or so we've started to poke the Kodi side of that work using Intel hardware where the dependences in a more mature state, but this is really a green-field area for all Linux hardware, so there are no prior examples to crib things from and we are literally making up the rules (and code) as we go. In the mid/long-term I have absolutely no concerns about LE (and Kodi) having A1+ support for HDR .. and hopefully in the near future I can write a blog post to explain what's going on in the background and why we're rather confident about that :)

  • RPI 3B+ Wifi issue

    wpa_supplicant exists but networks are configured through connman, and both are achieving the same result as the modprobe command. I'm not sure "EU" is a correct value since wireless regulations are normally country specific, hence DE/FR/UK etc. are used.