#
#asahi-dev · 2025-12-26 09:55
integralpilotalso sorry forget to mention, for hypervisor work, if anyone's trying it, you also need to apply https://patch-diff.githubusercontent.com/raw/AsahiLinux/m1n1/pull/515.diff
#asahi-dev · 2025-12-26 09:54
integralpilotoh thanks, i'll look into that
#asahi-dev · 2025-12-26 09:20
jannauthe documentation patch isn't merged but I think it should work now. never tried it myself though
#asahi-dev · 2025-12-26 09:19
jannauhave you seen https://lore.kernel.org/linux-kbuild/20240906-macos-build-support-v2-8-06beff418848@samsung.com/
#asahi-dev · 2025-12-26 09:18
jannauintegralpilot: yes, assume that cpu offsets are predictable
#asahi-dev · 2025-12-26 06:51
integralpilotits actually funny, because i used to use that as a hackintosh during lockdown, now its being used for the reverse
#asahi-dev · 2025-12-26 06:43
integralpilotatp, ive given up trying to compile linux (with my devicetree changes) on macOS. i think i'll pull out my old skylake tower from 2015 (the only other device i've got beside my macs).
#asahi-dev · 2025-12-26 05:34
integralpilotcu.usbmodem* is the macOS naming
#asahi-dev · 2025-12-26 05:34
integralpilotfl0_id: just saw you weren't finding cu.usbmodem devices, not sure if you've figured this out yet but on linux the relevant devices are /dev/ttyACM0 (for M1N1DEVICE) and /dev/ttyACM1 (for picocom), respectively.
#asahi-dev · 2025-12-26 04:24
integralpilotmy M3 pro is binned (missing an everest). in the devicetree can i just assume the extra everest is the same offset as all the others from the last one?
#asahi-dev · 2025-12-26 02:40
integralpilotalso sorry forgot to mention if you're trying m1n1 on hypervisor, don't plug the USB-C cable into the DFU port on the target (cloest to magsafe) as the connection will get reset as macOS reinitalises it during the boot process
#asahi-dev · 2025-12-26 02:37
integralpilotthanks to everyone who is trying it out, hopefully fresh eyes might be able to see how we can fix the random panics and i'll take a look from a fresh perspective later too
#asahi-dev · 2025-12-26 02:31
integralpilotsort of blocked on hypervisor work, so trying smth new and making t6030 device tress for the asahi kernel
#asahi-dev · 2025-12-26 00:10
chadmedi just git-restored my entire branch. the thing i was doing was stupid
#asahi-dev · 2025-12-26 00:10
chadmedyeah, and i spent like 3 hours wondering why the committed state was always one state ahead of our captured state :P
#asahi-dev · 2025-12-26 00:04
jannauI think subclassing drm_plane was wrong. dcp_surface belongs state. should have been obvious since it is derived from the common new state
#asahi-dev · 2025-12-25 23:53
chadmedoh you have to subclass state too
#asahi-dev · 2025-12-25 21:34
fl0_idok thx
#asahi-dev · 2025-12-25 20:31
integralpilotfl0_id: use 14.8.3 instead, it should work the same.
#asahi-dev · 2025-12-25 14:45
chadmedits 1am though, problem for tomorrow
#asahi-dev · 2025-12-25 14:45
chadmedso ive probably just got the order of operations wrong
#asahi-dev · 2025-12-25 14:45
chadmedok only broken thing now is a null pointer deref when "update" = "mr dcp tear down this plane"
#asahi-dev · 2025-12-25 14:33
chadmedso iomfb_flush is just filling in the swap from the captured state then flipping a switch on the crtc to tell plane_update to fill the other state and surface info
#asahi-dev · 2025-12-25 14:32
chadmedmy version keeps all the guts in iomfb_template so that we dont have to worry about versioning and also tracks state with the surface so that we dont have surfaces drifting away from their "designated" atomic_state
#asahi-dev · 2025-12-25 14:31
chadmedill take a look tomorrow and push something working so we can compare
#asahi-dev · 2025-12-25 14:30
jannauit was completely broken because I duplicated the padding
#asahi-dev · 2025-12-25 14:30
jannauchadmed: updated the branch to something working. survices boot, login to plasma and reboot
#asahi-dev · 2025-12-25 14:21
chadmedstill explodes sometimes but at least something gets drawn on the screen _before_ it explodes now!
#asahi-dev · 2025-12-25 14:20
chadmedok its sorta working? keeping two states and updating one while scanning out the other seems to do the trick mostly
#asahi-dev · 2025-12-25 09:03
fl0_idintegralpilot: do you have a source for 14.7.7? not sure which version I have installed anymore, but in mist for example 14.7.7 is not available anymore
#asahi-dev · 2025-12-25 02:55
integralpilotif you do see a panic that is the same message and at the same stage each time, there might be a new issue with 14.8.3 I’ll have to look into it after Christmas
#asahi-dev · 2025-12-25 02:49
integralpilotnow you’ll see non-determinstic panics due to memory/state corruption, where it happens is different each time, it might be in early boot, it might be after we’ve started most of the user space and about to start the GUI
#asahi-dev · 2025-12-25 02:48
integralpilotb074: if you see a progress bar and virtual serial output at all, it means all the binary patches work (they fix things that go wrong before we have those things)
#asahi-dev · 2025-12-24 20:28
b074having serial is a great step already. Ill try to help out if I get some progress as well
#asahi-dev · 2025-12-24 20:26
b074running on the 14.8.3, and I get a kernel panic very early on. So maybe some of the offsets have indeed changed
#asahi-dev · 2025-12-24 20:24
b074just confirms integralpilot progress on the t6030. Adding the chickens for the time registers + the in-memory patches is enough to get a loading bar and virtual serial output
#asahi-dev · 2025-12-24 19:23
b074merry christmas
#asahi-dev · 2025-12-24 19:23
b074thank you integralpilot
#asahi-dev · 2025-12-24 17:41
fl0_idthanks
#asahi-dev · 2025-12-24 17:41
fl0_idok :)
#asahi-dev · 2025-12-24 17:41
svenit’s essentially a incantation we have to recite to get the cores to work properly an we have no real way to figure out what exactly is going on
#asahi-dev · 2025-12-24 17:39
svenit’s contained in a single file and I don’t even care if we have the same sequence in there 10x as long as they do whatever xnu does
#asahi-dev · 2025-12-24 17:39
svendon’t try to make that code beautiful, just make it work
#asahi-dev · 2025-12-24 17:39
sventhey are very fragile, I’d keep the order especially because we don’t understand most of them
#asahi-dev · 2025-12-24 17:38
fl0_idis the order or registers set for chickens usually important? if not necessarily, I would move common ones to common and test that, but if the usually the order is very specific, probably not worth doing it. (some are common but done first so couldn't go into common as that atm (and in other chickens) gets executed after the custom ones
#asahi-dev · 2025-12-24 17:08
fl0_idnickchan yes, that's what i think. but some values are different. so has to be more carefully examined
#asahi-dev · 2025-12-24 17:07
nickchanand then add integralpilot's registers to init_common_everest()
#asahi-dev · 2025-12-24 17:07
nickchanreally what should happen is most of init_t6030_everest() be removed and call init_common_everst() instead
#asahi-dev · 2025-12-24 17:06
nickchanas for the rest - it's still very similar, but duplicated across init_common_everest() and init_t6030_everest()
#asahi-dev · 2025-12-24 17:05
nickchanin that file it's missing the registers that integralpilot mentioned

plus ›