#asahi-dev · 2026-08-15 17:01
yukadidn't immediately look like code to me#asahi-dev · 2026-08-15 17:01
yukait was some pointers#asahi-dev · 2026-08-15 16:59
yukaI can dump the contents ofc#asahi-dev · 2026-08-15 16:59
yukaAs I wrote in my PR: It is unclear if this region serves a special purpose#asahi-dev · 2026-08-15 16:55
yukaok, let me update the branch#asahi-dev · 2026-08-15 16:55
yukalmao#asahi-dev · 2026-08-15 16:55
yukasven: do you think we should add a reserved-memory workaround for the ctrr(?) ro issue or write a feedback assistant or both?#asahi-dev · 2026-08-15 15:02
yukahttps://termbin.com/eiitlb#asahi-dev · 2026-08-15 14:56
yukathey are structured very differently#asahi-dev · 2026-08-15 14:56
yukaI can not decipher the tz_regs for t8140/t6041#asahi-dev · 2026-08-15 14:42
yukabut m1n1 does not care about the carveout-memory-map in mmu_add_default_mappings, which is why it needs special handling for the mcc carveouts#asahi-dev · 2026-08-15 14:41
yukaAh, they are covered by the carveout-memory-map, so they are reserved to the kernel#asahi-dev · 2026-08-15 14:39
yukabut I guess this is not a problem since the kernel does not blanket map everything?#asahi-dev · 2026-08-15 14:38
yukathey are only unmapped inside of m1n1, and not once the kernel re-inits the mmu?#asahi-dev · 2026-08-15 14:38
yukathe ones read from "plane_base+i*tz->stride+tz->{start,end}", and then unmapped#asahi-dev · 2026-08-15 14:36
yukamcc carveouts#asahi-dev · 2026-08-15 14:24
yukaand if so, what about mcc even matters to linux other than it being enabled?#asahi-dev · 2026-08-15 14:22
yukado the carveouts even matter once linux takes over?#asahi-dev · 2026-08-15 14:08
yukado we also want an mcc_disable_cache and ensure the cache is disabled at some point?#asahi-dev · 2026-08-15 14:05
yukaI guess we still need mcc_unmap_carveouts() then even if these are enabled at boot?#asahi-dev · 2026-08-15 14:04
yukathey start out with 0x2800 = 0x8000000c, 0x2804 = 0xc000c00, and if I write 0 or some other <0xc value 'X' to the last nibble of the enable reg, it is echoed back as 0xX000X00 in the status reg. So I guess that means CACHE_WAYS = 12.#asahi-dev · 2026-08-15 14:00
yukat8140 & t6040 are different from this: both have a moved CACHE_ENABLE/CACHE_STATUS (0x2800/0x2804 instead of 0x1c00/0x1c04) and are already enabled on startup#asahi-dev · 2026-08-15 13:58
yukajust a different reg_offset, and the mcc_count can't be estimated using the remaining regs since there are trailing regs which are not mccs#asahi-dev · 2026-08-15 13:57
yukasame cache-ways#asahi-dev · 2026-08-15 13:56
yukasame tz_regs#asahi-dev · 2026-08-15 13:56
yukat8132 mcc is very similar to t6030#asahi-dev · 2026-08-15 05:24
yukafor quickly dumping some memory area using a phone#asahi-dev · 2026-08-15 05:24
yukawebusb m1n1 proxyclient when#asahi-dev · 2026-08-15 04:21
yukaquoting one of sven's messages from april: "much of the s3_0_c11_c smells like CTRR stuff to me"#asahi-dev · 2026-08-15 04:19
yukawait, that should be s3_0_c11_c1_4 and s3_0_c11_c2_0#asahi-dev · 2026-08-15 04:09
yukathat should bring the secondary cores in line with the boot cores, and fix the boot issues#asahi-dev · 2026-08-15 04:09
yukahttps://github.com/AsahiLinux/m1n1/pull/657#issuecomment-5300454583 <-- I suppose I could send a feedback assistant requesting s3_0_c11_c0_12 and s3_0_c11_c0_16 to be zeroed on the secondary cores?#asahi-dev · 2026-08-14 19:13
yukajannau: that means if I got a match for region-id-2, then its start/end value minus 1*stride should be the ones in the tz_regs?#asahi-dev · 2026-08-14 18:52
yukawell, if I assume stride = 0x14, then the entries above and below all have start = end = 0x10000000#asahi-dev · 2026-08-14 18:50
yukaand do not even make for reasonable start and end#asahi-dev · 2026-08-14 18:50
yukathe values below and above it do not match with any region-id-*#asahi-dev · 2026-08-14 18:49
yukaand what is the stride#asahi-dev · 2026-08-14 18:49
yukabut I'm not sure if this is supposed to be the first entry now#asahi-dev · 2026-08-14 18:49
yukathe mcc regs on t8132 are funny: mcc[7]+0x704 = 0x103e6da8, mcc[7]+0x708 = 0x103ffda7, which would be start and end of carveout-memory-map region-id-2#asahi-dev · 2026-08-14 16:29
yukanot sure if those new crates are still somehow related to the async runtime#asahi-dev · 2026-08-14 16:28
yukachaos_princess: I think originally smol was a tcp stack and async runtime?#asahi-dev · 2026-08-14 15:24
yukaalso "This can be used along with dumping the mcc reg space" I assume this does not mean dumping the mcc reg space from a booted macOS, but from m1n1? and then looking for values which would result in the carveout addresses?#asahi-dev · 2026-08-14 15:23
yukawhy would I need a booted macos for looking at a DT node otherwise#asahi-dev · 2026-08-14 15:22
yukadoes macOS modify the adt during boot?#asahi-dev · 2026-08-14 15:22
yukathe cache_enable part seems quite easy to figure out given a trace, but the tz start/end/enable not so much. I don't understand this part: "by looking at region-id-2 and region-id-4 on a booted macos, in the /chosen/carveout-memory-map DT node"#asahi-dev · 2026-08-14 13:52
yukaand you derive it from a trace by recognizing the same patterns that were written on m1?#asahi-dev · 2026-08-14 13:51
yukaand can't find any docs on the mcc#asahi-dev · 2026-08-14 13:51
yukaWhat is the dcs_* for in mcc.c? I don't see it being used anywhere#asahi-dev · 2026-08-12 19:26
yukaIs the irq num maybe wrong?#asahi-dev · 2026-08-12 16:10
yukatrying wifi with 26.6 fw