Quantcast
Jump to content

LuckyKnight

Members
  • Posts

    3
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by LuckyKnight

  1. @The Old Man kodi is available on the homebrew app store and has been for over 2 years. You can install via dev mode. Unfortunately LG have not supported its release on its own official app store, despite it being available on Google, Apple and Microsoft stores, for free for years.
  2. For native app developers, it would be great to see support for Vulkan graphics API. The requisite parts are already present, including the Mali GPU driver. However, the Vulkan ICD file is corrupt on my my TV (webOS 24): Here is the file: { "/bsppartICD"/bsppart: { "/bsppartapi_version"/bsppart: "/bsppart1.3.216"/bsppart, "/bsppartlibrary_path"/bsppart: "/bsppartlibmali.so"/bsppart }, "/bsppartfile_format_version"/bsppart: "/bsppart1.0.0"/bsppart } It should be: { "ICD": { "api_version": "1.3.216", "library_path": "libmali.so" }, "file_format_version": "1.0.0" } It would also need the Vulkan Wayland extension. This would allow for some newer and better performant applications to run on webOS.
  3. LG have been using 64-bit (aarch64) capable CPUs in their TVs for years. e.g. Linux LGwebOSTV 5.4.268-320 #1 SMP PREEMPT Mon Jun 17 01:25:25 UTC 2024 aarch64 GNU/Linux However, the user space shipped with webOS is still only 32-bit!: getconf LONG_BIT 32 This means that these CPUs are being held back by the continued use of armv7a (32-bit). There are many benefits for you to switch to aarch64, most notably a performance uplift of 20%+. This benefit would be seen by end users without even a hardware upgrade. Aarch64 has lots of benefits, such as FPU being forced as well as far more registers. I think its time to ditch armv7a and move future webOS releases to armv8a. Armv8a has been around since 2011! This change would also increase compatibility as a number of vendors dropped armv7a a long time ago (e.g. Google). For native app developers they would simply need to recompile their binaries into 64-bit, provide 32-bit and 64-bit binaries during the switch over. It wouldn't affect any web developers at all, as they interact with the libraries in the same way whether they are 32-bit or 64-bit. Please consider this move for webOS 26!!!
      • 1
      • Thanks

×
×
  • Create New...