10:37 <mntmn> time to test-drive the latest mesa on gc7000l...

10:57 <mntmn> now building with !7603 !9310 !9780 !9871

10:57 <mntmn> anything else i should test?

11:12 <marex> mntmn: neverball

11:12 <marex> mntmn: btw have you ever used the devcoredump with etnaviv ?

11:13 <marex> austriancoder: any hint on what to look for in the decoded traces ?

11:13 <mntmn> marex: will test. yes, i have used that but like forever ago, so my memory of that is near 0

11:13 <austriancoder> marex: that link is dead

11:13 <marex> mntmn: the patches are now in, so it should work

11:13 <marex> austriancoder: which link ?

11:13 <marex> oh

11:13 <austriancoder> marex: https://paste.debian.net/hidden/8f004c79/

11:13 <mntmn> marex: yep, i saw

11:14 <austriancoder> marex: maybe send me the dumb via mail

11:14 <marex> austriancoder: I would like to learn it though :)

11:15 <marex> austriancoder: anyway, see email

11:17 <austriancoder> marex: maybe its time for a blog post.. so everybody can read up the knowledge

11:17 <marex> austriancoder: I think that's long overdue in fact

11:26 <austriancoder> marex: fine.. I will prep something - but now I am out for a short bike tour as the weather here is so wonderful

11:27 <marex> austriancoder: no worries, have fun

11:33 <mntmn> ok, at least one of those 4 patches made glxinfo segfault and cause really funky corruption. i'm now on mesa master without any extra MRs.

11:33 <mntmn> marex: neverball looks good!

11:33 <mntmn> incl. sprites

11:35 <marex> mntmn: reflective surfaces are still broken (the NEVERBALL text in main menu) I think

11:36 <marex> mntmn: good thing about the point sprites, thanks for checking

11:36 <mntmn> i have a good new pathological case

11:36 <mntmn> it was already there in my last mesa build, but is still there on master: dropdowns in firefox cause a flickery mess

11:37 <mntmn> wayland-native firefox, that is

11:38 <marex> mntmn: hold on

11:38 <marex> mntmn: try applying weston MR570

11:38 <marex> (if you are on weston that is)

11:38 <mntmn> i'm using sway :D

11:38 <marex> mntmn: see the MR anyway, and MR568

11:38 <marex> mntmn: it might just be related

11:39 <mntmn> something about keyboard?!

11:40 <mntmn> marex: the bug that i'm seeing is def. an etnaviv problem. i'll make short video

11:41 <marex> mntmn: yeah, on keyboard-less devices, the chromium dropdown menus were randomly placed with weston , it worked on devices with keyboards , problem was in top level surface focus

11:41 <mntmn> marex: i think that is extremely unrelated

11:41 <marex> ok

11:42 <mntmn> one sec, i'll show you

11:43 <mntmn> marex: http://dump.mntmn.com/etnaviv-firefox-dropdown-flicker.mov

11:44 <mntmn> it's this typical double buffer confusion that can happen from time to time, but in this case it's 100% reproducible

11:45 <mntmn> will now try some MRs one by one

11:58 <mntmn> austriancoder: hey, last time i checked !9871 i probably made a mistake. it absolutely works. fixes alpha test in kicad 3d viewer for example

12:01 <mntmn> marex: maybe not a etnaviv bug after all, just looks like one https://bugzilla.mozilla.org/show_bug.cgi?id=1552020

12:02 <mntmn> > This issue was identified as a damage tracking issue in sway for subsurfaces attached to xdg_popups

12:09 <mntmn> upgraded sway to latest master and it is indeed fixed.

12:09 <mntmn> nice.

12:10 <mntmn> interesting, firefox with accelerated layers now works on latest mesa (before, there was a shader compiler crash). but introduces new interesting flickering.

12:15 <marex> mntmn: now that looks like my glmark2 cat pictures corruption :)

12:15 <marex> mntmn: oh ...