2023-03-13
00:01nick_ has left #asahi-dev [#asahi-dev]
00:44kesslerd_ has quit [Quit: Konversation terminated!]
00:45kesslerd has joined #asahi-dev
00:49stipa is now known as Guest7513
00:49Guest7513 has quit [Read error: Connection reset by peer]
00:49stipa has joined #asahi-dev
00:52kesslerd has quit [Remote host closed the connection]
00:54barrett has quit [Ping timeout: 480 seconds]
01:08barrett has joined #asahi-dev
01:13kesslerd has joined #asahi-dev
01:14kesslerd has quit []
01:17eiln has quit [Remote host closed the connection]
01:23eiln has joined #asahi-dev
02:25systwi has joined #asahi-dev
02:29systwi_ has quit [Ping timeout: 480 seconds]
02:33zef_ has joined #asahi-dev
02:40zef has quit [Ping timeout: 480 seconds]
03:22barrett has quit [Ping timeout: 480 seconds]
03:25barrett has joined #asahi-dev
03:41chip_x has joined #asahi-dev
03:46chipxxx has quit [Ping timeout: 480 seconds]
04:05barrett has quit [Ping timeout: 480 seconds]
05:03marcanI can't debug it with gdb because gdb is *also* broken (known upstream bug, fixed in main)
05:04marcanmeanwhile the kwin blur glitches are horrible but not only that, sometimes I get cursor redraw glitches even with blur disabled which tells me there is a deeper problem
05:05marcanI suspect half of this is bugs unrelated to us but I am not patching random KDE packages and we know we can't upstream anything to ALARM
05:06marcanjannau: how practical would it be to get cursor planes into dcp? that would at least alleviate the worst of the kwin issues I think
05:08marcanat this point I'm half tempted to just throw the towel on ALARM and switch to Fedora and get everything sorted out there, I know I can get this stuff fixed on short notice
05:13marcanthe cursor redraw glitches go away at 100/200% so this is totally yet another kwin fractional scaling bug... sigh.
05:56c10l57 has joined #asahi-dev
05:56c10l5 has quit [Read error: Connection reset by peer]
06:16jannaumarcan: we need a solution to deal with a partially off-screen cursor. I want to try if I can get away with adding 32 pixels to the stride and map it between a transparent page. that should give us 31 pixels transparency horizontally/vertically to work around dcp's limitation
06:19jannauwe can of course also deal with it by copying the visible part of the cursor to a shadow buffer if it is partially offscreen
06:48jannauI don't follow. inpractice we have the issue at the bottom and right screen edge so source x/y are always 0
06:51dottedmaga stupid question: if it's RGBA (it's RGBA, right?) can we play with w/h/stride of the buffer to tell DCP that the plane is exactly the size to fit on screen (and thus effectively hide the part of buffer that'd be rendered offscreen)
06:54dottedmagSomething like this (assuming that DCP has a notion of a stride): https://gist.github.com/dottedmag/4f48d81c143d56b93249926ec1d29bd7
06:56jannaumarcan: sigh, the surface limitations are biting us as well surf[2] doesn't overlay on surf[1] (with our current code), surf[1] on top of surf[0] does but uses overlays the background as well
06:57jannaudottedmag: the issue is that dcp expects an overlay to have at least 32x32 pixels on screen, if not it starts scaling the overlay
07:04dottedmagjannau: So this is also a problem for small cursors, not only partially off-screen ones, right?
07:10jannaulol, I found a solution for the bottom edge. I can display the cursor offscreen as long as src and dst rect have a width of at least 32x32
07:40jannaualso we can't support a2rgb10 cursors, which kde uses. I was under the impression that the cursor fb is supposed to be argb32
07:41chadmed has quit [Remote host closed the connection]
07:48chadmed has joined #asahi-dev
07:49ChaosPrincessin case it matters - i can also confirm cursor redraw leaving garbage in a square-shaped patter around cursor on plasma. didnt report it at first cause running gentoo, not arch, but apparently its not just my distro being broken.
07:58jannauI see have cursor artifacts pretty consistently on the panel but nowhere else with fractional scaling
08:00eiln has quit [Quit: Page closed]
08:02chadmedChaosPrincess: i try very hard to not release broken garbage so whatever state gentoo is in is what is going on in asahi
08:03chadmedthe only cursor artefacts ive noticed is occasionally a thick black outline appearing around it but it seems completely random
08:04ChaosPrincessi have a smashed together install with some packages from overlay and some from my own weird scripts, but iirc mesa is overlay
08:10jannauhave you tried booting with arm64.nobti / arm64.nopauth to rule out bti/pac issues if you're testing fedora? I suppose valgrind doesn't support that
08:14marcanif it's a race it's probably going to depend on nonsense like how big my taskbar is and what widgets I have on it
08:34marcanok wtaf this is a pthread mutex under the hood and as far as I can tell it is unlocked and locking it deadlocks
08:49___nick___ has joined #asahi-dev
09:08marcanthe asan hooks end up with it doing a rlock -> (asan) -> wlock -> wunlock -> (out of asan) -> runlock sequence I think
09:25skipwich has quit [Remote host closed the connection]
09:26skipwich has joined #asahi-dev
09:35___nick___ has quit []
09:35bisko has joined #asahi-dev
09:37___nick___ has joined #asahi-dev
09:37___nick___ has quit []
09:39___nick___ has joined #asahi-dev
10:13ChaosPrincess has quit [Quit: WeeChat 3.8]
10:14ChaosPrincess has joined #asahi-dev
10:14Mary6 has quit []
10:15Mary6 has joined #asahi-dev
10:21jannauyes, with startplasma-wayland from a tty, plasmashell crashes consistently, starts as expected without QV4_MM_AGGRESSIVE_GC=1
10:26nyilas has joined #asahi-dev
10:59chadmed_ has joined #asahi-dev
10:59chadmed has quit [Read error: Connection reset by peer]
11:09marcanI worked around it with a ridiculous number of automated breakpoints to skip over the problem areas
11:22marcanok, WTF, this JIT code is calling a function then immediately storing a caller-preserved register into the stack
11:36gladiac is now known as Guest7557
11:36gladiac has joined #asahi-dev
11:37jannauABI allows to return more 8 byte directly so x1 could be part of the return value. the rules for function arguments apply to return types as well
11:42Guest7557 has quit [Ping timeout: 480 seconds]
12:16marcanjannau: the really nasty kwin stuff goes away with plasmashell running, probably by accident
12:16marcanso we can prooobably punt on that as long as we at least disable blur by default because that is very broken
12:18zef has joined #asahi-dev
12:23zef_ has quit [Ping timeout: 480 seconds]
12:25MajorBiscuit has joined #asahi-dev
12:40c10l57 has quit []
12:40c10l has joined #asahi-dev
13:35jannaumarcan: plasmashell is slow with QV4_MM_AGGRESSIVE_GC=1 but the patch seems to fix the segfaults
13:39tobhe_ has joined #asahi-dev
13:44tobhe has quit [Ping timeout: 480 seconds]
14:03kettenisjannau: see it; does this diff actually fix booting linux or does it merely prevent a (very annoying) warning?
14:21jannaukettenis: it avoids the warning and prevents the disabled root ports from being discovered. i.e. it restores the observed pcie setup to having the ports deleted from the dt
14:22jannauthe lmb max region change fixes booting, the issue was that there was no lmb region for the uefi binary
14:25kettenisThe 2023.4 release is around the corner, and already has the number of lmb regions bumped to 16
14:25kettenisI'm basically asking whether we should push for these changes to be included in 2023.4 or not
14:27jannau16 is should be ok for now, pcie is mostly cosmetical and releng has pcie disabled anyway. no need to rush any of the two patches
14:30gladiac is now known as Guest7571
14:30gladiac has joined #asahi-dev
14:34kettenisthanks; hopefully this will be merged into the next branch or merged onto master early in the 2023.7 cycle
14:36Guest7571 has quit [Ping timeout: 480 seconds]
14:51veeyee has joined #asahi-dev
15:13bisko has quit [Read error: Connection reset by peer]
15:15bisko has joined #asahi-dev
15:25leftas has joined #asahi-dev
15:29Leftas7 has quit [Ping timeout: 480 seconds]
15:53pranav has joined #asahi-dev
16:17bisko has quit [Read error: Connection reset by peer]
16:47amarioguy has joined #asahi-dev
17:27nyilas has quit [Remote host closed the connection]
17:28barrett has joined #asahi-dev
17:29nyilas has joined #asahi-dev
18:02pranav has quit [Quit: Connection closed for inactivity]
18:06MajorBiscuit has quit [Ping timeout: 480 seconds]
18:06barrett_ has joined #asahi-dev
18:07barrett has quit [Remote host closed the connection]
18:20amarioguy has quit [Remote host closed the connection]
18:22veeyee has quit [Quit: Leaving.]
18:28amarioguy has joined #asahi-dev
19:26winter has quit [Quit: The Lounge - https://thelounge.chat]
19:38veeyee has joined #asahi-dev
19:45gladiac has quit [Quit: k thx bye]
20:14veeyee has quit [Quit: Leaving.]
20:14veeyee has joined #asahi-dev
20:15veeyee has quit []
20:28eiln has joined #asahi-dev
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:36stickytoffee has joined #asahi-dev
21:39WindowPa- has joined #asahi-dev
21:39WindowPain has quit [Read error: Connection reset by peer]
22:09nyilas has quit [Remote host closed the connection]
22:30skipwich has quit [Quit: DISCONNECT]
22:31skipwich has joined #asahi-dev
22:40barrett_ has quit [Ping timeout: 480 seconds]
22:52barrett has joined #asahi-dev
23:54chadmed has joined #asahi-dev
23:59chadmed_ has quit [Ping timeout: 480 seconds]