![]() ![]() ![]() Then download the latest version, open this dmg and drag DBGL.app to your Apps folder.Ĭlose down DBGL. Drag the existing DBGL App into the trashcan. jar files from the lib/ directory that are not present in the newly downloaded archive.Ĭlose down DBGL. Download the latest version and overwrite all existing DBGL files with the ones from the zip archive. Last version to run on Java version 7, 32-bitĭ dbgl082_ dbgl082_ĭ dbgl081_ dbgl081_ĭ dbgl080_ dbgl080_ĭ dbgl079_ dbgl079_ĭ dbgl078_ dbgl078_ĭ dbgl077_ dbgl077_ĭ dbgl076_ dbgl076_įirst version to include both 32 and 64-bit SWT libsĭbgl069_carbon.dmg dbgl069.dmg dbgl069_64bit.dmgĭbgl068_carbon.dmg dbgl068.dmg dbgl068_64bit.dmgĭbgl067_carbon.dmg dbgl067.dmg dbgl067_64bit.dmgĭbgl066_carbon.dmg dbgl066.dmg dbgl066_64bit.dmgįirst complete Mac release, another 'Starter Edition'įirst Linux version with 64-bit DOSBox, first 'Starter Edition'įirst complete release for Windows & LinuxĬlose down DBGL. It would be great to add libdrm-dev, libgbm-dev, libegl-dev, libgles-dev as dependencies for libsdl2-dev.First version to require at least Java version 11įirst version to require at least Java version 8, 64-bitĭ dbgl083_ dbgl083_ If you could give any pointers, I might be able to debug the issue. I don't understand who/how decides which library should be loaded in runtime. My wild guess is that it not using libmali.so. reinstalling mali-wayland-dkms + reboot starting from scratch with a clean image I haven't seen these behaviors when I compiled libsdl myself.ĮRROR: Couldn't initialize SDL: No available video device INFO: MODE 19: fmt=SDL_PIXELFORMAT_RGB888 w=640 h=480 refresh=75Īnd "testgles2", on KMSDRM runs limited by vsync, but on Wayland it runs at max speed. INFO: 0: "S2719DGF" (1920x1200, (0, 0)), 20 modes.ĮRROR: DPI: failed to query (That operation is not supported) but no Amlogic, Rockchip has it's own implementation of libdrm and is hosted here, so either there is a custom libdrm used or SDL2 is using Wayland or SDL2 is falling back to mesa software rasterizer and that's why I asked for the gles render string that you get when you start the testgles2 toolĬode: Select all INFO: Using video target 'wayland'. Samsung Exynos, Intel, Texas Instrument, Radeon, Nvidia, Raspberry etc. Well your explanation is mostly right but SDL2 KMS/DRM backend is using the libdrm API to talk to the kernel DRM driver, upstream libdrm does not have support for Amlogic meson other then the build system with the same name and here are the supported GPU vendors When using SDL2 with KMS/DRM the rendering is deletaged to this libmali.so, but the scanout is done by KMS/DRM (which I think uses the meson driver). This driver could be used by Wayland as well by KMS/DRM. So buffers and rendering are done by this library. This driver installs the "libmali.so" driver, which offers an implementation of: EGL, GLES2 and GBM (among other things). I'm using the mali-bifrost-wayland-driver for hw-accel in KMS/DRM. Tue 7:19 is my understanding (probably knows better): ![]()
0 Comments
Leave a Reply. |