Posts by chewitt

    Kodi needs to know how to open ffmpeg calling the correct hardware decoder (nvdec, not vdpau) and for things like DRMPRIME to work it also needs to understand an entirely different buffer management process (EGL Streams) not GBM, the standard the Linux kernel adopted. None of them are a huge leap, but "no more proprietary crap" is one of the few things the members of Team Kodi agree upon so if it happens it will almost certainly be a surprise drive-by conttribution from someone new not an existting team member.

    No major changes. Amlogic is now one of the best supported core codebases for ARM devices thanks to u-boot work done by Baylibre and efforts from LibreComputer to get their products accepted into the major distros. The multimedia capabilities are still languishing in the dark ages.

    LE10/K19 first alpha will be soon and likely uses Linux 5.7 .. but this an alpha and since final release is likely months away some higher kernel version will probably be used in final releases, we'll keep bumping during alpha and won't lock things down until beta. There is no point in including the patches flagged above, all they do is establish the current driver is for the A variant and add firmware for the B variant. Until there is also driver code for the B variant there's "nothing to see here, move along please" and adding the realtek vendor driver could be done in a private build, but it won't be done for a public release as we'd need to disable the in-kernel driver globally which will affect other users with A variant hardware.

    Keep an eye on Linux network development - Patchwork and once you see patches posted, there's something to test.

    unfortunately with this image device is not booting, always constant lighting red and blue LEDs. It doesn't matter if I try to start from SD card or USB pendrive. It worth mention that I installed balbes150 SPI boot 20191003/spiboot.img. Should I use different one SPI?

    I have an N2 (and N2+) with the latest petitboot spi image that HK published and all I do is write the SD card (or eMMC module) and ensure the boot switch is to the right, and it boots into LE without issues. I can't say I've ever tried USB, but mainline u-boot should support that too.

    The core OS is in awesome and super-reliable shape since we moved to mainline u-boot and modern kernels. Unfortunately the one thing we need to work well (hardware decoding) is in pissy shape .. and until there's a eureka moment on seeking/flushing support with GBM/V4L2 images aren't so usable. Raspberry Pi (also using stateful decoding) is now stuck at the same point so I'm hoping their considerably larger gene-pool of talent (Amlogic's is woefully small) will figure out something and then we'll be in better shape.

    You're either unlucky with choice of discs or there's something up. Can you share the OS and Kodi logs? (cat /path/to/log | paste and share URL)

    I can't find "gxm201_1g_2GB" in anyone's sources but both kszaq and CE kernels (3.14-nougat) show the same Ethernet config with Q201 devices using internal (rmii) PHY which is the same as the mainline kernel Q201 dtb. You'll need to share the "dmesg" output from the box for me to look any further into the problem. If the WiFi works you can probably get online to share logs from within the LE settings add-on (or CLI).

    I'd guess they aren't deleted by the TVH client as it didn't create them and doesn't know they exist. You could ask the Kodi developers who maintain the add-on the add functionality (via the suppport thread in the Kodi forums) .. or you could create create a shell script that runs via cron to delete the files at regular intervals.