Posts by chewitt

Quote from Sanduhrgucker

I anybody able to confirm open-cl is working ob this devices? (specs says yes.)

Kodi has no requirement for OpenCL so people in this forum have zero experience with support for it in the Amlogic BSP kernel. You will need to get the buildroot kernel sources from Amlogic's servers and look at the code yourself. I can authoritatively state there is no OpenCL support in the current mainline kernel - because it doesn't have properly functional OpenGL/GLES yet (via panfrost) and OpenCL is something that won't be considered until some point in the distant future.

LKML will have *everything* being submitted along with Q&A messages. If you're only interested in Rockchip patches, patchwork is easier:

Rockchip SoC list - Patchwork

Nothing for RockPi4 visible yet.

Another revision of patches have been submitted in the last week. It will take time to get things merged upstream and have that trickle (or flood) down into LE but there is progress and ongoing development.

1. Sounds terrible, and personally knowing the default skinners on Team Kodi I guarantee they will never consider ruining the default skin with this.

3. Submissions of code are welcome.

5. No idea, I don't use DNLA and have no personal plans to experiment with it.

6. Services which use HBBTV or similar derivatives can be done through Kodi addons which manage interaction between whatever client is required and the streaming interface (Kodi supports DASH etc. and the underlying player engine (ffmpeg). Kodi is unlikely to ever be HBBTV certified in any meaningful way because that requires HBBTV membership at €8k/year.

As all your suggestions are Kodi related (not LibreELEC related) the better place to ask them is the Kodi forums.

I've never encountered a column width restriction in the OS (using PuTTY or any client on macOS) so I think you need to use a different client that allows wider columns, or figure out how to configure SecureCRT correctly.

connman/connman.git - Connection Manager appears to show some support for connman displaying vlan tags against available services. It might be worth exploring what connmanctl shows as available services instead of the settings add-on client?

There is no support for EAP networks in the settings add-on GUI because nobody on staff has ever had access to an EAP network to figure out what's required to support them. You should be able to set the required things from the console using connmanctl or putting the required config in whatever text files connman requires. I suggest having a look at HOWTO guides for Arch/Ubuntu etc. to figure that out. And, if you succeed, some code to add support or fill missing gaps is always welcome.

Probably best to post in the dedicated thread for that release.

From the HTPC side a clean install removes all knowledge of the remote. From the BT remote side .. it's still paired to the previous HTPC install.

Yes/No .. depends on the hardware you have and if/whether the EDID data can be dumped to file and reused.

Not possible. It's a basic tethered hotspot not an access point. On/off and SSID name/passphrase are the only config options.

Send a pull request to jernej git repo - if it's a meaningful change he can absorb it and send upstream.

LE10 will add the nouveau driver so that nvidia users can see something on-screen, but most cards will run badly and nouveau is not a solution (unless someone has a eureka moment and figures out how to reclock nvidia cards). In reality LE10 will have no practical support for nvidia GPU cards. I will clarify the wording next time I write another development update.

You probably have to unpair the remote first before it an be re-paired.

Technically yes if have SSH access to the box and the 'dd' tool exists in the filesystem. Or spend $4 on a USB card reader.

Hello Tom. Our Rockchip codebase is in the process of being rebased against the Linux 4.20 kernel so please submit the working device-tree etc. to the upstream kernel first. If we see changes going upstream it becomes acceptable to add temporary patches to support your board. If we don't see any effort to upstream support our developers are unlikely to show interest. Thanks.

If you "get more" it opens the add-on browser .. or you can navigate there directly to install them (in Kodi settings or from the home-screen).

Kodi evaluates audio properties at startup only, so if things change after boot they will not be detected. It's not ideal, but it's how the current code is designed so it's not a bug. Hopefully it will change in the future - it's something we're aware of.