#asahi-dev · 2025-12-24 17:05
nickchanfl0_id: the treatment of t6031 and t6030 is almsot the same#asahi-dev · 2025-12-24 16:59
fl0_id(specifically also was looking at that, as integralpilot set some registers to boot macos#asahi-dev · 2025-12-24 16:58
fl0_idchickens_everest still looks a bit suspect to me. specifically, seems somewhat unlikely that t6031 needs so little special treatment compared to t6030, then just uses the "common" chickens that both use. but ofc maybe that's just incidental#asahi-dev · 2025-12-24 16:28
fl0_idok, thx for the clarfification#asahi-dev · 2025-12-24 16:23
chaos_princessit is the same, but it is a good habit to do so, to make sure c code changes apply#asahi-dev · 2025-12-24 16:09
fl0_id(or git commit hash or w/e)#asahi-dev · 2025-12-24 16:09
fl0_idnickchan right. but asssuming I have the same m1n1 versions, should it not be the same?#asahi-dev · 2025-12-24 16:08
nickchanespecially now the hypervisor is being modified to run macOS on m3...#asahi-dev · 2025-12-24 16:08
nickchanfl0_id: the hypervisor abi is not stable#asahi-dev · 2025-12-24 16:04
fl0_id@integralpilot - one q, why are you chainloading m1n1 from host to target, when it is already installed and waiting for proxy connection? Is this really necessary in your experience? I thought this was only for quickly trying new m1n1 versions or things like that#asahi-dev · 2025-12-24 15:02
fl0_idyeah, obviously :) linux: cat /dev/cu.somethingsomething : device not found ;)#asahi-dev · 2025-12-24 14:53
chaos_princessshould be doable if you change the M1N1DEVICE env var to use the linux naming convention#asahi-dev · 2025-12-24 14:07
fl0_idintegralpilot thanks for the writeup! I hope it work with a linux host too, as I have only 1 mac atm#asahi-dev · 2025-12-24 13:46
chadmedstill not doing anything with them but ill figure it out next week now#asahi-dev · 2025-12-24 13:21
chadmeddidnt realise it was still gated for 6.5#asahi-dev · 2025-12-24 13:21
chadmedcrawls back into his hole#asahi-dev · 2025-12-24 13:20
jannaujust to make sure, you're setting the env variable to enable overlays#asahi-dev · 2025-12-24 13:20
chadmedat this point i think the speed limit is iomfb itself though like i really cant see anything we're doing that would cause such long scanout/flip times #asahi-dev · 2025-12-24 13:19
chadmedyeah once its correct we can make it fast #asahi-dev · 2025-12-24 13:19
jannaunot sure how much or if at all it helps but at least it's closer to the intended design#asahi-dev · 2025-12-24 13:18
chadmed(other than the cursor which still works fine of course) #asahi-dev · 2025-12-24 13:17
chadmedcurrent and hopefully less tricky problem to solve is why kwin absolutely refuses to ever scan out anything on any plane and is always compositing no matter what#asahi-dev · 2025-12-24 13:16
chadmedill play with it more after the food and booze wears off in a few days :P #asahi-dev · 2025-12-24 13:15
chadmedjannau: thats close to what i had but i had subclassed drm_plane in a dumb way so that couldve been the problem#asahi-dev · 2025-12-24 13:07
jannaumerry christmas#asahi-dev · 2025-12-24 13:06
jannaudcp_surface is at least for now mostly unversioned and it allows moving code from templated code#asahi-dev · 2025-12-24 13:05
jannauchadmed: I was thinking about something like https://github.com/jannau/linux/commit/85a8222c8d92338416fe685f3274101132752e57 (untested since I don't want to unpack a test macbook on the train)#asahi-dev · 2025-12-24 11:50
svenMerry Christmas :)#asahi-dev · 2025-12-24 11:20
chadmedive given up on dcp for now for similar reasons, merry christmas :) #asahi-dev · 2025-12-24 10:50
integralpilotalso, merry chirstmas everyone! :)#asahi-dev · 2025-12-24 10:50
integralpiloti've just documented my current progress on booting macOS under m1n1 on M3 in a github gist, in case anyone wants to try and confirm it works for them or help with what i'm currently blocked on after the chirstmas period. https://gist.github.com/IntegralPilot/85c355124fe54e670e6d5586c7a07826#asahi-dev · 2025-12-24 09:27
mazfl0_id: no worries, I don't think anyone needs this urgently, if at all. when you get a chance to test it, let me know.#asahi-dev · 2025-12-24 07:06
chadmeda global shadow wont work because by the time we get to iomfb_flush we've already lost the state we need for the "current" commit#asahi-dev · 2025-12-24 07:05
chadmedyeah i cant figure out how to do this sanely given our firmware interface without a bunch of superfluous allocation and freeing#asahi-dev · 2025-12-24 04:33
chadmedsetting up the surfaces in atomic_plane_update is super unreliable/racy but im probably doing something wrong#asahi-dev · 2025-12-23 20:29
fl0_id(I would also be ok with sleeping in the gym, but as I'm not coming from home I have a bit more luggage and I cannot leave that there afaik)#asahi-dev · 2025-12-23 20:28
fl0_idi'll prob be at 39c3 from 27th and will bring a setup for debugging / testing m3 max things. still looking for accomodation so if somebody has a couch or whatever to offer I'm all ears#asahi-dev · 2025-12-23 20:23
fl0_idmaz compiles for me. cannot test flashing or functionality atm#asahi-dev · 2025-12-23 18:12
jannauchadmed: the annoying part of dcp_surface is that it's firmware version dependent#asahi-dev · 2025-12-23 18:11
jannausofus: no they use SPI to transport the HID packets but the HID interface should be the same or very similar#asahi-dev · 2025-12-23 15:48
sofusim pretty sure something similar could also work for non silicon macs with haptics, based on an out off tree driver i found#asahi-dev · 2025-12-23 15:46
sofusjannau: from my understanding m1 machines dont use dockchannel?#asahi-dev · 2025-12-23 15:37
jannauit started this was because there was only a single plane anyway#asahi-dev · 2025-12-23 15:36
jannauchadmed: we should create our own plane struct, embed drm_plane and dcp_surface and fill the dcp surface in apple_plane_atomic_update()#asahi-dev · 2025-12-23 13:43
chadmedand definitely are not linear#asahi-dev · 2025-12-23 13:43
chadmedive traced a few different video formats being scanned out directly from avd and general desktop stuff and the not-avd surfaces definitely have different plane/compression info#asahi-dev · 2025-12-23 13:40
chadmedjannau: the compression info is a list of structs describing the compression format with a bunch of magic numbers. the "plane" info one is the same (see my dcp/scanout branch) but seems to do double duty for tiled formats with fields for tile size/stride/etc#asahi-dev · 2025-12-23 13:25
jannauchadmed: how does it look exactly? the compression metadata is in a separate chunkt of the buffer? do we need per tile information without compression?#asahi-dev · 2025-12-23 13:22
jannausofus: great. I believe the HID interface on M1* machines is similar but hid transport might miss some things#asahi-dev · 2025-12-23 13:21
chadmedthe "compression" and tile format information