#asahi-dev · 2025-12-22 16:14
fl0_idmaz it's in pioasm of pico-sdk. but yet, bumping the sdk version / git commit should probably work. at least there was some disussion that this was fixed. lemme check pioasm#asahi-dev · 2025-12-22 14:09
fl0_idok fixed by just bumping the version requirement, once I found the right file#asahi-dev · 2025-12-22 13:58
fl0_id(for flashing to the pi-pico)#asahi-dev · 2025-12-22 13:58
fl0_iddoes anybody have a quickfix for building cs-sw with a newer cmake? some part of pico-sdk apparently expects an older cmake version and I cannot easily install one#asahi-dev · 2025-12-19 15:15
fl0_idsven I also am interested in a ticket, I am still waiting to hear from a friend so far#asahi-dev · 2025-12-19 14:00
fl0_idoliver_ it's often possible to get resale tickets, this year there's an official resale site but also through ppl posting to social media etc#asahi-dev · 2025-12-18 12:54
fl0_idsven if I do make it to c3 ( not sure yet ) would also be up for some m3 hacking (or at least testing etc)#asahi-dev · 2025-12-13 15:42
fl0_idintegralpilot - that would be great, but only if it's not too much work to put it in a draft pr, as I don't know how much I can work on it#asahi-dev · 2025-12-11 11:40
fl0_idin case integralpilot comes back, can someone ask them if they have their work in a branch or just local? would love to take a look#asahi-dev · 2025-12-09 23:43
fl0_idintegralpilot awesome!#asahi-dev · 2025-12-08 18:50
fl0_idintegralpilot awesome sounds great. maybe with these changes I could also do some more testing / debugging over xmas on the t6031#asahi-dev · 2025-11-25 16:04
fl0_idnickchan yeah, sorry I haven't had time to look into it more.#asahi-dev · 2025-11-24 11:13
fl0_idnickchan this is the same for "official" xnu with macos right? cause that was also my experience. (don't remember though at which point it panicked)#asahi-dev · 2025-11-21 15:43
fl0_idtruita sure just wanted to check you never know :)#asahi-dev · 2025-11-20 23:19
fl0_idtruita you can provide logs. but this is unsupported, you know that right?#asahi-dev · 2025-10-09 11:24
fl0_idt6030 is not even there#asahi-dev · 2025-10-09 11:23
fl0_id(for t6031)#asahi-dev · 2025-10-09 11:23
fl0_idjannau also found this comment in the cpufreq_init function: /* Unknown */#asahi-dev · 2025-10-08 16:35
fl0_idok that I should be able to find out, just hope I do not have to reboot too often ^^#asahi-dev · 2025-10-08 16:32
fl0_idyeah it does#asahi-dev · 2025-10-08 15:01
fl0_idbtw this is my error from kernel booting, likely doesn't tell anybody anything new but still, if it does, let me know :) https://www.pastery.net/jujenj/#asahi-dev · 2025-10-05 14:40
fl0_id(this is still with just usb, still need proper pinheaders for the central scrutinizer, so that it doesn't look too messy#asahi-dev · 2025-10-05 14:35
fl0_idas you guys just discussed m4 - tried booting linux kernel on the m3 recently ... unfortunately restarted, but I guess my custom dtb just has some bad adresses or sth.#asahi-dev · 2025-10-01 13:08
fl0_idnnym in the installer or somewhere there should also be an easier to read list of those...#asahi-dev · 2025-09-16 07:15
fl0_idmaettu102 who knows#asahi-dev · 2025-09-14 12:31
fl0_idsven sure. just in general I mean :)#asahi-dev · 2025-09-14 12:29
fl0_idusually I like to use pastery, but was also having issues#asahi-dev · 2025-09-14 12:28
fl0_idbut ok. if you need more let me know #asahi-dev · 2025-09-14 12:28
fl0_idsven weird#asahi-dev · 2025-09-14 12:26
fl0_idoops too late#asahi-dev · 2025-09-14 12:26
fl0_idsven https://pastebin.com/uc6tbrbT#asahi-dev · 2025-09-14 12:20
fl0_idsven I can offer m3 max, or copy the atcphy for you. you mean the adt from macos right?#asahi-dev · 2025-09-13 12:23
fl0_idtruita that's fine, I'm only working on this off an on (more off). I'm not mainly an embedded developer, so I'm not sure I can give good advice on how to learn. For just getting m1n1 updated, I don't think writing a whole OS is necessary. Ofc it's necessary to have at least some systems/embedded understanding, which I cannot judge. For learning that, may get an arm sbc and write an OS for that. (but I never did that and don't have the time for it)#asahi-dev · 2025-09-12 16:56
fl0_idjannau oh right they seem to be missing. Thanks that would be awesome#asahi-dev · 2025-09-12 16:47
fl0_idyou can also ping me for m3 questions. (though I cannot test on normal m3)#asahi-dev · 2025-09-12 16:47
fl0_id unclear to me yet why this error is there, the bypass is not merged) https://github.com/AsahiLinux/m1n1/issues/449#asahi-dev · 2025-09-12 16:47
fl0_idtruita m1n1 should work at least for m3 pro / max. Normal m3 is less tested. However it has some code here: https://github.com/AsahiLinux/m1n1/blob/main/src/smp.c#L269 you could start by making a macos install for exerimenting with m1n1. Then add T8122 in soc.h for uart I assume. (maybe also try the one from T8112 like in smp.c) In case you get to a successful m1n1 proxy, you might have to also add this fix to bypass an adt error. (because it's#asahi-dev · 2025-09-10 22:48
fl0_idjkaczman anything that's broken and that you feel comfortable with :)#asahi-dev · 2025-09-03 14:45
fl0_idchadmed wake on plant#asahi-dev · 2025-08-14 20:10
fl0_idjannau try a blockchain prediction market *ducksÜ#asahi-dev · 2025-08-04 13:27
fl0_id¯\_(ツ)_/¯ #asahi-dev · 2025-08-04 13:17
fl0_idanother reminder why my arch nas is on an lts kernel...#asahi-dev · 2025-07-18 20:53
fl0_id(sry wrong channel)#asahi-dev · 2025-07-18 20:53
fl0_idhi#asahi-dev · 2025-07-07 11:01
fl0_idleio no worries, it is also not certain that this is the issue, I was just speculating#asahi-dev · 2025-07-07 10:57
fl0_idso yes, I assume that's what you mean by breakpointing, that you used the hv. (though I guess you could also do that from linux without hv)#asahi-dev · 2025-07-07 10:56
fl0_idleio it's only active if you start it. you can boot a linux kernel with the hv, but also without.#asahi-dev · 2025-07-07 10:39
fl0_idmaz thx#asahi-dev · 2025-07-07 10:28
fl0_idregarding the HV on m3 - could it be related to memory size, that previous models just didn't support high amounts of ram or at least it was not tested well? (like f.e. did anybody test the HV with 96 GB ram, or 192 on a m2 ultra?) Otherwise it could also be related to differences in EL1 vs EL2, like some instructions seem to differ#asahi-dev · 2025-07-06 12:31
fl0_idso maybe somehow the memory management is different or somehow not mapped right?