Company has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
nchery has joined #dri-devel
mvlad has joined #dri-devel
sgruszka has joined #dri-devel
Cyrinux9474 has joined #dri-devel
Cyrinux947 has quit [Ping timeout: 480 seconds]
rasterman has joined #dri-devel
yyds has joined #dri-devel
dviola has joined #dri-devel
yyds has quit [Quit: Lost terminal]
yyds has joined #dri-devel
yyds has quit []
Leopold_ has joined #dri-devel
yyds has joined #dri-devel
yyds has quit []
yyds has joined #dri-devel
alanc has quit [Remote host closed the connection]
<yyds>
hello, I ask a question, what diffrent between dri-driver(/usr/lib/dri/*) and gallium-pipi(/usr/lib/gallium-pipe/*) driver?
alanc has joined #dri-devel
rz has quit [Remote host closed the connection]
rz has joined #dri-devel
kzd has quit [Ping timeout: 480 seconds]
frieder has joined #dri-devel
frieder has quit [Remote host closed the connection]
frieder has joined #dri-devel
Haaninjo has joined #dri-devel
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
kts has joined #dri-devel
ngcortes has joined #dri-devel
rgallaispou has joined #dri-devel
ngcortes has quit [Ping timeout: 480 seconds]
tursulin has joined #dri-devel
kxkamil has quit []
kts has quit [Quit: Konversation terminated!]
kxkamil has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
lynxeye has joined #dri-devel
aravind has joined #dri-devel
sarahwalker has joined #dri-devel
jkrzyszt has joined #dri-devel
fab has quit [Quit: fab]
dliviu has quit [Ping timeout: 480 seconds]
dliviu has joined #dri-devel
heat has joined #dri-devel
fab has joined #dri-devel
kts has joined #dri-devel
pcercuei has joined #dri-devel
cmichael has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
illwieckz has quit [Ping timeout: 480 seconds]
illwieckz has joined #dri-devel
illwieckz has quit [Remote host closed the connection]
dsrt^ has quit [Remote host closed the connection]
<MTCoster>
For VK_EXT_physical_device_drm, does anyone know if the primary node is supposed to be for the GPU or the display? The spec wording is vague but seems to lean towards GPU, but a lot of software seems to use it for display. I know a lot of hardware doesn't differentiate, but still
rz_ has joined #dri-devel
rz has quit [Remote host closed the connection]
<dj-death>
MTCoster: for display
<dj-death>
MTCoster: by default Anv for example uses the render node
nashpa has joined #dri-devel
dliviu has quit [Ping timeout: 480 seconds]
<emersion>
MTCoster: are you wondering about split render/display?
<MTCoster>
In pvr-land, the display is always a separate drm device to the gpu itself so the distinction matters for us
<emersion>
i don't think it's a good idea to carry over the mistakes of mesa's renderonly
kts has quit [Ping timeout: 480 seconds]
<emersion>
i'd expose one VkPhysicalDevice for the DRM render node
<emersion>
with primary of the render device
<emersion>
and leave the separate display device alone, it has nothing to do with vulkan
<MTCoster>
That was my initial thought, but it comes into play with VK_KHR_display
<MTCoster>
And some software seems to assume the primary drm node returned is for the display
<emersion>
what is "some software"?
<emersion>
VK_KHR_display is unrelated to the physical device
<emersion>
VK_EXT_physical_device_drm queries the physical device only, not what VK_KHR_display might use
<MTCoster>
The example I have on hand is the one given in !11616, swvkc
<MTCoster>
Gotcha, will stick with the render primary
<emersion>
returning the display device is causing lots of pain on the GL path
<MTCoster>
Is there an equivalent extension for obtaining the display node?
lanodan has quit [Quit: WeeChat 3.8]
lanodan has joined #dri-devel
simon-perretta-img has joined #dri-devel
kts has joined #dri-devel
mal has quit [Quit: leaving]
heat_ has joined #dri-devel
heat has quit [Read error: Connection reset by peer]
mal has joined #dri-devel
samuelig has quit [Quit: Bye!]
<emersion>
no
<emersion>
and i don't think there should be
<emersion>
it would be very useful to have a way to figure out that a VkPhysicalDevice can be used with a display device
<emersion>
but i don't think it should be a "try using it then figure out what display node the driver picked" kind of thing
samuelig has joined #dri-devel
heat_ has quit [Remote host closed the connection]
heat has joined #dri-devel
alyssa has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
yyds has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
smiles_1111 has joined #dri-devel
Cyrinux9474 has quit []
kts has joined #dri-devel
Cyrinux9474 has joined #dri-devel
heat has quit [Read error: Connection reset by peer]
heat has joined #dri-devel
heat_ has joined #dri-devel
heat has quit [Read error: No route to host]
yyds has joined #dri-devel
sima has joined #dri-devel
sgruszka has quit [Remote host closed the connection]
heat has joined #dri-devel
heat_ has quit [Read error: No route to host]
Company has joined #dri-devel
orbea has quit [Remote host closed the connection]
a-865 has quit [Quit: ChatZilla 0.17b1 [SeaMonkey 2.53.17/20230610105000]]
glennk has quit [Read error: Connection reset by peer]
fxkamd has quit []
fxkamd has joined #dri-devel
fab has quit [Quit: fab]
fab has joined #dri-devel
glennk has joined #dri-devel
fab has quit []
fab has joined #dri-devel
fab has quit []
fab has joined #dri-devel
JohnnyonFlame has joined #dri-devel
Leopold_ has quit [Remote host closed the connection]
a-865 has joined #dri-devel
benjaminl has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
Leopold_ has joined #dri-devel
rgallaispou has left #dri-devel [#dri-devel]
aissen has quit [Ping timeout: 480 seconds]
aissen has joined #dri-devel
junaid has joined #dri-devel
junaid has quit []
junaid has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
frieder has quit [Remote host closed the connection]
cmichael has quit [Quit: Leaving]
MrCooper has quit [Remote host closed the connection]
illwieckz has joined #dri-devel
MrCooper has joined #dri-devel
sarahwalker has quit [Ping timeout: 480 seconds]
MrCooper_ has joined #dri-devel
mceier has quit [Quit: leaving]
aravind has quit [Ping timeout: 480 seconds]
MrCooper has quit [Ping timeout: 480 seconds]
rasterman has joined #dri-devel
MrCooper_ is now known as MrCooper
bgs has joined #dri-devel
heat has quit [Read error: No route to host]
heat has joined #dri-devel
aissen has quit [Ping timeout: 480 seconds]
aissen has joined #dri-devel
tursulin has quit [Ping timeout: 480 seconds]
<dcbaker>
kusma: that devenv issue is caused by the `pkgconfig` module being imported but unusued. the easiest work around is to turn on any OpenGL driver (say radeonsi), which will use the module. The fix is already landed for 1.2.1
smiles_1111 has quit [Ping timeout: 480 seconds]
aissen has quit [Ping timeout: 480 seconds]
aissen has joined #dri-devel
<kusma>
Yeah, I saw from the issue tracker. But thanks for the info!
<dcbaker>
cool
lynxeye has quit [Quit: Leaving.]
yyds has quit [Remote host closed the connection]
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit []
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
xypron has quit [Ping timeout: 480 seconds]
gouchi has joined #dri-devel
gouchi has quit [Remote host closed the connection]
jkrzyszt_ has joined #dri-devel
jkrzyszt has quit [Ping timeout: 480 seconds]
a-865 has quit [Quit: ChatZilla 0.17b1 [SeaMonkey 2.53.17/20230610105000]]
Leopold_ has quit [Ping timeout: 480 seconds]
a-865 has joined #dri-devel
<alyssa>
jenatali: test-dozen-deqp has been really slow today, any idea what's up?
<jenatali>
alyssa: Blame whoever else is using the runners
<alyssa>
I don't mean the queued time or infra
<alyssa>
I mean it's spending 20+ minutes in deqp itself
<alyssa>
if that's normal.. then the job needs to be split in 2
<alyssa>
either we need twice as many runners available for it, or the fraction needs to be halved
<jenatali>
They're shared among other fdo projects
<alyssa>
is that special to the microsoft jobs?
<alyssa>
*windows
<alyssa>
or I guess special to the software rasterizer jobs?
<jenatali>
No, the Linux runners aren't dedicated for Mesa either
<jenatali>
Oh sure the hardware runners I guess are, but the build runners aren't
<alyssa>
ok..
<alyssa>
well I was told if runtimes are high it's because everything's on fire but
<alyssa>
I guess I should close gitlab and pretend I didn't see anything and we can all pretend I didn't say anything
<alyssa>
squirrel!
<jenatali>
I wish we had dedicated runners, but despite the size of my company, it's incredibly hard to get those kinds of resources allocated for a project like our drivers in Mesa
<jenatali>
So, we provide keys and then Collabora manages the runners for us
<zmike>
the execs know that if the drivers don't work nobody can see the problems
nchery has quit [Ping timeout: 480 seconds]
nchery has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
<dcbaker>
zmike: I've got a bunch of unexpected passes on the 23.2 branch with zink, you got any ideas or would you like me to just mark them as expected and move on? https://gitlab.freedesktop.org/mesa/mesa/-/pipelines/944410 (zink-radv-vangough-valve)
<zmike>
hm I vaguely recall seeing those fixed
<zmike>
so probably mark xpass
<dcbaker>
Sweet, thanks
Haaninjo has joined #dri-devel
tango_ has joined #dri-devel
mvlad has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
mceier has joined #dri-devel
Omax has joined #dri-devel
xypron has joined #dri-devel
lemonzest has quit [Quit: WeeChat 3.6]
lemonzest has joined #dri-devel
dos1 has joined #dri-devel
jkrzyszt_ has quit [Ping timeout: 480 seconds]
bgs has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
sima has quit [Ping timeout: 480 seconds]
YuGiOhJCJ has joined #dri-devel
Duke` has quit [Ping timeout: 480 seconds]
pcercuei has quit [Quit: dodo]
glennk has quit [Read error: Connection reset by peer]