Hey Y'all, I'd like some guidance on getting things upstream. I've been building an aarch64 port of AROS. The 64-bit ARM architecture support (CPU backend, context switch, ABI, the arch-level bits) is the part I think has general value. It isn't tied to my machine, it would apply to native aarch64 AROS too, a Pi for example. That's the "new platform" I'd like to bring to mainline. My question is mostly about process: how do you usually want a new CPU architecture introduced? Is there a preferred way (branch, patch series, where it lives in the tree, how you want it reviewed)? Separately there's the Apple / darwin-hosted side (Cocoa+Metal display, the hostlib bridges to macOS, the host-signal handling). That one is host-specific and I see it as a different discussion, so I'd keep it out of the arch upstreaming unless you want it later. For context, it boots and is quite stable since I'm no longer using the x18 register, it's even running ffmepg or Rust's std natively now. I also have a couple of small standalone patches ready if it helps to start there: a posixc

arc4random

, and a little hostlib convenience helper. Or maybe if there is anyone with a macbook and apple silicon that is willing to test? Just let me know.