#
✕ nick:kettenis
#asahi-dev · 2025-08-19 15:47
kettenisindeed
#asahi-dev · 2025-08-19 15:43
kettenisI suppose we always have the option to do a little bit of devicetree surgery in m1n1 if upstream insists on dropping stuff
#asahi-dev · 2025-08-19 15:39
kettenishopefully we can still add the generic compatibles for the non-upstreamed M2 machines where applicable?
#asahi-dev · 2025-08-19 15:37
kettenisbut now that u-boot uses some git trickery to get the official upstream device trees those old trees are no longer useful
#asahi-dev · 2025-08-19 15:36
kettenisthey were added to make a maintainer happy who insisted on having a device tree for all boards
#asahi-dev · 2025-08-19 15:35
kettenisI should remove those device trees from u-boot
#asahi-dev · 2025-08-19 15:35
kettenisprobably
#asahi-dev · 2025-08-19 15:33
kettenisI found one in the t8103.dtsi that is in the u-boot repo (but that file isn't actually used)
#asahi-dev · 2025-08-19 15:31
kettenisI never used "apple,dart" in U-Boot or OpenBSD so quietly dropping that one is ok from my perspective
#asahi-dev · 2025-08-19 15:24
kettenisthe only "problem" we have is that we started somewhere in the middle now that nickchan is adding support for older hardware
#asahi-dev · 2025-08-19 15:23
kettenisa compatible for the SoC itself and a compatible for the oldest SoC it is compatible with
#asahi-dev · 2025-08-19 15:23
kettenisthat is a fairly typical pattern
#asahi-dev · 2025-08-14 09:33
kettenisthat's a funny typo ;)
#asahi-dev · 2025-08-13 12:04
kettenisso the changes you propose should be fine
#asahi-dev · 2025-08-13 12:04
kettenisconstraints set by the bus-range properties I mean
#asahi-dev · 2025-08-13 12:02
kettenisjannau: regarding bus-range and iommu, OpenBSD will try to program the bus numbers in a way that meets the bus-range properties
#asahi-dev · 2025-08-13 11:51
kettenisthere are bits that don't really make sense
#asahi-dev · 2025-08-13 11:50
kettenismaz, jannau: right; I tried to upstream the FW loader at some point but feedback made me realize the linux driver needs some TLC
#asahi-dev · 2025-08-13 11:49
kettenisOpenBSD uses this binding already and defenitely doesn't use the additional node to instantiate a driver ;)
#asahi-dev · 2025-08-13 11:48
kettenisyeah, I think some push-back is in order
#asahi-dev · 2025-08-12 12:35
kettenisu-boot doesn't look at it at all
#asahi-dev · 2025-08-12 12:34
kettenislooks like linux only uses bus-range for the host bridge
#asahi-dev · 2025-07-07 20:55
kettenissince I managed to upstream a few more bits this round, I rebased the asahi branch on top of that
#asahi-dev · 2025-07-07 20:55
kettenisu-boot 2025.07 was released
#asahi-dev · 2025-07-01 13:50
kettenis(I see 0x7020000000000018 in a crashlog mailbox log that another OpenBSD developer sent me)
#asahi-dev · 2025-07-01 13:49
kettenisHas anyone ever seen a notification for SMC event 0x7020?
#asahi-dev · 2025-06-05 14:52
ketteniscan you check that fixes your issue?
#asahi-dev · 2025-06-05 14:52
kettenisnickchan: https://github.com/AsahiLinux/m1n1/pull/473
#asahi-dev · 2025-06-04 13:38
kettenisah, wait I guess you're loading a kernel directly from the stage1 m1n1
#asahi-dev · 2025-06-04 13:28
kettenisnickchan: are you using the .macho?
#asahi-dev · 2025-06-04 13:27
kettenisbut for some reason it is writable in my environment
#asahi-dev · 2025-06-04 13:26
kettenishmm, I think the pre-defined stage1 version property string ends up in read-only memory
#asahi-dev · 2025-06-02 19:58
kettenisit is mostly generated by m1n1 from the ADT
#asahi-dev · 2025-06-02 19:23
kettenisso is that produced as part of running rustup to install the cross-compile toolchain?
#asahi-dev · 2025-06-02 19:22
kettenishah, building with -Z build-std doesn't have rust/target ;)
#asahi-dev · 2025-06-02 10:58
kettenisand revisit if/when build-std becomes stable
#asahi-dev · 2025-06-02 10:58
kettenischadmed: thanks, sounds like we should go with what I have now then
#asahi-dev · 2025-06-01 18:27
kettenisI marked it as draft as the other option is to just always build m1n1 with -Z build-std
#asahi-dev · 2025-06-01 18:26
kettenisbtw, https://github.com/AsahiLinux/m1n1/pull/471
#asahi-dev · 2025-06-01 10:29
kettenisbad things could happen in smp_call4()
#asahi-dev · 2025-06-01 10:28
kettenisthe spin table is another thing that isn't flushed
#asahi-dev · 2025-05-31 17:43
kettenisbut target_cpu is also written and isn't flushed?
#asahi-dev · 2025-05-31 17:25
ketteniscrap, looking at an old tree
#asahi-dev · 2025-05-31 17:20
kettenisa "dmb sy" isn't going to work if we're running with caches enabled and the CPU that's being started starts without the caches enabled
#asahi-dev · 2025-05-31 17:20
kettenisin src/smp.c:smp_start_cpu()
#asahi-dev · 2025-05-31 17:19
kettenis _reset_stack = secondary_stacks[index] + SECONDARY_STACK_SIZE;
#asahi-dev · 2025-05-31 17:19
kettenisI'm fairly certain we need an explicit cache flush after:
#asahi-dev · 2025-05-31 17:04
ketteniswhile x29 is typically used as a frame pointer, the compiler is free to use it for other purposes
#asahi-dev · 2025-05-31 15:28
ketteniswell there is no cache flush after _reset_stack gets changed
#asahi-dev · 2025-05-31 15:15
kettenisin the m1n1 I looked at, dummy_stack isn't 16-byte aligned

plus ›