William D. Jones

>For MSP430 init we should move the discussion to another thread/issue. Fair enough. In the context of this issue, we are [removing](https://github.com/rust-embedded/msp430/pull/7) `enable_cs` (or making it `unsafe`, though I would...

`enable_cs` has been removed from the msp430 crate, so at least from the msp430 side of things `CriticalSection` being `Clone` isn't a problem. As for `Mutex`, what about https://github.com/rust-embedded/bare-metal/issues/43 as...

As much as I [disdain](https://github.com/rust-lang/rust/issues/67819) the bloat, I don't think getting rid of panics or even `panic_immediate_abort` is desirable. Rather, I wish `rustc` was smart enough to recognize (even if...

@MarcoIeni I ran headfirst into this issue as well. My workaround for now is the following: ``` // Newtype to implement PartialEq on svd::Device without needing // to fork the...

Apparently Tier 3 targets need a maintainer too. I'm fine w/ either the msp430 team or myself being a maintainer (cc: @YuhanLiin, would you be open to maintaining it too?)....

>This target supports interlinking with C code compiled using the TI MSP430 GCC compiler. Yes this is correct, but I would put a caveat that cross-language LTO w/ the GCC...

> @cr1901 I've fallen off embedded Rust lately, so I'm not really the right person for maintenance duty. @YuhanLiin Okay, no problem. I can take care of things. I've also...

@jamesmunns > Are there any plans to update your quickstarts to cargo-generate? Can this issue be closed? Once `v0.2.0` crates are published, I will update `msp430-quickstart` to use `cargo-generate`; publishing...

@jamesmunns Long overdue, but `msp430-quickstart` has been [updated](https://github.com/japaric/msp430-quickstart/pull/5) to use `cargo-generate`. This issue can be closed I believe.

My understanding is that, you need to check in `.cargo/config` in a workspace targeting multiple architectures at once. Consider a workspace containing: * x86_64 testing application * An ARM micrcocontroller...