01:11 <tlwoerner> yea!

01:19 <alyssa> tlwoerner: yea?

01:19 <tlwoerner> "yea" alyssa is back (?)

01:23 <tlwoerner> nobody else seemed excited, but i thought it warranted at least a "yea!"

01:23 <HdkR> yay \o/

01:26 <cphealy> yea!

01:32 <alyssa> pfheh thanks :p

01:32 <alyssa> the folks in #asahi will not be so enthusiastic :-p

06:22 <chewitt> @alyssa I'm watching the XDC talk

06:22 <chewitt> it appears Canada has assimilated you

06:22 <chewitt> repeated use of "aboot" instead of "about" :D

10:31 <alyssa> uh. oops. :-p

10:37 <alyssa> the trouble with "assimilation" into Canada is that there are a dozen distinct Canadian accents, and in the major cities you're liable to hear... all of them.

10:38 <alyssa> (and in the cities large numbers of people speak English as a second language)

10:46 <robmur01> apologetic... so Canadian :P

11:04 <robmur01> BTW, I reckon that "supporting" T62x would probably want to wait until we've made the two halves of T628 reliably talk to each other

11:04 <alyssa> ...oh. right. that.

11:04 <robmur01> otherwise the most likely result will be a flood of broken ODroids

11:12 <robmur01> FWIW I've now got the CTS to the point of actually running tests on my Juno, under real X - xvfb seems insistent on trying to use swrast even though I've compiled it out. However X refuses to start on T620/T720 for reasons undetermined :(

11:13 <robmur01> (also I guess I need to replace cts-runner with Mesa's equivalent so it can tolerate crashes)

11:22 <alyssa> Weee

12:27 <tomeu> robmur01: you can probably reuse mesa's kernel and rootfs for that

12:27 <tomeu> and maybe even the scripts

12:36 <robmur01> tomeu: oh, are there images somewhere accessible? I did try picking through the CI directory to see if there might be any clues about how the rootfs gets made, but quickly got lost

12:37 <tomeu> robmur01: you can download them from the same place where the boards downloads them: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/13731826

15:39 <rtp> robmur01: what did you meant by "two halves of T628" ?

15:43 <robmur01> rtp: T628 can have two "core groups", where each group (of up to 4 cores) has its own separate L2 cache and they are not coherent with each other

15:44 <robmur01> Consider it a bit like a T624 glued to a second T624 minus its tiler

15:44 <rtp> oh...

15:44 <HdkR> robmur01: Is that feature gone in newer generations btw?

15:45 <HdkR> "feature"

15:49 <rtp> what about T60x (eg T604) ? same kind of "feature" ?

15:50 <robmur01> The fact that all subsequent GPUs present as a single core group (or at least coherent core groups) probably says it all ;)

15:51 <chewitt> @alyssa You need this t-shirt https://www.ebay.com/itm/165069257423?hash=item266ee4facf:g:m3IAAOSw3f1g63D-

15:51 <robmur01> rtp: I believe there was technically a T608, but I have no idea if anyone ever built one. AFAIK T6x4 is always a single group of 1-4 cores

15:52 <HdkR> robmur01: Nice. I didn't track the hardware enough to know if it was still around. Is there a new extension for async compute tasks to not mess with graphics as much? Vulkan queues or something?

15:54 <robmur01> and of course technically you could have built a 4-core T628 - dunno if that would always be 2+2 or whether 3+1 or 4+0 would be valid configs, and there's no way I'm dredging up the RTL bundle to try to find out :P

15:55 <robmur01> hey, don't ask me about APIs, I just read the hardware manuals!

15:55 <HdkR> :>

15:58 <HdkR> Looks like the blob exposes two identical queues that likely run async

16:39 <tlwoerner> chewitt: lol "May not ship to Canada - Read item description or contact seller for shipping options."

17:52 <alyssa> I did not realize the day after XDC is the International Roast Alyssa's Accent Day :-p

17:56 <HdkR> I didn't realize that's how it works

20:11 <Lyude> alyssa: Lol I also noticed your accent had increased since last time

20:11 <Lyude> mupuf's definitely did as well

21:11 <alyssa> Lyude: oh right it is still International Roast Alyssa's Accent Day

21:11 <Lyude> :P

22:02 <JulianGro> Is there any demand for open-source GLES 3.2 software? I got Vircadia running on my RockPro64 and there isn't too many issues.

22:17 <alyssa> Hmm?

22:22 <anholt_> if your GL rendering is interesting and unusual, then getting a trace into https://gitlab.freedesktop.org/gfx-ci/tracie/traces-db gives us a way to make sure your stuff works across drivers going forward.

22:23 <JulianGro> Oh yeah I can do that. We do have some rare rendering issues we haven't been able to track down, but on panfrost there is definitely some more than that (which I assume is down to me using GLES 3.2 which isn't supported)

22:24 <alyssa> GLES 3.2 is not supported, but GLES 3.2 is just GLES 3.1 plus a bunch of funny Android extensions

22:24 <alyssa> and we support (on Mali-G52 at least) GLES 3.1 and a few of the extensions cherry-picked for 3.2

22:25 <JulianGro> Is there plans to support 3.2, or is that likely never going to happen?

22:40 <alyssa> 🤷

22:40 <alyssa> Huge amount of work for very little effort. The useful extensions should be advertised already on bifrost.

22:43 <robclark> mmm, some people think that geom/tess is useful..

22:48 <JulianGro> I guess that means that our software should probably check for GLES 3.1 + extensions instead of GLES 3.2

22:50 <robclark> I *always* recommend checking for lower gl version + extensions you actually need

23:12 <alyssa> JulianGro: 💯

23:12 <alyssa> Probably actually ES 3.0 + extensions but I guess ES3.1 on any modern part is standard now

23:12 <alyssa> ES3.0->ES3.1 is just a lot of effort :-p

23:35 <robclark> if you don't need compute shaders, then looking for gles30 + extensions will open up some more options.. but I guess if you do need compute shaders you might as well look for gles31+extensions

23:46 <JulianGro> I will actually have to go find out a lot more about how all of this stuff works. The engine that Vircadia uses is basically a hand-me-down and we only have a single person that seems to have an idea what they are doing while also having barely any time to invest. That should definitely be the next kind of area that I take a look at and see if I can make some sense or contribute some info on some of our issues.