ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel has landed in mainline, userspace driver is part of mesa - Logs at https://people.freedesktop.org/~cbrill/dri-log/index.php?channel=lima and https://freenode.irclog.whitequark.org/lima - Contact ARM for binary driver support!
yann has quit [Ping timeout: 256 seconds]
warpme_ has quit [Quit: Connection closed for inactivity]
camus1 has joined #lima
kaspter has quit [Ping timeout: 240 seconds]
camus1 is now known as kaspter
camus1 has joined #lima
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #lima
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #lima
camus1 has joined #lima
kaspter has quit [Ping timeout: 258 seconds]
camus1 is now known as kaspter
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
psydread has joined #lima
buzzmarshall has quit [Remote host closed the connection]
yann has joined #lima
warpme_ has joined #lima
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #lima
Barada has joined #lima
camus1 has joined #lima
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
<rellla> daniels: one more question :) ... or two ...
<rellla> the current implementation already uses an fbo/texture to be rendered on. i changed the code to use an eglImage for that. this is what kms_quad does.
<rellla> though i wonder, if i should go the eglSurface and eglSwapBuffers way because for me it seems easier to implement.
<rellla> what i am missing is, where i explicitely say that the bo from gbm_surface should go to the primary/overlay plane then?
<rellla> i guess this would be the place to do this https://gitlab.freedesktop.org/mesa/kmscube/-/blob/master/drm-legacy.c#L96
<daniels> yeah, I think the README covers the difference between gbm_bo + EGLImage vs. gbm_surface + EGLSurface
<daniels> the only real reason you want gbm_bo is if you want explicit control over buffer allocation and availability
<daniels> don't use SetPlane :)
<daniels> you really want to use the atomic modesetting API to do planes
<daniels> SetPlane has no timing guarantees
<daniels> on some platforms, it just blocks for one or two frames - on other platforms,it returns immediately
champagneg has quit [Ping timeout: 256 seconds]
champagneg has joined #lima
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
<rellla> wait...
Barada has quit [Quit: Barada]
buzzmarshall has joined #lima
yann has quit [Ping timeout: 256 seconds]
mripard has quit [Quit: Lost terminal]
mripard has joined #lima
drod has joined #lima
narmstrong has quit []
narmstrong has joined #lima
<anarsoul|2> daniels: narmstrong: are there any chances to get lima CI re-enabled any time soon?
gcl has quit [Ping timeout: 256 seconds]
gcl has joined #lima
cwabbott_ has joined #lima
cwabbott has quit [Ping timeout: 260 seconds]
cwabbott_ is now known as cwabbott
psydread has left #lima [#lima]