#
✕ nick:fl0_id_
#asahi-dev · 2026-10-20 15:18
fl0_id_(f.e. last year I stayed at a flatshare for free - it was a bit outside, but doable)
#asahi-dev · 2026-10-20 15:18
fl0_id_for c3, def do not hesitate to ask for a discount. you don't need to only eat cup ramen or sth, just explain your situation and usually that's enough. if anybody needs help with a ticket/voucher or a place to sleep, I will try to help
#asahi-dev · 2026-10-20 10:50
fl0_id_it's still basically a pebkac problem i guess
#asahi-dev · 2026-10-10 22:05
fl0_id_JamesCalligeros[m] no worries, I have other stuff that I would care about more, I just wanna stay up to date-ish and learn. just had to look up that reference and I guess I haven't been on that website in very long
#asahi-dev · 2026-10-10 22:01
fl0_id_ah that makes much more sense haha. yeah I read about that work, but didn't associate it with that name
#asahi-dev · 2026-10-10 21:58
fl0_id_chadmed random movie mention... I was super into it years ago haha
#asahi-dev · 2026-10-10 21:57
fl0_id_myria isn't is like good for async stuff etc?
#asahi-dev · 2026-10-10 21:56
fl0_id_dumb question, p3s is not similar to RPCS3 is it? (yes I tried searching)
#asahi-dev · 2026-09-24 12:45
fl0_id_ah thx. so m3 max ecore prob also uses more power i guess
#asahi-dev · 2026-09-24 12:43
fl0_id_nickchan what's the difference, different chickens and IDs? or actually also different functioning
#asahi-dev · 2026-09-23 20:34
fl0_id_MaximilianKenfenheuer[m] I think someone wanted to take a look... maybe check irc logs (search) and ask if they are still on it. or check PRs...
#asahi-dev · 2026-09-22 14:07
fl0_id_diesller[m] then don't and read the blog(s) and / or irc logs ;)
#asahi-dev · 2026-09-18 15:55
fl0_id_JPeisach check how far apart they are. probably asahi-wip
#asahi-dev · 2026-09-18 08:47
fl0_id_integralpilot happy holidays :)
#asahi-dev · 2026-09-15 11:36
fl0_id_like just spelling, but I assume this will be part of the cover letter
#asahi-dev · 2026-09-15 11:36
fl0_id_just language things: repports => reports. "Internally the AVD does not uses an Apple specifik format (format modifier??)"- "does not use" and "specific"
#asahi-dev · 2026-09-12 09:14
fl0_id_yeah. some ppl did send to the mailing list, but I didn't see any replies
#asahi-dev · 2026-09-12 09:12
fl0_id_myria it seems MRs on sourceforge are most active... but yeah it's bit unclear where activity happens
#asahi-dev · 2026-09-08 12:41
fl0_id_right. you think it might work (with some changes) for t6031? like if it needs testing. otherwise I'll leave it for now
#asahi-dev · 2026-09-08 12:18
fl0_id_sofus I can probably try it later or tomorro. it just adds dcp right?
#asahi-dev · 2026-09-04 09:24
fl0_id_(but possible with container or vm)
#asahi-dev · 2026-09-04 09:24
fl0_id_images are a bit hard to build...
#asahi-dev · 2026-09-04 09:24
fl0_id_oh you mean only the installer. yeah for sure, it's just not always obviosu ( to me) how things connect
#asahi-dev · 2026-09-04 09:23
fl0_id_myria why do you not just use the dev installer? wasn't it live already?
#asahi-dev · 2026-08-28 10:50
fl0_id_yuka it's a space odyssey alright :)
#asahi-dev · 2026-05-22 21:23
fl0_id_so there is https://github.com/step21/linux-asahi/tree/t6031-multidie-wip but like I said the additional parts are not rly tested so prob faster if you redo it I assume, sorry
#asahi-dev · 2026-05-22 21:22
fl0_id_jannau: I kinda had one, but then I couldn't really test it b/c I had no time and my tree/setup was bodged. Then I had the bright idea to bring my m3 for a screen replacement (after a year) and now have to re-setup everything...
#asahi-dev · 2026-01-17 11:49
fl0_id_integralpilot thx for thinking about that. I am traveling today, so can only check tonight cet
#asahi-dev · 2026-01-13 11:37
fl0_id_Mmmh ok. Sven but that is for macOS only right? Or should it work / is necessary for using cs with linux as well?
#asahi-dev · 2026-01-05 18:54
fl0_id_looking at differences between t6030 and t6031 - is there a reason why in src/cpufreq, some switch statements only include t6031, not t6030 (but all other devices) or did integralpilot or others add this locally? if this was different between these, it would seem like a pretty big change. selectively disabling things did not help however haha
#asahi-dev · 2026-01-05 17:13
fl0_id_(and good, then i don't have to check there)
#asahi-dev · 2026-01-05 17:12
fl0_id_svenpeter[m]: probably, from src/cpufreq.c I just thought maybe it already jumped / started the kernel as it is after uncompressing the kernel. and m1n1(proxy) is presumably running on that one core, so what's the problem (for m1n1) ^^ I tried different values for the counter, but they don't seem to change anything. Would be just like me to have overlooked sth incredibly basic ... but not as far as i could find
#asahi-dev · 2026-01-05 14:37
fl0_id_at the point where the kernel has been uncompressed, and then says "initializing clusters" - is the device tree also important at that stage? like just wondering if it can be only chickens or a fault in the device tree could also crash it here
#asahi-dev · 2026-01-04 01:00
fl0_id_https://www.pastery.net/hruxye/
#asahi-dev · 2026-01-04 01:00
fl0_id_integralpilot ok, I get some output on ACM1. but yeah it looks like only m1n1 output
#asahi-dev · 2026-01-04 00:28
fl0_id_to clarify for integralpilot - it briefly shows the rainbow logo, then switches to asahi logo with logs (which I assume is the kernel) but only very briefly, before reloading m1n1
#asahi-dev · 2026-01-03 20:38
fl0_id_no, seems to be correct.
#asahi-dev · 2026-01-03 20:31
fl0_id_the t6031 chickens were originally added by dberlin, in the commit message they also said the early uart base changed, but this is exactly where it's currently failing for me. could it be possible that this is not always the same? maybe I'll just try some other ones or it's because of some other issue...
#asahi-dev · 2026-01-03 20:16
fl0_id_playing around a bit more with everest chickens, nothing else seems to effect this so far. neither positively or negatively, even without any chickens it still gets to the same place in the startup sequence
#asahi-dev · 2026-01-03 19:55
fl0_id_but prob these are not related
#asahi-dev · 2026-01-03 19:54
fl0_id_as this seems to fall within VUART, could it help to add uart to the device tree?
#asahi-dev · 2026-01-03 19:42
fl0_id_now it fails after some pmgr stuff and with SERROR
#asahi-dev · 2026-01-03 19:41
fl0_id_hey, so I commented the two t6031 specific chickens before the init_common_everest and that got me quite a bit further afaict https://www.pastery.net/gpnjmq/
#asahi-dev · 2026-01-02 23:59
fl0_id_integralpilot I ran it via hypervisor now. similar exception only in EL1 now as expected, but maybe with some more helpful debug output https://www.pastery.net/erjhwn/