chewitt: First of all thank you for your answer. I will try to sum up the information that I have and the path that makes most sense to go (even if I do not know if I'm able to do this but at least see what would be the approach that would make most sense):
For the update the following points need to be tackled:
- using 9.2.8 to see if it is "just working" will not work "out of the box" and would need to be modified to run on the CM4S - USB hardware which in my opinion (and as you are hinting to) does not make that much sense
- so it makes more sense to directly update to the newest version of Libreelec (as of writing this, the stable version for the Raspi 4 is 11.0.4) and thus updating the python code from python 2 to python 3.
- This would mean that
- we are talking about the same discussion that was started here (plus adding the support for the CM4S): Getting LibreElec 11 on a Slice CM3+
- the controls for the USB-"Hub"/hardware needs to be updated - not just by copying over the old blob anymore (as described here: https://github.com/LibreELEC/LibreELEC.tv/pull/4566 and here https://github.com/LibreELEC/slice-firmware but by updating the blob and implementing some device-tree changes (or is the blob then not needed anymore?):
- bcm2835-bootloader: re-add slice-firmware and dt-blob.bin handling
- RPi: readd updated dt-blob.bin handling from bootloader update.sh
- scripts/image: re-add dt-blob.bin handling
- scripts/mkimage: re-add dt-blob.bin handling
- and/or perform some device-tree changes
- updating/creating the following files that were removed according to https://github.com/LibreELEC/LibreELEC.tv/pull/4566 (especially taking into account your (chewitt's) last comment (#5) from Getting LibreElec 11 on a Slice CM3+ ).
- RPi: (re-)add device Slice4CMS (Slice and Slice3)
- the slice firmware (update)
- the slice drivers (update)
- (re-)add Slice4CMS (Slice and Slice3) devices in options file
- kodi: (re)-add Slice/Slice3 devices in package.mk
- re-add (updated?) led_tools package
- re-add (updated?) service-slice: addon
- This would mean that
- so it makes more sense to directly update to the newest version of Libreelec (as of writing this, the stable version for the Raspi 4 is 11.0.4) and thus updating the python code from python 2 to python 3.
At least that are all the information i could gather until now (with thanks to chewitt and HiassofT as most of the documentation/answers were provided by you/them).
Fun little abstract. I have not used chatGPT until know and created an account for checking if chatGPT could support. Following are the steps to be taken acc. to the answer and additional it was offering me to upload the content of the files and respond with the "new" version. And yes, I'm aware that it is not as simple as uploading all necessary files to chatGPT and magically all files will be provided and directly working.
Updating a Python 2 plugin to Python 3 and making it compatible with a newer version of LibreELEC and a different Raspberry Pi model involves several steps. It's a complex process, and I can provide general guidance, but you might need to adapt the steps based on the specifics of your plugin. Here's a high-level guide:
Update Python Version:
- Convert the Python 2 code to Python 3. Use tools like '2to3' for automated conversion.
- Manually fix any issues that the automated tool might miss.
Library Compatibility:
- Ensure that the libraries and dependencies used by your plugin are compatible with Python 3.
LibreELEC Compatibility:
- Check the LibreELEC documentation for changes and updates. Adapt your plugin to work with the latest version.
Device-Specific Changes:
- Since you're moving from Raspberry Pi Compute Module 3 to Raspberry Pi 4, there might be device-specific changes required.
- Adjust driver-files, firmware-files, and scripts to match the hardware differences.
Device Tree:
- Modify the device tree to reflect the changes in the hardware. This may involve GPIO pin assignments and other hardware-related configurations.
Testing:
- Test your updated plugin thoroughly on the new environment to identify and fix any issues.
Documentation:
- Update any documentation associated with your plugin to reflect the changes.
Community Support:
- Seek help from the LibreELEC and Raspberry Pi communities. Others may have faced similar challenges and can provide valuable insights.
Backup:
- Before making significant changes, ensure you have a backup of your current setup to avoid data loss.
Iterative Process:
- The update may require an iterative process of testing and refinement. Be prepared for this and address issues as they arise.
Remember that the specifics of your plugin will heavily influence the required changes, and you may encounter challenges unique to your situation. If you encounter specific issues during the process, feel free to ask for help on forums or community channels dedicated to LibreELEC and Raspberry Pi development.
