Posts by chewitt

    That document feels recent, which means it's probably written for the mainline kernel not the ageing fossil that's in current LE release images. Have a play with the balbes150 releases with a 4.19 kernel. Things are a little experimental still, but the GPIO stuff is likely work better.

    Audio is currently HDMI only and 2ch, but there's been activity on the DesignWare audio IP in the last coupe of weeks; the same IP is shared with Allwinner and Rockchip hardware. Some work is needed on the Amlogic i2s driver next, but that will probably happen in the next month as long as people don't get too carried away with video stuff which is a bit more exciting.

    I've no idea what the differences are with p282 boards. I can make enquiries.

    Changing Kodi version is simple. Changing all the stuff Kodi is dependent upon to support the version you changed to is less simple. If you are trying to roll back to an older Kodi version it will be easier to roll the entire distro back to the point where that Kodi version is used.

    shippy Normal 1080p media works fine in 4.19+ kernel images. 4k support has caveats as the HDMI driver only supports 8-bit output at the moment so 10-bit formats like HEVC don't work right and in some situations can crash the box. Until Amlogic/ARM framebuffer compression support is added 4k also requires a CMA memory pool that's too large for 1GB RAM devices. Further work on 10-bit and AFBC is planned in January. Intel has also submitted changes for HDR support to the upstream kernel recently, and while it will take a few more iterations before patches are accepted and merged, once 10-bit support has been added we can start looking at how to hook into the proposed frameworks. If you stick to 1080p media and don't need deinterlacing (as this is still done in software) it's quite usable and I haven't used 3.14 kernel images since August this year. I don't know what S905W box you have but a 1GB/8GB TX3 mini I have runs fine. S905W should be nothing special for 4.19+ kernel as long as the correct device tree for the box is used.

    ^ it appears to be attempting NTP requests to IPv6 servers (2001:12ff::8 is poot.ntp.org) and since we don't support IPv6 that will fail. If the time is not set correctly SSL certs are invalidated (they are valid for a start/end time range in the future) and everything which uses SSL (basically everything these days) lots of internet based functions break. If no time is set the system clock defaults to something weird like the release date of the GCC compiler that was used in our build system, which is something like June 2018.

    NTP is handled by connman which is configured to fall-back/default to using 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org as it's NTP servers if nothing is explicitly set via DHCP or user config, but these are being resolved to IPv6 addresses (presumably by the DNS functions in your router) so you can try overriding these with IPv4 address in the LE settings add-on, e.g.

    ^ pick some IP's from those servers. You might also find that the router provides NTP if you configure it's IP address as the first NTP server.