Jonathan 'theJPster' Pallant

rebased on master

Hmmm. RESETS is [Send but !Sync](https://docs.rs/rp2040-pac/latest/rp2040_pac/struct.RESETS.html) so this change might be moot.

armv7a-none-eabi, armv7r-none-eabi, armv7r-none-eabihf and armv8r-none-eabihf are tested in the https://github.com/rust-embedded/cortex-ar repo. aarch64-unknown-none-softfloat is tested in https://github.com/rust-embedded/aarch64-cpu/ (but not aarch64-unknown-none?).

I'm not seeing any interest in this.

I think it's fair to say this RFC has been rejected at this time.

I have some branches with some proposed updates: https://github.com/thejpster/rust/branches Please send PRs to that branch with any changes you'd like before it goes upstream.

~~How do you find llvm-objcopy? It's not in $PATH, nor `.cargo/bin`?~~ Actually you can `cargo binstall cargo-binutils` because this project has been built by quickinstall. But it would be better...

How does this work for RP2350, where there is a need to have applications build for both Cortex-M and RISC-V, with no code changes?

The proposed syntax is this, right? ```rust #[external_interrupt(ExternalInterrupt::UART)] unsafe fn external_uart() -> ! { } ``` That's completely unlike what cortex-m-rt does. Will it (cortex-m-rt) be changed to match, or...

Oh and to clarify I mean https://github.com/rp-rs/rp-hal/blob/main/rp235x-hal-examples/src/bin/blinky.rs has to build with both `--target=thumbv8m.main-none-eabihf` AND `--target=riscv32imac-unknown-none-elf`. And today https://github.com/rp-rs/rp-hal/blob/main/rp235x-hal-examples/src/bin/pwm_irq_input.rs does not because it uses `#[interrupt]`.