Posts by chewitt

    _emanuel_ panfrost is used for accelerated GUI rendering and has nothing to do with hardware video decoding. The vdec drivers (which do) are still early work in progress (with not much work in progress). I looked at the vendor keernel dreamone/two dtb files and apart from IR keymaps, LED and button things, there's not much to improve upon with a dedicated dtb - you can build off the W400 dtsi the same as the existing Ugoos AM6 and various Beelink G12B devices (GT King would be a good match). The mainline kernel also takes RAM size from u-boot so this does not need to be set. What do you think is missing?

    Am I right in thinking that the switch to GBM is switching to wayland or will kodi be acting as its own display server? Otherwise with chrome supporting wayland would that not work?

    No, Kodi will render directly to the framebuffer with no windowing system. It's effectively the same arrangement we use with ARM devices. The lack of window system is the blocker. We could also run Kodi under Wayland, but then you have no "adjust refresh" support and there'd be an angry mob of pitch-fork waving villagers complaining about that :)

    From Petitboot, "Exit to Shell" and run:

    # flash_eraseall /dev/mtd0
    # flash_eraseall /dev/mtd1
    # flash_eraseall /dev/mtd2
    # flash_eraseall /dev/mtd3

    This exorcises petitboot from the SPI flash, and distro images that use modern u-boot with extlinux.conf (LE, Armbian, etc.) will now boot from SD card. I've asked HK when they plan to support extlinux.conf boot in petitboot and got a meh response. Restoring Petitboot (if you want to do that) is achieved by creating an SD card with the petitboot update file on it and booting the board. There are instructions for that in the HK wiki.

    chewitt .. quick question, i saw this on the LE blog "We are pretty confident RPi4 users will like the update since it brings HBR audio and initial HDR video support" .. what exactly does initial support mean?

    So has anyone done "proper" passthru audio testing of the build in 502? Like does it finally fix the split second audio drop that occurs every few mintues?

    Initial support means: it is the first time someone coded HBR audio for the latest RPi4 codebase (Linux 5.10+) .. not that anyone is planning to rewrite it but as with all first implementations there are likely some corner cases and issues to find. There have already been some fixes and bits which are tested and then pushed upstream. So no idea what you mean with the pithy "proper" comment. The work is being done by a group of people who care deeply about getting it right and there's been a substantial amount of testbench and people testing so it's not some "hey mum, look we make sound" half-arsed exercise. I've no idea what "the build in 502" refers to. You can look at GitHub commits if you want to track the status of development.

    I'm having the same problems on Libreelec 10, all other Kodi installs on Windows, Mac and Android are working fine.

    I'm using DNS names for my shares and SQL database (no chance to change that easily).

    I've been reading that SMB got an updates in Libreelec 10 and using the IP address might solve the issue.

    Yet another user with wild theories and no facts about their configuration. Good luck on getting help.

    ^ this list is mostly older Amlogic GXL or maybe early G12A devices so "none of the above" would be my recommendation. On paper they all have amazing hardware spec but all boxes will ship with 3-4 year old Android image and there will be no OTA updates from the vendors. You can find CoreELEC images (equivalent to older LE images) that run on the legacy vendor kernels but further comment on their images needs to come via their forums - I have no interest in it and don't run it. LE images based on our modern kernel codebase are still early-stage (nightly and my builds exist, but there are playback glitches to resolve).

    It's fairly obvious you don't want to listen to RPi comments, but: I actively/regularly use an assortment of Rockchip, Allwinner, Amlogic and Pi devices and the winner of "easiest device to live with" by some way is an RPi4 (in Kodi flirc case, and with flirc USB IR receiver). RPi4 will never win a "longest list of spec" award and will cost a little more than a 2105-2018 era $45 box (modern boxes are typically more - and component supply problems are inflating costs) but RPi4 has all the main codecs you actually need, with 4K HEVC, and now with HDR and HBR audio. RPi gets A1+ software support direct from the manufacturer. In the long-run software support is why it's been the most popular Kodi device since 2012 and that's unlikely to change. At some point someone will make a fantastic RPi "box" using the CM4 board to add things like eMMC or nVME storage, but there's more $$ in the IoT space so I didn't see one yet.

    I recently tried hooking the RPi4 directly to the Bravia. With this setup, and the same file as before, the Bravia WILL show HDR in 4K.

    Is this something worth troubleshooting in libreelec, or is this maybe a problem with my AVRx4300h?

    It works without the AVR inline. It doesn't work with the AVR inline. In not seeing how it's an LE problem :)