5schatten
5schatten
@lwfinger Not quite the same error but probably linked to this. Build log: https://pastebin.com/pZnMDc69 ``` /home/supervisedthinking/git/libreelec-rr/LibreELEC.tv/build.LibreELEC-KVIM.arm-9.1-devel/RTL8192DU-3105cd3179d5e60a7aa675611a3592a45b29bfcb/os_dep/osdep_service.c: In function ‘call_read_iter’: /home/supervisedthinking/git/libreelec-rr/LibreELEC.tv/build.LibreELEC-KVIM.arm-9.1-devel/RTL8192DU-3105cd3179d5e60a7aa675611a3592a45b29bfcb/os_dep/osdep_service.c:41:19: error: ‘const struct file_operations’ has no member named ‘read_iter’ return...
Well in that case I guess it's not worth the hassle since the AML Kernel 3.14.29 is basically a dead end. I'll create a separate package with a older driver...
@afrantzis I tried to run glmark on my RockPro64 too & it fails with the same output: ``` rockpro64:/usr/bin # LD_PRELOAD=/usr/lib/libEGL.so.1 LD_PRELOAD=/usr/lib/libGLESv2.so glmark2-es2-drm -d Debug: Using Udev to detect the...
@webgeek1234 I tried both and I still have these glitches. The Vulkan renderer doesn't draw those artifacts so I guess it's related the OpenGL renderers color handling ¯\_(ツ)_/¯
Last time I updated the core I added a patch with https://github.com/libretro/beetle-psx-libretro/pull/504 but still have these problems. I guess it's also related to the Intel drivers because it runs fine...
I updated to the latest version but still get these weird dots. Happens for me on my i3-6100 / J3455 & on older i5-2520m based systems but not on my...
The bug happens for Sandy Bridge, Skylake & Apollo Lake based systems even on latest Mesa 19.1.2 with both available drivers i965 & Iris. So then it's probably a kernel...
IMHO you should have a look at [FluidSynth](https://github.com/FluidSynth/fluidsynth) or [Munt MT-32](https://github.com/munt/munt/blob/master/DOSBox-mt32-patch/dosbox-SVN-r4025-mt32-patch.diff) Maybe the way Retroarch implemented a MIDI driver could give a hint. https://github.com/libretro/RetroArch/commit/c1662ded34792b3e8746292ad573640b2191c8e9 Both works fine for me with...
Can we define a common numbering scheme for patches e.g. https://github.com/LibreELEC/LibreELEC.tv/blob/master/packages/mediacenter/kodi/patches/README.patches ?
Just a wild guess but does the maintainer of this package actually use it at all? I mean without the ability to use custom .conf files we're pretty screwed.