An official recommendation to anyone reading the ^ above procedure is: Do not upgrade from old OE installs. Back-up the essential things like sources and database files, but then do a clean install of LE instead of cross-grading, followed by a restore of the few things you copied. You will end up with a cleaner and leaner install, and will have a 512MB boot partition so you won't need to resize partitions at some future point.
Posts by chewitt
-
-
-
-
Build an LE image and then edit project/RPi/devices/RPi4/linux/linux.arm.conf (for RPi4, others in similar folders) and then rebuild the image, it will only rebuild the kernel with your changes. If you truly need/want to edit the defconfig it can be done by navigating to the linux build folder, which will be somewhere like build.LibreELEC-RPi4.arm-<version>/build/linux-<string>/ and then doing "ARCH=arm make menuconfig" to edit the existing .config file in the folder, then copy the .config to project/RPi/devices/RPi4/linux/linux.arm.conf and rebuild the image.
-
Hi, feature requests for Kodi should be made via the Kodi forums.
-
There are some known caveats with the Amlogic mainline codebase right now, but the core OS is in good shape on the C2 and this morning I added support for the Odroid C4 to my work-in-progress branch. LE will continue to champion upstream Linux kernel development and the future of Linux and Amlogic (and Allwinner, Rockchip, Raspberry Pi, etc.) support within Kodi; for our own personal fun and amusement, to benefit the wider open source community, and never for profit. If you're familiar with the author Douglas Adams, everything to do with CE is ring-fenced with an "SEP field".
-
-
Telegraf is a metrics/monitoring tool for IoT platforms. It has nothing to do with social media - I think you're conofusing with Telegram.
-
It's a known and unresolved bug, and all development on LE 9.0.2 is completed. Best to use LE 8.2.5.
-
Kodi master was bumped the other night and most add-ons in the repo need to be rebuilt and version bumped before they will work. That process is being done right now .. so sometime in the next 24h the repo should be up-to-date again.
-
Use /storage/.config/system.d/ .. as /storage is the only persistent area of the filesystem, everything else is created on boot.
-
It's been tested with a proper HDMI analyser and other bench equipment - at 4K resolutions the clocks are unstable and it will not lock onto HDMI 2.0 frequencies correctly so you have a bunch of display problems that will not be solveable in software. People can always revert the change to experiment, but S805X was never meant to be a 4K part so I'm not surprised it's out of spec.
-
Mali = GPU, used for rendering GLES content on screen (e.g. Kodi). It has nothing to do with hardware video decoding.
-
-
I'll talk to the maintainers about making the change, as it was originally raised for a reason.
btw, see drm/meson: add mode selection limits against specific SoC revisions - Patchwork for the first attempt at keeping S805X devices to 1080p. It looks like the patch will take some revisions get merged, but it will come. -
LE is focussed on being an awesome media playback OS for Kodi and we have no ambition to become a general purpose distro that people can use for webcam chats with their family and similar - Covid or no Covid. As a result there is an intentional lack of webcam drivers in the OS, and no plan to change that an add bloat that overall nobody uses (aka the death of a thousand cuts). It's open source though, so if you want to experiement on your own, that's fine with us. You already figured out the easiest way to add a driver. If you wanted to bundle them as an add-on, have a look at how the DVB driver add-ons are handled - lots of prior art in the build-system.
-
So that kinda had me wondering what direction was better to look into "stateful or the newer stateless" and didn't want to go in a direction that was opposite to where everyone here is working towards.
Hardware IP is either stateless or stateful .. it's not a choice. Amlogic is stateful.
-
Kodi v19 is still in a pre-Alpha state, and that suits us just fine since there's still a ton of plumbing that we'd like to do for GBM/V4L2 support on ARM devices. So there will be an LE10, but not anytime soon, and we're not in a rush. The K19 add-on Python3 migration situation will also ensure lots of people will remain on K18 for a while yet anyway.