#asahi-dev · 2025-03-07 15:08
alyssa(for some reason people want games to go fast, idk)#asahi-dev · 2025-03-07 15:08
alyssamaz: i was promised it would also make perf work inside muvm?#asahi-dev · 2025-03-07 14:17
mazjannau: it was the whole point of this exercise. hopefully we can take this into 6.15 (I need to go once more over the details).#asahi-dev · 2025-03-07 13:35
alyssaI do enjoy reading the reddits to see when people notice the features we've quietly shipped :p#asahi-dev · 2025-03-07 13:35
alyssajannau: woo!#asahi-dev · 2025-03-07 12:20
jannauhttps://www.reddit.com/r/AsahiLinux/comments/1j5cnzh/psa_windows_11_arm64_virtual_machines_can_run_on/#asahi-dev · 2025-03-07 12:19
jannaunice, a user has noticed that windows on arm as kvm guest is working with Oliver Upton's PMUv3 emulation patches. I never bothered to test and only got to downloading the install image#asahi-dev · 2025-03-07 09:38
leioI need to see if backports got done#asahi-dev · 2025-03-07 09:38
leioand some of those happened on x86 too on tigerlake#asahi-dev · 2025-03-07 09:37
leiothese are fixed in gtk git#asahi-dev · 2025-03-07 08:52
cy8aerchaos_princess: thanks for the information#asahi-dev · 2025-03-07 08:26
chaos_princessgnome bug, they draw with an unitialized texture, and they don't notice it on x86, as there it is fully transparent#asahi-dev · 2025-03-07 07:58
cy8aer(scrolled from right to left -> scroll to the left desktop would be a better description)#asahi-dev · 2025-03-07 07:55
cy8aerGSK_RENDERER=ngl#asahi-dev · 2025-03-07 07:53
cy8aerm1pro 14''#asahi-dev · 2025-03-07 07:52
cy8aerI have some OpenGL glitches in Gnome: Sometimes (more rarely) I have full-screen magenta flickers when I scroll back and forth between desktops. Less when I do this with the keyboard, more with three fingers and usually scrolled from right to left. Has anyone ever seen this? mesa 20250221, minimum 6.12.12-x, minimum gnome-shell 47.4 but also with 48-beta4#asahi-dev · 2025-03-07 06:21
svenI’d like to see someone review that first, will probably wait for next cycle tbh#asahi-dev · 2025-03-07 05:14
nickchannicolas17: it's all using existing data#asahi-dev · 2025-03-07 05:08
nicolas17nickchan: did you figure out cache sizes for A7-A11?#asahi-dev · 2025-03-07 04:13
nickchanabout the wiki#asahi-dev · 2025-03-07 04:13
nickchanchannel#asahi-dev · 2025-03-07 04:13
nickchansomeone shoule go update the chanel topic#asahi-dev · 2025-03-07 04:13
nickchananyways#asahi-dev · 2025-03-07 01:58
nickchansven: will you apply the a7-a11 cache nodes for this cycle? I already mentioned it should be fine on the list that it is only used for reporting to userspace in sysfs#asahi-dev · 2025-03-06 18:15
nickchanand delay may be above 32-bit and i am not sure the kernel it would like that#asahi-dev · 2025-03-06 18:11
nickchananyways this means that I would have to schedule_delayed_work() up to 194 days and i have no idea how i am going to test that in a short time#asahi-dev · 2025-03-06 18:09
nickchanpresumably since a12 otherwise dtk would have massive issues with time#asahi-dev · 2025-03-06 18:08
nickchan>sets the offset itself on m1#asahi-dev · 2025-03-06 18:06
nickchanwould not be suprising if smc sets the offset itself on m1 so that doesn't happen#asahi-dev · 2025-03-06 18:05
nickchansince whatever time setting set by other software on a7-a11 is overwritten on iOS boot, which is needed so the rtc does not go wrong even if someone reboots the device right when the counter is about to overflow#asahi-dev · 2025-03-06 18:03
nickchansmc may be doing some heavy lifting on m1#asahi-dev · 2025-03-06 18:03
nickchanand OSes will overwrite each other's time configuration, evident if setting time from iOS restore ramdisk#asahi-dev · 2025-03-06 18:02
nickchanon a7-a11 the counter can only count like 194 days and cannot be reset so it requires OS interevention to stay correct#asahi-dev · 2025-03-06 17:58
nickchanalso#asahi-dev · 2025-03-06 17:50
nickchanbut on m1 the rtc definitely has more bits for the offset#asahi-dev · 2025-03-06 17:49
nickchanfunnily enough a11 is still subject to year 2038 problem#asahi-dev · 2025-03-06 17:48
chaos_princesswe access it via smc#asahi-dev · 2025-03-06 17:44
nickchanspmi pmu rtc should exist on m1 too but asahi device tree makes no reference to it#asahi-dev · 2025-03-06 17:01
nickchanmore information tends comes up as research is conducted#asahi-dev · 2025-03-06 17:00
nickchanokay pmu reset panic counter does apply on a7-a11#asahi-dev · 2025-03-06 16:58
sventhanks, reading the last attempt from late 2022 (sigh) there were just a bunch of comments to be addressed#asahi-dev · 2025-03-06 15:54
alyssasven: good luck#asahi-dev · 2025-03-06 13:47
fl0_id(also because I can only do it at one place, so I always had to pause it and restart each time...)#asahi-dev · 2025-03-06 13:42
fl0_idthough I already patched the installer for me as well. so hopefully shouldn't take long once backup is done#asahi-dev · 2025-03-06 13:41
fl0_idmischa85 I decided to do a backup first before installing m1ni1 properly, and my backup is to spinning rust so it's still going. but I'm on it.#asahi-dev · 2025-03-06 10:56
mischa85fl0_id: have you been succesful in dumping t6030/t6031 adt?#asahi-dev · 2025-03-06 10:13
svenaditya: have you guys ever started working on a t2 backend for our smc driver?#asahi-dev · 2025-03-06 08:01
jannausounds good#asahi-dev · 2025-03-06 07:21
svenok, so i'm probably gonna pick up smc again this weekend. my plan is to submit the smallest set of changes possible (dt-bindings, mfd core driver, rtkit backend, gpio driver without irq support) and then follow-up with the other drivers after that's upstream#asahi-dev · 2025-03-06 06:47
jannaucy8aer: those are fixed in 6.13.5-3