#
#asahi-dev · 2025-03-23 11:20
mischa85but lemme try without any handling at all
#asahi-dev · 2025-03-23 11:20
mischa85yes but the character gets passed, it requires a combination with another specific char to do anything
#asahi-dev · 2025-03-23 11:17
svenit's pretty likely 0x1f will be somewhere in the xnu binary and mess things up
#asahi-dev · 2025-03-23 11:16
mischa85i was thinking the same thing, but 0x1f doesn't seem to be involved. but going to disable them anyway just to be sure
#asahi-dev · 2025-03-23 11:15
sveniirc there are some control chars that will be caught by the cs software. have you tried disabling them?
#asahi-dev · 2025-03-23 11:11
mischa85this time in total early bringup m1n1 mode at 115200 baud
#asahi-dev · 2025-03-23 11:10
mischa85alright, i now tried with a way smaller release kernel. it stops at 0x5d2360/0x3ed4000, does show the dots this time. but throws another serialexception
#asahi-dev · 2025-03-23 09:12
svenmakes testing and picking them up easier :)
#asahi-dev · 2025-03-23 09:12
nickchannext version
#asahi-dev · 2025-03-23 09:11
nickchansven: I will for that version, thanks for the heads up!
#asahi-dev · 2025-03-23 09:03
svendoes that one also require changes to the dt? if yes please directly add those to the series
#asahi-dev · 2025-03-23 07:55
nickchanrebased my a7-a11 pmu series above the feat_pmuv3 support, will send when the merge window closes
#asahi-dev · 2025-03-23 04:25
chadmedlesgoo figured out the silly alsa client thing
#asahi-dev · 2025-03-23 00:39
mischa85so worries for later i guess
#asahi-dev · 2025-03-23 00:39
mischa85anyway, disabling mmc_init() doesn't make a difference
#asahi-dev · 2025-03-23 00:33
mischa85but this still doesn't explain how two big hex values translate to tz.count/stride/start/end/enable
#asahi-dev · 2025-03-23 00:33
mischa85So dberlin wrote this: Note: For unhandled machines, the TZ regions can be found (on m1, m2, m3) by looking at region-id-2 and region-id-4 on a booted macos, in the /chosen/carveout-memory-map DT node. This can be used along with dumping the mcc reg space to find the correct start/end/enable above.
#asahi-dev · 2025-03-23 00:30
fl0_idah ok :)
#asahi-dev · 2025-03-23 00:30
fl0_idyeah makes sense
#asahi-dev · 2025-03-23 00:30
mischa85yeah i noticed on my irc searches
#asahi-dev · 2025-03-23 00:30
fl0_id(or so I assume)
#asahi-dev · 2025-03-23 00:29
fl0_idmischa85 ah yeah btw their nick on irc is yuka probably
#asahi-dev · 2025-03-23 00:29
mischa85at least enough to get hv running which might supply some missing values and chickens
#asahi-dev · 2025-03-23 00:28
mischa85fl0_id: yeah it's going to be a bit of a mix here and there. i have a branch from yu-re-ka which got some info on t8132, now with t6031 i'm trying to fill in the gaps for t6041
#asahi-dev · 2025-03-23 00:27
mischa85so i might very well have those wrong
#asahi-dev · 2025-03-23 00:26
mischa85i still have a tz_regs section which i'm unsure about in mcc. should be translatable from region-id-2 and region-id-4 but nobody told anyone *how* they translate
#asahi-dev · 2025-03-23 00:25
fl0_idmischa85 yeah based on the code numbers that makes sense I guess. Like also on m3, m3 has an 8x number, pro and max have a 6x. and the pro and max always need extra things
#asahi-dev · 2025-03-23 00:23
mischa85no problem, it's fine
#asahi-dev · 2025-03-23 00:23
mischa85t6041 seems more similar to t6031 than to t8132 in many ways
#asahi-dev · 2025-03-23 00:22
fl0_idjust wanted to make sure I didn't accidentally sabotage you
#asahi-dev · 2025-03-23 00:22
fl0_idmischa85 ok good
#asahi-dev · 2025-03-23 00:22
mischa85fl0_id: not really. it's mainly useful to see where m3max and m4max are similar and give me some hints
#asahi-dev · 2025-03-23 00:21
fl0_idmischa85 btw, didn't think about it at the time, but does the adt change between firmware versions? as the one I sent you was still for sonoma as I'm stlll using that. Not sure if I mentioned that at the time...
#asahi-dev · 2025-03-23 00:15
mischa85*mcc
#asahi-dev · 2025-03-23 00:15
mischa85could this be related to mmc?
#asahi-dev · 2025-03-23 00:10
mischa85m1n1 is not responding anymore fwiw
#asahi-dev · 2025-03-23 00:04
mischa8524D60 kernel stops at 0x21a7eb0/0x6e3c000
#asahi-dev · 2025-03-22 23:39
mischa85i still have a seperate partition on 15.1 because anything newer bootloops before m1n1 even loads
#asahi-dev · 2025-03-22 23:38
mischa85but lemme gather a different one for science
#asahi-dev · 2025-03-22 23:38
mischa85the one i use right now matches the one on the macos partition m1n1 is running from
#asahi-dev · 2025-03-22 23:36
chadmedi had trouble with m1n1's heap not being big enough for certain payloads a while ago but i dont think it's that unless the kernel is now 1 GB
#asahi-dev · 2025-03-22 23:35
chaos_princesswant to figure out if it is a uart problem and some pattern in the file breaks it, or m1n1 crashes due to some other reason
#asahi-dev · 2025-03-22 23:35
chaos_princessdifferent version or something
#asahi-dev · 2025-03-22 23:34
chaos_princessOk, can you find a different kernel image
#asahi-dev · 2025-03-22 23:33
chaos_princessRight, i think it has to be a mach-o
#asahi-dev · 2025-03-22 23:33
mischa85the random file doesn't upload at all as it fails some parsing (makes sense)
#asahi-dev · 2025-03-22 23:33
mischa85construct.core.StreamError: Error in path (parsing) -> cmds -> args
#asahi-dev · 2025-03-22 23:26
mischa85sure
#asahi-dev · 2025-03-22 23:25
chaos_princesscan you generate a random file of that length and try uploading that?
#asahi-dev · 2025-03-22 23:25
chaos_princesshmm

plus ›