<sravn>
tzimmermann, mlankhorst, mripard ^^ - I think this Q is more for one of you
pcercuei has quit [Quit: leaving]
<Plagman>
MrCooper: yeah i've reported it directly as well and pointed at that bug as a source of info for reference
<Plagman>
thanks!
<Plagman>
emersion: danvet: it seems to really suck that we're the ones getting yelled at just because the thing that broke us wasn't caught right away
ella-0 has quit []
<tzimmermann>
sravn, unless the docs are misleading i wouldn't consider -fixes
ella-0 has joined #dri-devel
<Plagman>
danvet: looking at precedence, it seems to only be a subset of simon's change (only checking comm instead of comm+exe) and Christoph also seems to take issue with the idea of checking comm in the first place
<Plagman>
also i guess any process that starts with 'X' is disallowed from atomic? good thing we're not Xgamescope
kenjigashu has joined #dri-devel
Kayden has quit [Quit: off to find idr]
iive has joined #dri-devel
kenjigashu has quit []
tzimmermann has quit [Quit: Leaving]
kenjigashu has joined #dri-devel
<emersion>
yeah X is a forbidden letter now :P
<emersion>
Plagman: indeed, if we wanted to be annoying we could argue that the chromeos fix is a kernel regression and get it reverted
<Plagman>
yea
<emersion>
but sending patches to make everyone happy is better
<Plagman>
clearly it's not making everyone happy
<emersion>
… sigh
<Plagman>
i don't think i got anything useful as to how to move forward from the chrome people, let me go back and re-read again
<emersion>
i've just re-sent the patch with the conflict fixed
<emersion>
i haven't heard from the ChromeOS folks at all…
<Plagman>
i did send a note but i don't think we got much useful out of it as to how to deal with this short-term other than value jugment on amd hardware and indeterminate plans for the future
camus has quit []
<Plagman>
if you resend goes up in flames i vote we get it reverted
<Plagman>
your*
<emersion>
if we don't have a choice, i think that would make sense: iirc chromeos has internal trees anyways? so they could keep the patch in their tree
<emersion>
until they get it fixed
<bnieuwenhuizen>
weren't Rob or Emma saying something about that when it was initially discussed here?
<emersion>
yeah, they have chromeos quirks for msm
<emersion>
but i haven't found these in mainline
<emersion>
so i assume they are in google trees
<emersion>
cc robclark ^
<Plagman>
for some reason that thread isn't making it in my inbox but going by the archive link you posted, there also seems to be a lack of maintainer input in there
<Plagman>
if it got accepted in a maintainer tree it seems like the discusison should be more between core maintainer and leaf maintainer than individual devs getting screamed at, or that they should at least participate
<Plagman>
i appreciate moral support on irc but maybe insufficient in this case
<robclark>
emersion, Plagman: yeah, I think we can keep workarounds for CrOS bugs in CrOS trees.. that is what we've been doing for snapdragon/msm.. but btw, what thread is this?
<emersion>
hm seems like dri-devel isn't even CC'ed
<Plagman>
i see lkml according to the archive but it's not n my linux-kernel inbox somehow
gawin has quit [Ping timeout: 480 seconds]
<Plagman>
and i don't think i have a linux-next folder where that would have landed..
<emersion>
do you have an "utter crap" filter which makes it go directly to spam? :P
<emersion>
yeah LKML seems to be CC'ed…
<robclark>
emersion, agd5f, I think drop the CrOS workaround upstream.. and then implement it in a much simpler way (ie. not bothering to need to check the userspace process) in CrOS kernel tree
urja has quit [Read error: Connection reset by peer]
<Venemo>
HayashiEsme: depends on your areas of interest. any place is good to start
urja has joined #dri-devel
<Venemo>
which driver do you want to contribute to?
mlankhorst has quit [Ping timeout: 480 seconds]
kenjigashu has joined #dri-devel
kenjigashu has quit [Remote host closed the connection]
<emersion>
thanks agd5f
<Venemo>
correct
<Venemo>
I think it's best to start with something that motivates you personally, on hardware that you have now
<danvet>
Plagman, emersion I'm way behind on email, but imo comm check gets my ack
<danvet>
maybe poke airlied for this too
<danvet>
Plagman, also note that you can still get atomic if your Xgamescope
<danvet>
you just need to ask for atomic v2
<danvet>
so we weren't completely silly
<Plagman>
ah yea
<danvet>
ofc assuming agd5f is fine with the comm check only
<Venemo>
there are difficult bits and pieces everywhere
<Venemo>
just don't be afraid to ask questions if you're stuck
<Venemo>
we're here for you
<Plagman>
i think emersion's v2 still also gets the exe, just from some other spot that doesn't require that export?
mlankhorst has joined #dri-devel
lynxeye has quit []
<airlied>
I'm not a big fan of the exe probing tbh, since it's unversioned and has no great info in what needs to be fixed in userspace
<airlied>
like the X atomic one was pretty nutso that we had to do that
<airlied>
I'm not sure it should set a precedent
<robclark>
IMO, no real good reason for carrying CrOS workarounds upstream other than for testing upstream kernels if things are *completely* broken otherwise (and in that case maybe guard it w/ a modparam instead)
<robclark>
otherwise we can carry workaround downstream.. and drop it in sync with userspace getting fixed
<robclark>
for snapdragon/msm case.. the issue worked around is a bit more of an edge case, so doesn't get in the way of upstream testing
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
<Venemo>
HayashiEsme: if you want to start with iris, then Kayden and jekstrand are the people who may help you get started
<robclark>
Venemo, HayashiEsme, jfyi only Venemo's side of the conversation is showing up (so I guess you are both using matrix but one of you is not identified with NickServ?)
<Venemo>
Oh yes that can happen if you are connected through Matrix
<Venemo>
robclark can't see what you write as long as you're not authenticated
<robclark>
(just mentioning because I guess Kayden and jekstrand are also not seeing the other half of the conversation either ;-))
<HayashiEsme[m]>
Gosh, can everyone of OFTC see this now?
<bnieuwenhuizen>
yea
<HayashiEsme[m]>
\o/!!
<HayashiEsme[m]>
Oh my goodness that would explain a lot
<HayashiEsme[m]>
Thanks for pointing that out @robclark, NickServ is usually pretty good at telling me I'm doing something silly
<HayashiEsme[m]>
Yeah I had been trying to say hi ...but clearly only to people connected to matrix via OFTC 🤦♀️
<HayashiEsme[m]>
I'm being chased out of the bedroom by the boyfriend but I'll properly say hi in a bit, bbl -- whoops on the NickServ thing bah
<HayashiEsme[m]>
OFTC via matrix*
<Venemo>
no worries
<Venemo>
happened to me as well at some point
<anholt>
sweet. new gtest-runner for doing vaapi unit tests seems to be basically working.
lemonzest has quit [Quit: WeeChat 3.2]
Peste_Bubonica has joined #dri-devel
shashank1202 has quit [Quit: Connection closed for inactivity]
join_subline has quit [Ping timeout: 480 seconds]
join_subline has joined #dri-devel
Peste_Bubonica has quit [Quit: Leaving]
Duke`` has quit [Ping timeout: 480 seconds]
eric_engestrom__ has quit []
eric_engestrom has joined #dri-devel
<eric_engestrom>
quick reminder that the mesa 21.3 branchpoint is in a bit less than 48h :)
<eric_engestrom>
(as usual, I'm planning on doing it at around 6pm UTC, just so that you don't wait until EOD US time :)
Ahuj has quit [Ping timeout: 480 seconds]
sarnold has quit [Remote host closed the connection]
gouchi has quit [Remote host closed the connection]
thellstrom has quit [Remote host closed the connection]
thellstrom has joined #dri-devel
vivijim has quit [Ping timeout: 480 seconds]
<HayashiEsme[m]>
Goodness, I'm surprised I hadn't been barred from posting at all without registerring my nick, but here's a pastebin of the conversation between venemo and I - since I had been doing so through Matrix and not also through OFTC https://paste.ubuntu.com/p/MfwdgF6fDw/
pushqrdx has quit [Remote host closed the connection]
bl4ckb0ne has quit [Read error: Connection reset by peer]