Posts by chewitt

_emanuel_ I picked the MIPI-DSI patches currently on the mailing list to https://github.com/chewitt/linux/commits/amlogic-6.7.y so use that branch for device-tree experiments. AFAIK the kernel does not support output on MIPI and HDMI at the same time currently, but the folks working on the MNT Reform laptop + BananaPi CM4 (A311D) module should investigate that. So focus on getting normal output on the LCD working first. NB: The two patches I didn't pick to my branch (which are important for prior-art) are:

[v8,11/12] DONOTMERGE: arm64: meson: khadas-vim3l: add DSI panel - Patchwork

[v8,12/12] arm64: dts: amlogic: meson-g12b-bananapi-cm4: add support for MNT Reform2 with CM4 adaper - Patchwork

The Khadas TS050 driver is already upstream in the kernel (hence the compatible can be used). Same for the Innolinux LCD used in the Reform laptop. You might end up needing to author a driver for the LCD panel; I'm not sure what part is used in the DB2?

EDIT: found some more useful stuff:

Share photo's of the PCB (both sides)

The LE12 releases are also fine: https://test.libreelec.tv/12.0/RPi/RPi5/

Have a read: https://wiki.libreelec.tv/configuration/wireguard

I'll revise my answer somewhat. The Widevine L1 license isn't required to use Netflix. If the box is not L1 licensed (e.g. only has L3) you will be restricted in resolution to 1080p max. The key thing is to be using the official Netflix app installed from the official Android app-store and I'd always want an OS that is updated periodically: and that combination of requirements still herds you towards a Firestick/Shield like device.

"If it works, don't fix it"

Kodi has "a" library (singular) for movies so even if you code it's a non-trivial change to implement multiple databases. The default Estuary skin also does not support adding new items in the top-level navigation menu. However, it's possible to add your own shortcuts similar to "recently added" or "genres" under Movies using the "node editor" addon. Using this you could add a "Home Movies" item that displays content using specific metadata or source as the node filter criteria. I believe some skins also support adding additional navigation items, which might allow you to do similar things (or leverage the nodes you added) but on the top-level menu (but I only use Estuary so I forget the names of the ones that do allow that). Worst case, and if you wanted to stick with the default Estuary skin, you can clone/hack the skin to manually hardcode the items. You need to clone /usr/share/kodi/addons/skin.estuary to /storage/.kodi/addons/skin-estuary-mod and then change the skin name in addon.xml to skin.estuary-mod to avoid a namespace clash. Or if you're more build-system minded; create a diff patch of the change and then build your own LE image (which is easier than it sounds) to always have your changes pre-built.

_emanuel_ I can add them back, but no plans to upstream them as long as there's no functional difference between v1/v2 boxes. I note that there's been some movement on MIPI-DSI support (due to the MNT Reform Laptop) so it could be interesting for you to see if the 3" display on the v2 box can be got working?

RPi4/5 can handle HEVC at 1080p resolutions but ultimately it's a Linux device so you'll experience whatever challenges and problems that Netflex chooses to inflict on the FOSS community via API changes and such. To eliminate that you need to use Kodi with an Android device with a Widevine L1 license. The device used by most Team Kodi staff is the nVidia shield; largely because nVidia shipped a load of them to be used as test devices a few years ago, but also because nVidia provides regular OS updates for the device over time unlike most Android boxes which are obsolete within minutes of shipping. The other would be Amazon firesticks and such which (again) have the DRM licenses needed for long-term easy access to the DRM protected services.

Have a read of https://wiki.libreelec.tv/hardware/amlogic .. there's a device-tree included in the AMLGX "box" image. Also read recent release notes to understand the current state of things. I'd have thought OSMC was the best OS to use on that device.

Have you read https://wiki.libreelec.tv/configuration/ir-remotes ?

The log shows no attempt to switch to HDR modes which implies HDR isn't exposed as an option through the kernel rendering system which implies the Intel GPU drivers in the kernel we are shipping (also the latest available) don't support HDR. Updating firmware doesn't change anything in the kernel drivers, and comparisons against other OS (with entirely different software stacks) aren't meaningful.

It would help to see the EDID info which is logged in kodi.log on startup; this doesn't show as you've enabled debug after boot.

The issue and latest findings should be reported upstream to the Pi devs via their GitHub tracker (as advised in post #62 back in March).

The upstream kernel switched IR keymaps to the "toml" format so I'd guess you need to make the same changes in your file. Have a look at the keymaps in /usr/lib/udev/rc_keymaps/ to crib the format changes (not hard).

Your Q was already answered: https://github.com/LibreELEC/LibreELEC.tv/issues/8322

If the same file being played by the same K21-b1 version of Kodi on Windows works, the issue is likely to be Intel drivers, in which case our normal course of action is to simply wait for Intel to finish adding support for their latest/recent chips.

WiFi is conected via the SDIO bus which supports device discovery, so even if the device-tree file you're using describes a Broadcom wireless module (as is the case with all the generic reference designs) the bus is probed and if a Realtek device ID is found the correct driver will run, and as long as the firmware is available WiFi will work. BT is different; it's a serial UART device and requires device-tree to correctly describe the hardware, and if a Broadcom chip is the 'compatible' hardware described a Realtek chip doesn't work. The solution to that is creating a dedicated device-tree file for the box. It's not a particularly complicated process (fairly easy to copy/paste) but still requires you to then create kernel patches and self-build an LE image and most users aren't interested in having a go.

I replied in the other thread.

https://github.com/LibreELEC/LibreELEC.tv/pull/4566 <= That's the PR that dropped support for Slice boxes. In there you'll find the original add-on that FiveNinjas created and LE buildsystem package.mk files that tell you where the drivers are. Compile the drivers for your OS and then use the add-on (or use it for inspiration on how to control the LEDs). The only barriers to doing things are time and effort.