ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel driver has landed in mainline, userspace driver is part of mesa - Logs at https://oftc.irclog.whitequark.org/lima/
dri-logg1r has joined #lima
dri-logger has quit [Ping timeout: 480 seconds]
dri-logger has joined #lima
dri-logg1r has quit [Ping timeout: 480 seconds]
dri-logg1r has joined #lima
dri-logger has quit [Ping timeout: 480 seconds]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
dri-logg1r has quit [Ping timeout: 480 seconds]
dri-logger has joined #lima
yuq825 has joined #lima
jernej_ has joined #lima
jernej has quit [Ping timeout: 480 seconds]
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
chewitt has joined #lima
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
yuq825 has quit [Ping timeout: 480 seconds]
yuq825 has joined #lima
camus1 has joined #lima
camus has quit [Read error: Connection reset by peer]
camus1 has quit []
camus has joined #lima
<casept> Is there a tool similar to e.g. nvtop for monitoring usage of a lima-compatible GPU? I'm trying to figure out whether a given application that's performing poorly is even using HW acceleration.
<linkmauve> casept, the relevant driver API never got merged, see https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6077
<linkmauve> But if you just want to see if your program is using OpenGL, maybe try apitrace?
<enunes> casept: I guess an easier way would be just printing the gl renderer or something?
<enunes> casept: to actually answer your first question, no, we don't have it for now. I attempted this before but it had to be reverted: https://patchwork.kernel.org/project/dri-devel/cover/20230312233052.21095-1-nunes.erico@gmail.com/
<enunes> I guess eventually we should go back and look again if the situation is better to reimplement it now
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
yuq825 has left #lima [#lima]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
dri-logger has quit [Ping timeout: 480 seconds]
dri-logger has joined #lima
Leopold has joined #lima
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #lima
dri-logg1r has joined #lima
Leopold_ has quit [Remote host closed the connection]
dri-logger has quit [Ping timeout: 480 seconds]
dri-logg1r has quit [Ping timeout: 480 seconds]
dri-logger has joined #lima
chewitt has quit [Quit: Zzz..]
chewitt has joined #lima
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
<cambrian_invader> is there any cursor hardware acceleration support in mali400?
<cambrian_invader> I noticed that moving the cursor over glxgears halves the framerate
<cambrian_invader> I also don't see any change in behavior with SWCursor set to true/false
<cambrian_invader> is there anything to tweak in this area?
<anarsoul|2> cambrian_invader: Nope. Mali4xx is not a display controller, it's a pure GPU. Some display controllers may have a cursor plane
<cambrian_invader> ah, ok
<anarsoul|2> so it depends on what display controller is used in your SoC
<cambrian_invader> this is with zynqmp-dpsub
<cambrian_invader> so maybe I need to tweak my kms driver
<anarsoul|2> yeah
<cambrian_invader> the armsoc driver has some cursor settings, but the modesetting driver (which I am currently using) doesn'
<cambrian_invader> t seem to have that sort of thing
chewitt has quit [Quit: Zzz..]
<cambrian_invader> ok, so modetest only shows an overlay and a primary plane
<cambrian_invader> which I guess means hardware cursors are not supported
<linkmauve> cambrian_invader, your compositor might support using the overlay plane for the cursor, I think Weston supports that for instance, but I would have to check to be certain, I’ve never used such a display controller.
<cambrian_invader> atm I'm just using X without a display manager, but I'll look into using a compositor in the future
<linkmauve> Xorg is pretty much the worst compositor for modern hardware.
<linkmauve> Try anything Wayland, like Weston or GNOME.
<cambrian_invader> well, mali is not exactly modern hardware either :P
<linkmauve> Lima isn’t involved in the display controller.
<cambrian_invader> last time I worked on this project I had a lot of trouble getting mutter to work which iirc was due to mali not supporting newer opengl
<linkmauve> Oh, it doesn’t use GLES instead of GL?
<cambrian_invader> I don't remember
<cambrian_invader> I never got it working, so take that with a grain of salt
tanty has quit [Quit: Ciao!]
tanty has joined #lima
tanty has quit []
Leopold_ has joined #lima
tanty has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
<daniels> mutter really wants ES3.0
<daniels> you should be able to use MESA_GLES_VERSION_OVERRIDE=3.0 to make it do it
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
erlehmann has joined #lima
<anarsoul|2> daniels: no ES2 support anymore?
<daniels> anarsoul|2: not for a few years aiui; ES3 definitely became mandatory when they started using glBlitFramebuffer to implement multi-GPU
<daniels> ttbomk they don't have ES3 requirements beyond what you could support as a generic Gallium driver
<anarsoul|2> IIRC lima worked fine with Gnome 40, but it's been a while, yeah
Leopold_ has quit [Remote host closed the connection]
<daniels> some would say that Mali-4xx SoCs aren't the target platform for a JavaScript-based compositor
<anarsoul|2> wow, that's been 3 years ago :)
<cambrian_invader> (tell that to my customer who wants both this specific SoC and GNOME)
<anarsoul|2> cambrian_invader: they may need a beefier SoC then :)
<cambrian_invader> they originally wanted vulkan too
<cambrian_invader> and when we said they would need to change SoCs or drop vulkan they dropped vulkan
<cambrian_invader> so I guess they are getting KDE or something
<anarsoul|2> cambrian_invader: you can always use lavapipe :)
<cambrian_invader> I believe they are looking for accelleration, not decelleration...
<daniels> I can recommend Weston
<anarsoul|2> or Sway
<cambrian_invader> I'll keep that in mind
<anarsoul|2> cambrian_invader: Wikipedia says it's 19 year old GPU. On steroids, yeah, but architecture is 19yo
<cambrian_invader> I know... I did not design the system I only get to make it work
<daniels> on low-power systems, you really want to use either Weston (works very well for systems without too much interactive window management, i.e. you run one or two apps where window management isn't governed by dragging windows around), or something wlroots-based
<daniels> I'm biased towards the one I develop though :)
erlehmann has quit [Ping timeout: 480 seconds]
erlehmann has joined #lima