#asahi-dev · 2026-09-26 16:22
jannaum1n1 dockchannel uart works now as well#asahi-dev · 2026-09-26 16:16
jannauor P or whatever#asahi-dev · 2026-09-26 16:16
jannaucomes up on core 6, S core#asahi-dev · 2026-09-26 16:13
jannauI looked at the code and missed it#asahi-dev · 2026-09-26 16:04
jannauthe M6 boot core has both MIDR_CORE_TYPE_P and MIDR_CORE_TYPE_M set. MIDR is 0x611f0731#asahi-dev · 2026-09-26 15:56
jannauuart works#asahi-dev · 2026-09-26 15:54
jannauuart is my fault. I looked at the wrong adt and ended up with the wrong address#asahi-dev · 2026-09-26 15:35
jannaum1n1 doesn't appear to be crashing but a watchdog appears to be active. after a few minutes it restarts to recovery#asahi-dev · 2026-09-26 15:33
jannauno m1n1 output on M6, dockchannel uart stops with "End of iBootStage2 serial output." and samsung uart is completely silent#asahi-dev · 2026-09-26 15:29
jannauah, I thought the first large package on connect was enough#asahi-dev · 2026-09-26 15:26
jannau0x0 works#asahi-dev · 2026-09-26 15:26
jannauit seems to work#asahi-dev · 2026-09-26 15:26
jannauI see 0x34980000 in wireshark but kisd guesses 0x348000000 after I added bcd 5.00#asahi-dev · 2026-09-26 15:25
jannauI already forget everything#asahi-dev · 2026-09-26 15:25
jannaufor debugusb#asahi-dev · 2026-09-26 15:24
jannauyuka: was there a known offset for the macos wireshark captured address and the actual base?#asahi-dev · 2026-09-26 14:38
jannauflying spaghetti monster. I almost written a 3 letter word#asahi-dev · 2026-09-26 14:25
jannauthank FSM, the M6 has again "parent_addr = 0x200000000"#asahi-dev · 2026-09-26 13:09
jannaulol, the m6 mac mini froze during resizeContainer. I initially assumed it wasn't making any more progress at 15%#asahi-dev · 2026-09-26 12:07
jannauanything dcp related in the macos log? macos may timeout external display setup if the HV is too slow, seen with dcp tracing specifically#asahi-dev · 2026-09-26 11:55
jannau23.5G of apple intelligence data. Where do I charge Apple for that? multiply by 2-3 installtions per device#asahi-dev · 2026-09-26 11:53
jannauerr, jumps between 58 and 63 GB, not sure what it does? maybe refreshes apple intelligence model data in the background?#asahi-dev · 2026-09-26 11:50
jannauhow does the min macos storage in the installer work? Do we need to adjust it for macOS 27.0? the m6 uses almost 60GB after its initial update#asahi-dev · 2026-09-26 11:42
jannauthe template devicetree still has aqc references so I suppose they kept it. Their ILO appears to be a integrated aqc solution#asahi-dev · 2026-09-26 11:35
jannaumac mini 2.5 gbps ethernet is Realtek 8125#asahi-dev · 2026-09-26 11:20
jannaualready full of runners for berlin marathon adjacent events#asahi-dev · 2026-09-26 11:19
jannaujoke is on me, none of the two apple stores had a m5 ultra on display. 27km cycling, wouldn't have been as bad had I thought to avoid the area around the brandenburg gate#asahi-dev · 2026-09-26 08:19
jannauexcept maybe for serial numbers but I'm not sure what I can do with the serial numbers of a random store unit#asahi-dev · 2026-09-26 08:18
jannauyes, picking the m6 mini up. not sure what apple store people should have against looking at ioreg output. not that would contain any secret information#asahi-dev · 2026-09-26 08:01
jannauit does, I guess I'll check later in the Apple store#asahi-dev · 2026-09-26 07:49
jannauM5 Ultra can use then either t6050d.dtsi or t6052.dtsi#asahi-dev · 2026-09-26 07:48
jannauI guess we can use t6050.dtsi and t6050s.dtsi for M5 Pro and t6050c.dtsi for M5 Max#asahi-dev · 2026-09-26 07:47
jannaum5 max has chip-id 0x6050. would be interesting what m5 ultra uses. unfortunately ioreg doesn't print chip-id#asahi-dev · 2026-09-25 17:19
jannauthen macOS either dies too early or it is otherwise broken under HV#asahi-dev · 2026-09-25 17:17
jannaualso possible that whatever m1n1 does breaks macos. try uncommenting #define NO_DISPLAY in config.h#asahi-dev · 2026-09-25 17:14
jannaum1n1 would be expected as the iboot interface appears to be incomptible on m4 and/or macOS 26#asahi-dev · 2026-09-25 14:29
jannauyuka: you might need to parse it in the apple pinctrl driver as well#asahi-dev · 2026-09-25 12:47
jannaufor nv15 I'd expect YCbCr format with a plane with "BitsPerBlock = 40"#asahi-dev · 2026-09-25 12:46
jannauno, 'p420' packs 3 values into 4 bytes with 2bits of padding (or 6 into 8 bytes for CbCr) if we're speaking about "PixelFormat = 1882468912;"#asahi-dev · 2026-09-25 12:36
jannauyuka: I think "gpio-reserved-ranges" is at least close enough that you would have to argue why you can't use it#asahi-dev · 2026-09-25 12:34
jannausofus: I did not look at your tree and replied to "But nv15 gives the correct bpp"#asahi-dev · 2026-09-25 12:06
jannauit packs 4 consecutive 10-bit values in 5 bytes#asahi-dev · 2026-09-25 11:51
jannauI think P___ are semi-planar high-bit-depth (Y plane and interleaved CbCr plane). I wouldn't read too much into it and just look up how the format is defined#asahi-dev · 2026-09-25 11:33
jannaufrom Documentation/devicetree/bindings/gpio/gpio.txt "gpio-reserved-ranges" seems to the right property#asahi-dev · 2026-09-25 11:23
jannauanother possible solution would be to add a property to Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml#asahi-dev · 2026-09-25 11:22
jannaulooking through the other dt-bindings and not seeing something that might be similar is enough#asahi-dev · 2026-09-25 11:10
jannaudid you check if any other pinctrl dt-binding has something similar#asahi-dev · 2026-09-25 11:09
jannauyuka: "apple,protected-pins" (no underscore) is fine and and matches "apple,npins". I could bikeshed over "apple,unused-pins", "…,skipped-pins", "…,externally-used-pins"#asahi-dev · 2026-09-25 08:26
jannauI got the day wrong but I remembered. unfortunately Miguel was sick so I did not ask him#asahi-dev · 2026-09-24 19:23
jannauthe model/compatible property order and 2 new node order issues but the line length and dcache-size property issues are gone