#
✕ nick:chaos_princess
#asahi-dev · 2025-07-12 08:57
chaos_princessAnd also asahi is almost impossible on m4 with macos 15.x due to apple bug that is fixed in 26.x
#asahi-dev · 2025-07-12 08:57
chaos_princessdevices - well, you need the devices in question, so go to apple.com and you can easily get a quote that way. Time - we kinda got two "hard" generations in a row with m3 and m4. m3 has a new gpu ISA, which is the "hard" part for it, and m4 will need a lot of m1n1 work (m1 also did, ofc, but most of it was "hidden", as when that was happening the project was a lot more low profile).
#asahi-dev · 2025-07-08 21:03
chaos_princesskettenis: mind tagging u-boot?
#asahi-dev · 2025-07-07 20:57
chaos_princessnice
#asahi-dev · 2025-06-29 16:09
chaos_princessup to you
#asahi-dev · 2025-06-29 16:03
chaos_princess*err_disconnect
#asahi-dev · 2025-06-29 16:02
chaos_princessdepending on if it is ok to operate in this "degraded" state
#asahi-dev · 2025-06-29 16:02
chaos_princessand you may or may not want to add a goto entry_disconnect after dev_err(tps->dev, "Couldn't register sysfs group for CD321x VDMs\n");
#asahi-dev · 2025-06-29 16:01
chaos_princessno, just drop entry cleanup at all. the fact that you moved the creation to the end is enough
#asahi-dev · 2025-06-29 15:59
chaos_princessyou got the order wrong, now all other errors will cause a non-existent sysfs groups to be removed
#asahi-dev · 2025-06-29 14:11
chaos_princessyes, but it is more that you are not cleaning up everything that you should if something errors out
#asahi-dev · 2025-06-29 14:06
chaos_princessbuilt-in here, and it seems like your thing probes before the supplier devices do. so something returns EPROBE_DEFER after you created the sysfs entries, and you never clean up those on error
#asahi-dev · 2025-06-29 14:05
chaos_princessare you building as module or built-in?
#asahi-dev · 2025-06-29 14:05
chaos_princessi think i maybe see the issue
#asahi-dev · 2025-06-29 14:04
chaos_princesshttps://pastebin.com/ymNM30Xu - that should be all the relevant bits
#asahi-dev · 2025-06-29 14:00
chaos_princesssysfs spam is still a thing though
#asahi-dev · 2025-06-29 13:59
chaos_princessi could talk between machines over serial with picocom
#asahi-dev · 2025-06-29 13:59
chaos_princessdfu port is port1 on j314
#asahi-dev · 2025-06-29 13:57
chaos_princessok, nvm, i am stupid, it works
#asahi-dev · 2025-06-29 13:54
chaos_princessactually, wait
#asahi-dev · 2025-06-29 13:54
chaos_princessyep, still not working
#asahi-dev · 2025-06-29 13:28
chaos_princesssure, give me a few mins
#asahi-dev · 2025-06-29 12:31
chaos_princesssure
#asahi-dev · 2025-06-29 12:09
chaos_princessi also get a bunch of this dmesg spam https://pastebin.com/PdvmgHBi
#asahi-dev · 2025-06-29 12:08
chaos_princesspatching out the check does not help btw
#asahi-dev · 2025-06-29 12:02
chaos_princesshttps://pastebin.com/7wczp2rF
#asahi-dev · 2025-06-29 11:36
chaos_princesssure, how do i test it?
#asahi-dev · 2025-06-24 13:28
chaos_princessthat specific firmware blob is per-os-install, and the one from 13.5 is used
#asahi-dev · 2025-06-24 13:27
chaos_princessfrom firmware's perspective, all asahi installs are macos 13.5
#asahi-dev · 2025-06-24 13:25
chaos_princessno
#asahi-dev · 2025-06-21 14:24
chaos_princessfl0_id: usb power gating is probably not working properly
#asahi-dev · 2025-06-18 10:31
chaos_princessfat pointer, and then you can copy it yourself
#asahi-dev · 2025-06-18 10:12
chaos_princessslice::from_raw_parts(thing as *const Whatever as *const u8, mem::size_of::<Whatever>()) ?
#asahi-dev · 2025-06-16 11:35
chaos_princessProbably not amazing that we do not package fexconfig in upstream repo, but idk how to package linux fex
#asahi-dev · 2025-06-16 11:31
chaos_princessstrace on some small x86 app and see where it looks?
#asahi-dev · 2025-06-16 11:22
chaos_princessidk, maybe it is that, maybe it is some registry location, i am not sure
#asahi-dev · 2025-06-16 11:21
chaos_princessdoesn't it pick fexconfig for the 64-bit precision?
#asahi-dev · 2025-06-16 08:19
chaos_princessm1
#asahi-dev · 2025-06-16 08:18
chaos_princesswell, i already had like 2 instances of thinking "having nested virt would be really useful right now" just last week :P
#asahi-dev · 2025-06-16 08:05
chaos_princessyes
#asahi-dev · 2025-06-16 08:04
chaos_princessalso, if you do RE on m4, use tahoe as base macos, all relevant sonoma versions have an apple bug that breaks a feature that linux needs
#asahi-dev · 2025-06-16 08:03
chaos_princessthis is the easy part
#asahi-dev · 2025-06-16 07:50
chaos_princessNo active work from core project, if you want a "how does one do that", join #asahi-devel on matrix and scroll up a page or two
#asahi-dev · 2025-06-13 22:38
chaos_princessnobody, but feel free to ask here
#asahi-dev · 2025-06-13 21:22
chaos_princessiirc m1 does not have wifi6, and half of the patchset is about that, and the wifi chip is broadcom, so might want to not regress other users
#asahi-dev · 2025-06-13 21:21
chaos_princessi think if you want to poke at wifi, you might want a m2 and probably a raspi
#asahi-dev · 2025-06-13 21:17
chaos_princessyou can dualboot. In fact, we do not support removing macos
#asahi-dev · 2025-06-13 21:11
chaos_princesswe are 6.14
#asahi-dev · 2025-06-08 10:39
chaos_princessthere is the possible downside that if you are messing with the disk, there is a chance that it will destroy all oses that are installed in that container, but i don't think that is likely
#asahi-dev · 2025-06-08 10:38
chaos_princessthat should work

plus ›