heat has quit [Read error: Connection reset by peer]
heat has joined #dri-devel
glennk has joined #dri-devel
yuq825 has joined #dri-devel
archbirdplus has quit [Ping timeout: 480 seconds]
aravind has quit [Remote host closed the connection]
aravind has joined #dri-devel
kzd has quit [Ping timeout: 480 seconds]
mszyprow has joined #dri-devel
archbirdplus has joined #dri-devel
sima has joined #dri-devel
frieder has joined #dri-devel
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #dri-devel
vliaskov has joined #dri-devel
rasterman has joined #dri-devel
mszyprow has quit [Remote host closed the connection]
mszyprow has joined #dri-devel
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
camus has quit [Read error: Connection reset by peer]
camus has joined #dri-devel
lynxeye has joined #dri-devel
Company has joined #dri-devel
JohnnyonFlame has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
Haaninjo has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
archbirdplus has quit [Ping timeout: 480 seconds]
alatiera has quit [Quit: Connection closed for inactivity]
tursulin has joined #dri-devel
archbirdplus has joined #dri-devel
i509vcb has quit [Quit: Connection closed for inactivity]
rsalvaterra has quit [Ping timeout: 480 seconds]
hansg has joined #dri-devel
pcercuei has joined #dri-devel
yyds_ has joined #dri-devel
archbirdplus has quit [Ping timeout: 480 seconds]
yyds has quit [Ping timeout: 480 seconds]
flom84 has joined #dri-devel
flynnjiang has quit [Quit: flynnjiang]
kathleen_ has joined #dri-devel
vliaskov has quit [Read error: Connection reset by peer]
archbirdplus has joined #dri-devel
frieder has quit [Remote host closed the connection]
aravind has quit [Ping timeout: 480 seconds]
flom84 has quit [Quit: Leaving]
archbirdplus has quit [Ping timeout: 480 seconds]
frieder has joined #dri-devel
kts has joined #dri-devel
kts has quit []
kts has joined #dri-devel
mvlad has joined #dri-devel
shoragan has quit [Read error: Network is unreachable]
pH5 has quit [Read error: Network is unreachable]
vliaskov has joined #dri-devel
lynxeye has quit [Read error: Network is unreachable]
yyds has joined #dri-devel
lynxeye has joined #dri-devel
yyds_ has quit [Read error: Connection reset by peer]
shoragan has joined #dri-devel
ADS_Sr has quit [Ping timeout: 480 seconds]
ShibaInu has quit []
Shibe has joined #dri-devel
<jani>
so the vesa e-ddc spec says we should try to read displayid from address 0xa4 before reading edid from 0xa0. we currently don't. I've been curious if displays commonly populate the displayid ddc address. we never probe it, so we have no idea
<jani>
I wrote some patches to do just that, and sent them to the intel ci trybot
<jani>
looks like very few of the displays in our ci respond to the displayid ddc address
<jani>
I found three that do. two of them have the regular edid header 00 ff ff ff ff ff ff 00 which is wrong for data in the displayid ddc address. *sigh*. one of them responds with all 00, all 66, or all 22. *facepalm*
<ccr>
not knowing much about the topic, but what I've heard about EDID etc conformance, that somehow does not surprise me at all
<jani>
in conclusion, if you had any hopes that a dedicated displayid at a dedicated ddc address would make things better, and reduce legacy, forget it. same shit, new ddc address
<jani>
ccr: yeah
<ccr>
with such things, it seems like it's often the case of https://xkcd.com/927/ but with the addition that it's another standard nobody complies with
<jani>
so far all the displays will populate the edid at its address, with displayid data in edid extension blocks, because that's backwards compatible with old source devices
Leopold_ has quit [Remote host closed the connection]
Leopold has joined #dri-devel
mvlad has quit [Ping timeout: 480 seconds]
<jani>
this is where I say I think Postel was wrong :p
<jani>
basically "be liberal in what you accept" in this context means no matter what garbage a display has for an EDID, we try very hard to interpret it as if it was meaningful, and get a picture on screen
<jani>
if windows outright rejected EDIDs that don't follow the spec, we'd only have standards compliant EDIDs out there
<jani>
/rant
glennk has quit [Ping timeout: 480 seconds]
glennk has joined #dri-devel
jsa has joined #dri-devel
mvlad has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
rgallaispou has joined #dri-devel
archbirdplus has joined #dri-devel
bmodem has quit [Ping timeout: 480 seconds]
ungeskriptet is now known as Guest11039
ungeskriptet has joined #dri-devel
archbirdplus has quit [Ping timeout: 480 seconds]
Guest11039 has quit [Ping timeout: 480 seconds]
aravind has joined #dri-devel
macslayer has quit [Remote host closed the connection]
Lyude has quit [Ping timeout: 480 seconds]
yyds has quit [Remote host closed the connection]
aravind has quit [Ping timeout: 480 seconds]
Lyude has joined #dri-devel
Daanct12 has quit [Quit: WeeChat 4.1.2]
archbirdplus has joined #dri-devel
kts has joined #dri-devel
kts has quit []
archbirdplus has quit [Ping timeout: 480 seconds]
yuq825 has quit []
kts has joined #dri-devel
azsxdcz has joined #dri-devel
azsxdcz has quit []
yann-kaelig has joined #dri-devel
Leopold has quit [Remote host closed the connection]
mszyprow has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
junaid has joined #dri-devel
junaid_ has joined #dri-devel
glennk has quit [Ping timeout: 480 seconds]
glennk has joined #dri-devel
junaid has quit [Ping timeout: 480 seconds]
junaid_ has quit [Remote host closed the connection]
junaid has joined #dri-devel
junaid has quit [Ping timeout: 480 seconds]
<bl4ckb0ne>
there's no entry in doc/features.txt for EGL exts?
yann-kaelig has quit []
yann-kaelig has joined #dri-devel
yann-kaelig has quit []
<karolherbst>
jenatali: `get_global_size` is broken :')
<jenatali>
karolherbst: elaborate
<karolherbst>
it doesn't account for lowered huge workgroups
<karolherbst>
ehh huge grids
<jenatali>
Oh, we don't actually have a sysval for that so I have to pass it through a side channel anyway
<karolherbst>
yeah...
<karolherbst>
well.. we have num_workgroups
<karolherbst>
guess the frontend could kinda handle that, but...
<jenatali>
Right, you'll need to disable whatever sysval is reporting that and pass it through a ubo like the offsets themselves
<karolherbst>
I was actually wondering to clean up all that sysval mess properly
<karolherbst>
like
puck_ has quit [Remote host closed the connection]
<karolherbst>
rename/split them properly between "driver" and "api" versions, and drivers never should have to implement the API ones
puck_ has joined #dri-devel
<karolherbst>
atm it's kinda a mess
<karolherbst>
maybe keep the names...
<karolherbst>
but then uhh.. the frontend doesn't really know what the hardware supports anyway
<karolherbst>
but yeah...
<karolherbst>
I guess lowering the num_workgroups to a constant ubo pull is probably the cheapest solution here...
<jenatali>
Yeah having a clean split is hard, there's a lot of details that only the driver knows
<karolherbst>
no point in doing the math in the kernel
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #dri-devel
archbirdplus has joined #dri-devel
kts has quit [Remote host closed the connection]
lemonzest has quit [Quit: WeeChat 4.1.2]
kts has joined #dri-devel
archbirdplus has quit [Ping timeout: 480 seconds]
lemonzest has joined #dri-devel
jsa has quit []
macslayer has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
Aura has quit [Ping timeout: 480 seconds]
kzd has joined #dri-devel
gpiccoli_ is now known as gpiccoli
kts has quit [Read error: Connection reset by peer]
kts has joined #dri-devel
<karolherbst>
okay done.. 🙃 that wasn't too hard actually
hansg has quit [Quit: Leaving]
<karolherbst>
nice.. seems to work on my rpi4 :3
<karolherbst>
now half of math_bruteforce isn't crashing anymore :D
<jenatali>
Nice
<karolherbst>
but there is a second benefit: I've added an env variable so users can reduce the grid size drivers support in order to work around the kernel nuking long running jobs
<karolherbst>
need to test if it actually helps or if I also have to flush more often
<karolherbst>
I have some bug reports on iris where this should help
Duke`` has joined #dri-devel
mbrost has joined #dri-devel
<karolherbst>
now the only big item left are splitting textures and samplers inside v3d :'(
<jenatali>
karolherbst: Pretty sure I have a pass that helps with that
<karolherbst>
it's wrong in the gallium driver
<jenatali>
Right
<karolherbst>
v3d kinda only works with gl atm as they simply assume they appear in pairs
<karolherbst>
shouldn't be hard to fix, just.. uhh.. work
kts has quit [Quit: Leaving]
ADS_Sr has joined #dri-devel
vliaskov_ has joined #dri-devel
vliaskov has quit [Ping timeout: 480 seconds]
sarnex has quit [Read error: Connection reset by peer]
jsa has joined #dri-devel
sarnex has joined #dri-devel
<karolherbst>
oh no.. regressions :(
mszyprow has joined #dri-devel
<karolherbst>
unrelated problem.. I've added an assert drive-by and it triggers :')
<karolherbst>
might actually fix other issues
digetx is now known as Guest11066
digetx has joined #dri-devel
Guest11066 has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
<abhinav__>
pq Hi, I had a question about https://patchwork.freedesktop.org/patch/572343/. So this series is not actually using the UAPI's struct drm_mode_solid_fill but actually just a local IGT struct equal in size to the UAPI one. For demonstrating IGT usage for UAPI changes, is the usual flow that we first make libdrm change for the UAPI, wait for it to
<abhinav__>
merge and then uprev IGT's libdrm version and use that UAPI?
vliaskov has joined #dri-devel
jsa has quit []
rsalvaterra has joined #dri-devel
sima has quit [Quit: Leaving]
sima has joined #dri-devel
vliaskov_ has quit [Ping timeout: 480 seconds]
archbirdplus has joined #dri-devel
mbrost_ has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
mbrost has joined #dri-devel
mbrost_ has quit [Ping timeout: 480 seconds]
vliaskov has quit [Ping timeout: 480 seconds]
archbirdplus has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Remote host closed the connection]
gouchi has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
gouchi has quit [Remote host closed the connection]
FireBurn has joined #dri-devel
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
Duke`` has joined #dri-devel
lynxeye has quit [Quit: Leaving.]
mbrost has quit [Remote host closed the connection]
rz has joined #dri-devel
<kchibisov>
Is EGLSurface thread safe (like can you send it between threads)? I see that EGL spec says that the API is thread safe. I just remember that wayland platform creates queues, and I'm not sure you can send them?
sgm has quit [charon.oftc.net dacia.oftc.net]
rz_ has quit [charon.oftc.net dacia.oftc.net]
tursulin has quit [Ping timeout: 480 seconds]
sgm has joined #dri-devel
frieder has quit [Remote host closed the connection]
gouchi has joined #dri-devel
junaid has joined #dri-devel
<daniels>
kchibisov: queues are totally fine; the rule is just that you can only dispatch a queue from one thread at a time, and it represents one context of execution
<daniels>
that's ok with EGL, because you can only have one context current on one thread at a time
fab has joined #dri-devel
<kchibisov>
So sending EGLSurface around is fine? I just know that you sort of need to handle callbacks, etc?
<kchibisov>
I'd assume that I need to make surface not-current and then send, so it'll be _safe_?
<kchibisov>
From what I understand there's a current context and current surface concepts, and they are not tied to each other. Since you can make context current without any surface just fine, but you can't send it unless you make it non-current.
Mangix has quit [Ping timeout: 480 seconds]
gouchi has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
<DavidHeidelberg>
btw. he didn't exactly catch what is affected in the commit messages (except the .*other part)
<DavidHeidelberg>
previously all these tests has been skipped
junaid has quit [Remote host closed the connection]
gouchi has joined #dri-devel
gouchi has quit [Remote host closed the connection]
Mangix has joined #dri-devel
<robclark>
that is... weird.. without looking closely at the test, a quick look at the commit looks like it is making things _more_ restrictive
<robclark>
looking at the result .xml, the failure looks like maybe a color precision issue or maybe srgb confusion or something like that
<robclark>
the rendered vs reference is close, just slightly off in color
junaid_ has joined #dri-devel
csloif^ has quit [Remote host closed the connection]
mszyprow has joined #dri-devel
Mangix has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
<daniels>
kchibisov: a surface is only current with respect to a context - so just make sure that you don't have the context active in more than one thread (eglMakeCurrent will fail if you try) and you'll be totally fine. there are no callbacks in EGL so no concerns there
glehmann_ has joined #dri-devel
Venemo has joined #dri-devel
mszyprow has quit [Ping timeout: 480 seconds]
glehmann_ has quit []
glehmann has joined #dri-devel
archbirdplus has joined #dri-devel
Leopold_ has quit [Remote host closed the connection]
junaid_ has quit []
archbirdplus has quit [Ping timeout: 480 seconds]
gouchi has joined #dri-devel
gouchi has quit []
archbirdplus has joined #dri-devel
gouchi has joined #dri-devel
gouchi has quit []
gouchi has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
mbrost has joined #dri-devel
gouchi has quit [Remote host closed the connection]
gouchi has joined #dri-devel
Mangix has joined #dri-devel
fab has quit [Ping timeout: 480 seconds]
gouchi has quit [Remote host closed the connection]
gouchi has joined #dri-devel
gouchi has quit []
tlwoerner__ has quit []
tlwoerner has joined #dri-devel
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
thaytan has quit [Ping timeout: 480 seconds]
mbrost has quit [Remote host closed the connection]