2026-06-07
00:30voidah has quit [Ping timeout: 480 seconds]
00:31ipatch has quit [Quit: WeeChat 4.9.0]
00:32ipatch has joined #asahi-dev
00:37voidah has joined #asahi-dev
00:45voidah has quit [Ping timeout: 480 seconds]
00:53voidah has joined #asahi-dev
01:02voidah has quit [Ping timeout: 480 seconds]
01:09voidah has joined #asahi-dev
01:18voidah has quit [Ping timeout: 480 seconds]
01:26voidah has joined #asahi-dev
01:26Calandracas_ has joined #asahi-dev
01:26Calandracas has quit [Ping timeout: 480 seconds]
01:35Calandracas_ has quit [Remote host closed the connection]
01:45Calandracas has joined #asahi-dev
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
02:00nnym has quit [Read error: No route to host]
02:00nnym has joined #asahi-dev
02:08voidah has quit [Ping timeout: 480 seconds]
02:09gargantua has quit [Ping timeout: 480 seconds]
02:16voidah has joined #asahi-dev
02:25voidah has quit [Ping timeout: 480 seconds]
02:26gargantua has joined #asahi-dev
02:33voidah has joined #asahi-dev
02:42voidah has quit [Ping timeout: 480 seconds]
02:44tobhe has joined #asahi-dev
02:49voidah has joined #asahi-dev
02:51tobhe_ has quit [Ping timeout: 480 seconds]
02:55gargantua has quit [Remote host closed the connection]
02:55gargantu1 has joined #asahi-dev
03:41marvin24_ has joined #asahi-dev
03:45nora_ has joined #asahi-dev
03:47nora has quit [Ping timeout: 480 seconds]
04:00Stary has quit [Quit: ZNC - http://znc.in]
04:08Stary has joined #asahi-dev
04:56WoC has joined #asahi-dev
05:17ishyemini has joined #asahi-dev
05:21ishyemini has quit [Quit: Leaving]
05:22voidah has quit [Ping timeout: 480 seconds]
05:29voidah has joined #asahi-dev
05:33ishyemini[m] has joined #asahi-dev
05:38voidah has quit [Ping timeout: 480 seconds]
05:45voidah has joined #asahi-dev
05:54voidah has quit [Ping timeout: 480 seconds]
06:01voidah has joined #asahi-dev
06:06gargantua has joined #asahi-dev
06:08gargantu1 has quit [Ping timeout: 480 seconds]
06:09voidah has quit [Ping timeout: 480 seconds]
06:17voidah has joined #asahi-dev
06:25voidah has quit [Ping timeout: 480 seconds]
06:34voidah has joined #asahi-dev
06:42voidah has quit [Ping timeout: 480 seconds]
06:49voidah has joined #asahi-dev
06:50voidah has quit [Remote host closed the connection]
06:58voidah has joined #asahi-dev
07:10ViniciusPeixoto[m] has joined #asahi-dev
07:18voidah has quit [Remote host closed the connection]
07:18voidah has joined #asahi-dev
08:01voidah has quit [Ping timeout: 480 seconds]
08:05jannauit won't be a slideshow and I don't remember display without gpu as unsable. under kwin it ishould have improved due to using an overlay plane for the cursor
08:07minecrell0 has quit []
08:07jannauthe main advantage simpldedrm has over dcp is that it supports damage while dcp always swaps complete framebuffers
08:07minecrell has joined #asahi-dev
08:09jannaui.e. simpledrm has an advantage when only a small part is updated. without overlay cursor movement would be the prime example
08:10voidah has joined #asahi-dev
08:18voidah has quit [Ping timeout: 480 seconds]
08:26voidah has joined #asahi-dev
08:35voidah has quit [Ping timeout: 480 seconds]
08:36JamesCalligeros[m]Swap reqs have damage region support on paper but i couldnt make them work
08:40JamesCalligeros[m]macos never uses them either iirc
08:42voidah has joined #asahi-dev
08:43jannaualso not how the driver works at the moment. only way I can image how it could work is that either the driver or dcp has a separate static framebuffer and dcp blits the damage into it
08:45ralim has quit [Quit: The Lounge - https://thelounge.chat]
08:46ralim8 has joined #asahi-dev
08:51voidah has quit [Ping timeout: 480 seconds]
08:52svenI just don’t wanna know how quick it burns through the battery; all cores were easily at 20-30% running llvmpipe
09:00voidah has joined #asahi-dev
09:04jannauI guess a little less so due to the damage handling but unless the notebook is constantly used the powered backlight while the display is "off" will burn those savings
09:29jannausven: due you known if any of atc sub-device register functions might call back into atc and thus deadlock? I think a deadlock during probe could be catastrophic when other devices are probe as well. asking for https://github.com/AsahiLinux/linux/issues/465
09:33sventhe only thing that could happen was that e.g. the mux was registered and would already trigger a callback to atc from a different thread while atc was busy registering the phys
09:35svenbut i'm pretty sure i guard against that by taking the mutex before registering all those devices
09:38jannauye, atc->lock is locked while registering the devices. so the only issue could be that one of register calls tries to access the locked phy. it would be unexpected and I think it's unlikely to be racy either
09:44jannauprobing tipd, dwc3 and atc at the same time is probably racy but I don't understand why that would easily reproducible on some devices and and at all on others
09:45svenand well... the atcphy struct would disappear, so that's probably not it because we'd just see a crash
10:05jannauthe register calls all look sane. I don't see how they could indirectly call back into atc
10:06pb17 has quit [Ping timeout: 480 seconds]
10:07pb17 has joined #asahi-dev
10:30gargantua has quit [Ping timeout: 480 seconds]
10:36sofus has joined #asahi-dev
10:40freetolga has quit [Quit: Connection closed for inactivity]
10:55sofus has quit [Read error: No route to host]
10:58voidah has quit [Ping timeout: 480 seconds]
11:00beastd has joined #asahi-dev
11:01voidah has joined #asahi-dev
11:09voidah has quit [Ping timeout: 480 seconds]
11:17voidah has joined #asahi-dev
11:25pjv has joined #asahi-dev
11:25voidah has quit [Ping timeout: 480 seconds]
11:35voidah has joined #asahi-dev
11:40svenhttps://git.kernel.org/pub/scm/linux/kernel/git/sven/linux.git/log/?h=b4/nvme-m3 something like that would be nvme support for macos 15+ if we go with the "new compatible" path
11:44voidah has quit [Ping timeout: 480 seconds]
11:52voidah has joined #asahi-dev
11:58pb17 has quit [Ping timeout: 480 seconds]
12:01pb17 has joined #asahi-dev
12:01voidah has quit [Ping timeout: 480 seconds]
12:02voidah has joined #asahi-dev
12:03xal has quit []
12:05xal has joined #asahi-dev
12:10voidah has quit [Ping timeout: 480 seconds]
12:18voidah has joined #asahi-dev
12:26voidah has quit [Ping timeout: 480 seconds]
12:34voidah has joined #asahi-dev
12:42voidah has quit [Ping timeout: 480 seconds]
12:52voidah has joined #asahi-dev
13:03svenother alternative would be to add apple,firmware-version but we also need to change the compatible because the old driver will SError very early
13:11voidah has quit [Ping timeout: 480 seconds]
13:19voidah has joined #asahi-dev
13:20chaos_princessAppleANS3NVMeController. But apple themselves are inconsistent since that same device is RTBuddy(ANS2)
13:21gi0 has joined #asahi-dev
13:35pjv has quit [Quit: pjv]
14:11nickchan"ANS2" is on Apple A11-A13 and T2, it's roughly similar to the m1 device but it doesn't have linear SQ or nvmmu
14:13svenand hen M2 dropped the linear sq, nvmmu stuff and apple still called that ans3, didn't they?
14:14nickchani need to do some additional testing on how the t8015-nvme-ans2 compatible behave if used on like t6000
14:15nickchanthe a11 driver is broke-ish until the patch that is still on the list so i do want to test again
14:16svenbtw. what exactly happens when the nvme driver SErrors because we try to access the pre-15 MMIO registers? does that only crash that one thread or does the kernel stop completely then?
14:17nickchanSError exception should be a kernel panic; it's async and all linux knows is that it came from "somewhere"
14:22nickchan"assert failed: [7442]:cmd fetch error for host Admin SQ, rresp code 2, status_reg: 0x1000000"
14:22nickchanokay so the status is still the same, optional linear sq on T8103, on T6000 it became required
14:39WoC has quit [Remote host closed the connection]
14:42sveni guess we really should add apple,firmware-abi to any new thing we upstream to prevent this nvme mess :(
15:11voidah has quit [Remote host closed the connection]
15:11voidah has joined #asahi-dev
15:19voidah has quit [Ping timeout: 480 seconds]
15:27voidah has joined #asahi-dev
15:35voidah has quit [Ping timeout: 480 seconds]
15:43voidah has joined #asahi-dev
15:51voidah has quit [Ping timeout: 480 seconds]
15:59voidah has joined #asahi-dev
16:07voidah has quit [Ping timeout: 480 seconds]
16:15voidah has joined #asahi-dev
16:23voidah has quit [Ping timeout: 480 seconds]
16:33voidah has joined #asahi-dev
16:36Yushi has quit [Remote host closed the connection]
16:37Yushi has joined #asahi-dev
16:50voidah has quit [Ping timeout: 480 seconds]
16:58voidah has joined #asahi-dev
17:01gi0 has quit []
17:05Yushi has quit [Remote host closed the connection]
17:10Yushi has joined #asahi-dev
17:30aites[m]Heya all! I've been trying to set up the m1n1 hypervisor on my Macbook M2 Max and I've been following the guide (https://asahilinux.org/docs/sw/m1n1-hypervisor/), but when creating the kernel cache and finding the debug dwarf, you need to have the kernel from the kernels directory match exactly with your SoC, right? I think that the M2 Max uses the t6021 kernel but from the KDK I found on the apple website I couldn't find a t6021 kernel
17:33svenand t6022 is then just 2x t6021 dies with a very high speed connection inbetween so that one likely uses the same kernel as well
17:34aites[m]Ahh right, I'm currently trying to boot with the t6020 and it's stuck on the rainbow logo with no progress bar
17:35MikeM64 has quit [Ping timeout: 480 seconds]
17:36Calandracas_ has joined #asahi-dev
17:39aites[m]The latest version I believe, 26.5, I tried with running sudo picocom -b 115200 /dev/ttyACM1 on a separate terminal before starting macos but it hasn't given me any outputs
17:39yuka> The m1n1 hypervisor targets macOS Ventura 13.5. Running later versions of macOS under the m1n1 hypervisor is not supported.
17:42Calandracas has quit [Ping timeout: 480 seconds]
17:46yuyichao has quit [Quit: Konversation terminated!]
17:48yuyichao has joined #asahi-dev
17:58yuyichao has quit [Quit: Konversation terminated!]
17:58yuyichao has joined #asahi-dev
18:09nela has quit [Quit: Ping timeout (120 seconds)]
18:10nela has joined #asahi-dev
18:13voidah has quit [Ping timeout: 480 seconds]
18:21voidah has joined #asahi-dev
18:24catred has quit [Remote host closed the connection]
18:29voidah has quit [Ping timeout: 480 seconds]
18:37voidah has joined #asahi-dev
18:51voidah has quit [Ping timeout: 480 seconds]
19:01voidah has joined #asahi-dev
19:09voidah has quit [Ping timeout: 480 seconds]
19:19voidah has joined #asahi-dev
19:27voidah has quit [Ping timeout: 480 seconds]
19:35voidah has joined #asahi-dev
19:52voidah has quit [Ping timeout: 480 seconds]
19:54michaelros4444559 has joined #asahi-dev
20:00voidah has joined #asahi-dev
20:08voidah has quit [Ping timeout: 480 seconds]
20:17voidah has joined #asahi-dev
20:24asahi has joined #asahi-dev
20:27MikeM64 has joined #asahi-dev
20:34yuyichao has quit [Quit: Konversation terminated!]
20:35yuyichao has joined #asahi-dev
20:35yuyichao has quit []
20:35yuyichao has joined #asahi-dev
20:35yuyichao has quit []
20:36yuyichao has joined #asahi-dev
21:08michaelros4444559 has quit [Read error: Connection reset by peer]
21:09michaelros4444559 has joined #asahi-dev
21:17StanfordAppliedCyber[m]m2 has sptm on 26.5? damn i didn't realize the gl plumbing was present for so long
21:17StanfordAppliedCyber[m]i suppose they definitely rolled it out on iphone chips first
21:18chaos_princessm2 is one of the earliest to get sptm, in 15. m3 got it in 26, and m1pro/max in 26.something-non-zero
21:19chaos_princessthat's why we are targeting 14.something for m3
21:21StanfordAppliedCyber[m]yeah i knew about ppl on m1, i read your blog post on that ages ago
21:28gargantua has joined #asahi-dev
21:37slowlydev has joined #asahi-dev
21:41slowlydev has quit [Remote host closed the connection]
21:45slowlydev has joined #asahi-dev
21:45slowlydev has quit [Remote host closed the connection]
21:46slowlydev has joined #asahi-dev
21:49kaazoo has joined #asahi-dev
21:51asahi has quit [Quit: asahi]
21:53kaazoo has quit [Remote host closed the connection]
22:00Z750 has quit [Quit: bye]
22:05slowlydev has quit [Remote host closed the connection]
22:07StanfordAppliedCyber[m]i'm preparing a PR for the xnu bootstrap SPTM table document (this is the biggest one and, aside from txm, the only one that isn't an iommu whose core functionality we already understand)
22:08StanfordAppliedCyber[m]where should i put the file under docs?
22:08Z750 has joined #asahi-dev
22:08gargantua has quit [Ping timeout: 480 seconds]
22:10StanfordAppliedCyber[m]fw is the place that stuck out to me but figured i'd just ask
22:11JamesCalligeros[m]If youre describing a fw interface it should go in fw yeah
22:11StanfordAppliedCyber[m]this is the first out of 6 documents, xnu bootstrap (all the page table mapping stuff), txm, then dart/uat/sart/nvme
22:11StanfordAppliedCyber[m]ack, will submit a PR shortly then, writing these docs really made me remember how annoying figuring all this stuff out in the first place was
22:39ansg191_ has joined #asahi-dev
22:54ansg191_ has quit [Remote host closed the connection]
23:17aites[m]chaos_princess: because I forgot I could run a second partition with an older version of macOS on it haha
23:19aites[m]though, softwareupdate only provides up to Ventura version 13.8 so im gonna have to take another look at this when i get more time for that tomorrow o-o
23:27gargantua has joined #asahi-dev
23:50veloek has quit [Ping timeout: 480 seconds]